Fix: Redirector Has Open Handles (0X80000023)

You're sitting there, trying to disconnect a network drive or unload a printer driver, and Windows throws up STATUS_REDIRECTOR_HAS_OPEN_HANDLES (0X80000023). The redirector is in use and cannot be unloaded. This usually hits when you're trying to unmap a drive or remove a network printer, but something—a file, a folder, or a print job—is still holding a connection open. I had a client last month who couldn't remove their old accounting server's mapped drive because Excel had a workbook open on that share. The drive unmount failed, and this error was the result.

What Actually Causes This

The redirector is the Windows component that translates file requests over the network. When you access a file on a mapped drive or send a print job to a network printer, Windows opens a handle through the redirector. If any of those handles are still active, Windows refuses to unload the redirector. It's a safety feature—it prevents data corruption. But it's also a pain when you need to clean up.

Common triggers:

Excel, Word, or AutoCAD has a file open on the mapped drive.
A print job is stuck in the queue on a network printer.
A command prompt or PowerShell session still has the network location as its current directory.
A backup or antivirus scan is actively accessing the share.

Fix It: Step-by-Step

Skip the reboot if you can. Here's the real fix work for 9 out of 10 cases.

Step 1: Kill Open File Handles

Open Computer Management (right-click This PC → Manage). Go to System Tools → Shared Folders → Open Files. Look for files from the problematic network location. Right-click and close them. If you don't see any, move on.

Step 2: Force Unmount with net use

Open Command Prompt as admin. Run:

net use * /delete /y

This disconnects all mapped drives. If it succeeds, the error is gone. If it fails, note which drive didn't disconnect—that's your culprit.

Step 3: Kill Stuck Processes

Open Task Manager. Look for any process that might be using the network drive. Common ones: explorer.exe, OUTLOOK.EXE, WINWORD.EXE, taskhostw.exe. End them one by one. After each, try the net use command again. For explorer.exe, restart it after you're done.

Step 4: Clear the Print Queue

If a network printer is involved, go to Control Panel → Devices and Printers. Right-click the printer, choose See what's printing, and cancel all jobs. If that won't work, stop the Print Spooler service (net stop spooler in admin cmd), delete the stuck jobs from C:\Windows\System32\spool\PRINTERS, then start it again (net start spooler).

Step 5: Use Handle Tool (Advanced)

Download Handle from Sysinternals. Run:

handle.exe -a -p explorer.exe | find /i "\\server"

Replace \server with your target server name. If you see open handles, note the PID and handle value. Then close them with:

handle.exe -c [handle_value] -p [PID] -y

This is nuclear. Be sure you're not closing something critical.

If It Still Fails

You've tried everything above and the error persists? Then you're looking at a deeper issue. Check these:

Registry locks: Open Regedit, go to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2. Delete the subkey for the problematic drive. This removes the cached connection.
Services hanging: Restart the Workstation service (net stop LanmanWorkstation, then net start LanmanWorkstation). This will kill all network connections momentarily.
Third-party software: I've seen backup agents (Veeam, Acronis) and cloud sync tools (OneDrive, Dropbox) hold handles. Disable them temporarily.
Reboot is your last resort: If none of this works, restart the machine. It's ugly, but it works every time.

One more thing: if you're on a domain, check with your admin—group policy might be mapping drives at login, and you can't remove them permanently without policy changes. That's a different problem, but it'll give you the same error.