Fix STG_E_FILENOTFOUND 0x80030002 – Windows File Error

Quick answer: The file you're trying to open lives on a drive that Windows can no longer reach—either the drive letter changed, the external drive disconnected, the network share dropped, or the path is corrupted. Don't reinstall software; check the path first.

Why you're seeing 0x80030002

What's actually happening here is that COM (Component Object Model) or the Windows shell is trying to access a storage object—could be a document, a media file, or even a shortcut target—but the underlying file system returns "file not found." The error code STG_E_FILENOTFOUND comes from the Structured Storage API, which older apps like Microsoft Office, Adobe Reader, or even Windows Explorer use. It's not the file itself being corrupt; it's the path being invalid at the moment of access.

This error shows up a lot when you:

Plug in a USB flash drive and Windows assigns it a different drive letter than last time (say E: instead of F:).
Map a network drive, then the connection drops or the folder gets renamed.
Click a shortcut that points to a removable drive that's no longer inserted.
Open a file from a recently used list after the drive disconnects.

The real fix is not to reinstall the app—that almost never works because the path is external to the application. You need to reconnect the file or fix the reference.

Step-by-step fixes

Step 1: Check the file's actual location

Right-click the file or shortcut that throws the error and select Properties. Look at the Target or Location field. If it shows something like E:\Projects\report.docx, and your drive is now F:, that's your culprit. Remap or copy the file to match the path.

Real-world scenario: You open a Word doc from your recent files list. Word says "0x80030002." Check the path—your USB drive was E: yesterday, but today it's F:. Windows can't find the old path. Fix: reconnect the drive or move the file to the original path.

Step 2: Reconnect external drives and check drive letters

Open Disk Management (right-click Start > Disk Management). Look for your external drive. If it has a letter, note it. If the path you saw in Step 1 uses a different letter, you have two choices:

Right-click the drive in Disk Management, select Change Drive Letter and Paths, and assign the same letter it had before (e.g., E:).
Or copy the file from the current drive to the exact path the error expects.

The reason step 2 works: Windows caches absolute paths, not relative ones. Changing the drive letter back restores the original route.

Step 3: Remap network shares

If the file lives on a network share, open File Explorer, right-click This PC, and choose Map network drive. Use the exact same drive letter and path that the error references. For example, if the error says \\Server\Docs\file.txt, you need that share to be accessible right now.

Test connectivity with ping ServerName in Command Prompt first. If ping fails, the server is off or your network is down—no software fix can help that.

Step 4: Rebuild the shortcut or recent file list

For shortcuts (.lnk files) that point to removable drives, just delete the shortcut and create a new one. For recent files lists (MRU lists in Office, or jump lists in Windows), clear them:

Office: File > Options > Advanced > Show this number of Recent Documents > set to 0, restart Office, then set it back.
Windows Explorer jump lists: Right-click the app icon in the taskbar > right-click the file name > Remove from this list.

Step 5: Run SFC and DISM if it's a system file

If the file itself is a system file or a DLL (rare but happens with custom applications), corruption in the component store can cause this. Open Command Prompt as admin and run:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

This won't fix a missing user file, but it ensures Windows system files are intact. I've seen this fix the error when a third-party installer broke a COM registration.

If the main fixes don't work

Sometimes the file is genuinely deleted or the drive is dead. Try these:

Use File History or Previous Versions: Right-click the folder where the file should be, select Restore previous versions. If backups are enabled, you can get the file from a date before it disappeared.
Data recovery tools: For deleted files on a still-working drive, stop using the drive immediately and run something like Recuva or TestDisk. The more you write to it, the less chance of recovery.
Check the Recycle Bin: Yes, obvious—but I've spent 20 minutes on this before realizing the file was sitting in the bin. Open the bin, search for your filename.

Prevention tip

Stop relying on absolute drive letters for removable media. Use paths like %USERPROFILE%\Documents\ for personal files, or store critical data on internal drives with fixed letters. If you must use USB drives frequently, assign them a permanent drive letter via Disk Management—that reduces the chance of collisions. For network shares, use UNC paths (\\Server\Share\file.txt) instead of mapped letters; they survive reboots better.

Also, regularly review your recent files and shortcut lists. If you see a file path referencing a drive letter that changes often, delete that entry before it bites you.