Fix ERROR_PATH_BUSY 0X00000094 – Simple to Advanced Steps

Quick Fix (30 Seconds) – Close the Obvious Culprit

Nine times out of ten, this error shows up because another program has a lock on the file or folder you're trying to access. Think of it like someone holding a door open – you can't walk through until they let go.

First, close any app you think might be using that file. If you're trying to delete a PDF, close Adobe Reader. If it's a Word doc, shut down Word. Don't just minimize it – actually close it.

Still stuck? Try rebooting your machine. I know it sounds basic, but a quick restart clears most temporary file locks. If the error goes away after a reboot, you're done. If not, move on.

Moderate Fix (5 Minutes) – Use Task Manager or Process Explorer

If the quick fix didn't work, something is holding the path open and it's not obvious. You need to find the process that's locking it.

Step 1: Find the Locking Process with Task Manager

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Click More details if you only see a simple list.
3. Go to the Details tab. Look for processes like explorer.exe, svchost.exe, or any app you suspect. Right-click and choose End task.

But honestly, Task Manager is crap for finding file locks. Grab Process Explorer from Microsoft Sysinternals – it's free and way better.

Step 2: Use Process Explorer to Unlock the File

1. Download Process Explorer from here (it's an official Microsoft tool).
2. Run it as Administrator (right-click, Run as administrator).
3. Press Ctrl + F to open the Find Handle or DLL dialog.
4. Type the file or folder name that's giving you the error. Hit Search.
5. Process Explorer shows you exactly which process (PID and name) has a handle on that path.
6. Double-click the result – it jumps to that process in the main window.
7. Right-click the process and choose Close Handle. Or if it's safe, just kill the process with Kill Process.

That's it. The path should be free now. Try your original action again.

Advanced Fix (15+ Minutes) – Dig Deeper When Nothing Else Works

If Process Explorer didn't find anything or the handle keeps reappearing, you've got a more stubborn problem. Here's your playbook.

Check for Antivirus or Backup Software

Some antivirus programs (looking at you, McAfee and Norton) lock files while scanning them. Same with backup tools like Carbonite or OneDrive. Temporarily disable your antivirus – not uninstall, just disable real-time protection for a few minutes. Then try again. If it works, add an exclusion for that folder in your AV settings.

Look for Hung Network Drives

If the path is on a network drive or a mapped drive, a disconnected session can leave handles open. Open Command Prompt as Admin and run:

net use

Check for any drives with status Unavailable or Disconnected. Remove them with:

net use Z: /delete

(Replace Z: with the actual drive letter.) Then remap the drive fresh.

Check for Corrupted System Files

Rare, but possible. Run these commands in an Admin Command Prompt:

sfc /scannow

Let it finish. Then run:

DISM /Online /Cleanup-Image /RestoreHealth

Reboot after both complete.

Worst Case – Kill the Explorer Shell

If the window or File Explorer itself has the lock, you can restart the shell. Open Task Manager, find Windows Explorer (not the process, the app under Processes), right-click, and choose Restart. This kills all open Explorer windows but usually clears stale locks.

Why This Happens in the Real World

I've seen 0X00000094 most often when someone tries to delete a file that's still open in a background app. Common triggers: a Word document left open overnight, a PDF in a browser tab, or a video file being indexed by a media server like Plex. Also happens when you try to move a folder while an antivirus scan is running on it.

If you're getting this error on a server, check for open SMB sessions. Run net session in Command Prompt to see who's connected and disconnect stale ones with net session /delete.

One last thing – don't bother with registry hacks or third-party 'unlocker' tools that claim to fix everything. They're rarely needed and can break things. Stick with Process Explorer – it's the gold standard.