STG_E_INUSE (0X80030100): A Device Access Error

I know this error is infuriating — you're trying to access a drive or file, and Windows just tells you it's busy with no clue who's holding it. Here's the fix.

The Quick Fix: Find and Kill the Locking Process

The number one cause of STG_E_INUSE (0X80030100) is a background process that's got a handle on your drive or file. Usually it's backup software, a media player indexing the drive, or a stubborn explorer window. Here's how to find it fast.

1. Download Process Explorer from Microsoft Sysinternals (or use the command line tool Handle.exe if you prefer).
2. Run Process Explorer as Administrator — right-click and pick 'Run as administrator'.
3. Hit Ctrl+F to open the Find Handle or DLL dialog.
4. Type the drive letter or file path that's giving you the error. For example, if your external drive is E:\, type E:\.
5. Process Explorer will list every process holding a handle to that location.
6. Double-click any matching process to jump to it, then right-click it and choose Close Handle (but that's temporary — the process will reopen it).
7. Instead, right-click the process and select Kill Process. Only do this for processes you recognize — avoid killing system processes like svchost.exe.

That's it. Once you kill the offending process, try your operation again. The error should vanish.

Why This Works

Windows uses file handles to track who's reading or writing to a drive. When a process has an open handle, the OS marks the object as busy. The 0X80030100 error is COM's way of saying 'I can't touch that right now'. Process Explorer shows you exactly which handle is locked — it's like having x-ray vision for your file system.

Most of the time, the culprit is an app that didn't release its handle after finishing. I've seen this with Google Drive backup scanning a USB stick, Windows Media Player trying to read thumbnails, and even Adobe Lightroom locking a photo catalog on an external drive. The fix is the same in every case: find the handle, kill the process.

Less Common Variations

Sometimes Process Explorer shows nothing. That's rare but possible. Here's what else to check.

1. Hidden Explorer Handles

An open Explorer window pointing to your drive can hold a handle. Close all Explorer windows and reopen them. If that doesn't work, restart the Windows Explorer process from Task Manager — right-click Windows Explorer under Processes and select Restart.

2. Search Indexer Locking the Drive

Windows Search Indexer can lock newly connected drives. Check if the drive is being indexed. Go to Control Panel > Indexing Options and see if your drive is listed. If it is, remove it from the index temporarily. I've run into this on Windows 10 22H2 with large external drives — the indexer hangs, and nothing else can touch the drive.

3. Antivirus Real-Time Scanning

Some antivirus software locks drives during full scans. Disable real-time protection for a moment and test. If the error stops, add an exclusion for the drive in your antivirus settings.

4. Corrupted Shell Extensions

A bad shell extension (like a custom right-click menu tool) can hold handles open. Use ShellExView from NirSoft to disable third-party extensions one by one and see if the error stops.

Prevention: Stop It From Coming Back

You don't want to fight this error every time you plug in a drive. Here's how to keep the peace.

• Safely eject external drives before unplugging. This forces all handles to close properly. Use the 'Safely Remove Hardware' icon in the system tray — not just yanking the cable.
• Close all apps that might scan the drive before you try to access it. Backup software, media libraries, and photo organizers are the worst offenders.
• Update your drivers for USB controllers and disk drives. Go to Device Manager, find your disk drives, and check for driver updates. Rare but fixes some underlying issues.
• Run chkdsk /f on the drive if you see frequent errors. A corrupted filesystem can cause the OS to hold handles longer than normal. Open Command Prompt as Admin and run chkdsk X: /f (replace X with your drive letter).

That's the whole playbook. No fluff, no 'contact support' nonsense. You've got a handle on it now — literally.