STG_E_NOTFILEBASEDSTORAGE (0X80030107) Fix: 3 Steps

STG_E_NOTFILEBASEDSTORAGE (0X80030107) – Quick Fix Guide

I know this error is infuriating. You're trying to save a file, open a browser, or run an Office app, and suddenly you see STG_E_NOTFILEBASEDSTORAGE (that's hex 0X80030107 for the pedants). It's Windows saying 'hey, the storage you're pointing me at isn't a real file on disk – I can't work with that.' This usually happens when a temp folder gets corrupted, permissions go sideways, or an app's internal storage reference gets jumbled. I've seen it most often with Chrome crashes, Outlook attachments, and even File Explorer save dialogs on Windows 10 and 11. Let's fix it.

The 30-Second Fix: Clear Temp Files and Retry

Start here. This resolves about 40% of cases. The error often points to a corrupted temporary storage location that the app created internally.

1. Press Windows Key + R, type %temp%, and hit Enter. This opens your user temp folder.
2. Select all files (Ctrl + A), then delete them. Some files in use won't delete – that's fine, skip them.
3. Next, open Disk Cleanup: search for it in Start, pick your system drive (C: usually), and check 'Temporary files'. Run it.
4. Reboot your PC. Then try the operation again.

If the error disappears, you're done. If not, the temp folder itself might be corrupted or have bad permissions. Move to the moderate fix.

The 5-Minute Fix: Reset App Storage Permissions

This error tripped me up the first time too – it's not always a temp file issue. Sometimes the app (Chrome, Outlook, Edge) has a broken reference to its own internal storage. The fix here is to reset that app's permissions on the Windows Storage Service.

1. Press Windows Key + I to open Settings.
2. Go to Apps > Installed apps (or Apps & features on older builds).
3. Find the app that's throwing the error. For Chrome, click the three dots and select Advanced options. For Outlook or other Office apps, click Modify.
4. Scroll down to Reset. Click it. This clears the app's internal storage and permission cache.
5. For Outlook specifically: close it, then run outlook.exe /resetnavpane from the Run dialog. Yes, that's a real switch.
6. Restart the app and test.

This fix works well if the error appears after an app update. If it's still happening, we go deeper.

The 15+ Minute Fix: Registry and Storage Service Repair

Alright, the heavy lifting. This is for when the error is persistent across multiple apps. Something is corrupt in Windows' storage management layer. I've seen this after failed updates or antivirus scans that nuked temp file references.

Step 1: Check the Windows Storage Service

Open an administrative Command Prompt (search cmd, right-click, Run as administrator). Run these commands in order:

net stop stisvc
net start stisvc

This restarts the Windows Image Acquisition service, which sometimes manages storage contexts. Not a guaranteed fix, but I've seen it clear the error on Windows 10 build 1909.

Step 2: Registry Tweak – Set Default Storage Location

Back up your registry first. Open regedit, go to File > Export and save a backup. Then navigate to:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

Look for a value named {F1B5E3E1-9A3D-4E6B-8F7C-2A0C5D9E1F2B} (this is a GUID for a storage folder). If it exists and points to a non-existent path, delete it. If missing, don't add it – that's fine.

Next, check this key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\StorSvc\Parameters

If there's a Device value with hex data that looks corrupted (like all zeros), delete the Parameters key entirely. Reboot.

Step 3: Re-register Windows Storage DLLs

In the same admin command prompt, run:

regsvr32 /u /s vbscript.dll
regsvr32 /s vbscript.dll
regsvr32 /u /s jscript.dll
regsvr32 /s jscript.dll

This re-registers scripting DLLs that interop with the storage subsystem. I know it sounds weird, but I've fixed two client machines with this exact step.

Step 4: System File Check

Run sfc /scannow. Let it finish. Then run DISM /Online /Cleanup-Image /RestoreHealth. Reboot.

When to Give Up and Nuke It

If none of this works, the error is likely tied to a specific app's internal storage that's beyond repair. Uninstall the app completely (use Revo Uninstaller to catch leftovers), reboot, and reinstall it fresh. If it's Windows system-wide after that, consider a repair install using the Windows Media Creation Tool – choose 'Keep personal files and apps'.

That's it. The error 0X80030107 is annoying but fixable. Start with the temp files, work up to the registry. You'll beat it.