Fix net use error 0X000008CA connection not found

You get this error when Windows can't find a saved network drive mapping. The fix is usually removing stale credentials or remapping. Takes 30 seconds to 15 minutes.

What actually causes error 0X000008CA

You're trying to run a batch script or just double-click a mapped drive, and Windows throws back 0X000008CA (NERR_UseNotFound). The short version: Windows lost track of the drive mapping. It's not that the network share is gone — it's that the saved mapping is corrupted, stale, or points to a credential that doesn't exist anymore.

I see this most often when someone changed their domain password, or they're running a script that expects a drive letter that's already in use by something else. Also happens after a VPN disconnect if the mapping didn't clean up. Don't overthink it.

The 30-second fix: check and retype

Open Command Prompt as admin. Type this and hit Enter:

net use

Look at the list. See any drives with the status "Unavailable" or "Disconnected"? That's your culprit. The drive letter is reserved but the path is broken.

Next, delete that mapping:

net use X: /delete

Replace X with your actual drive letter. If it asks for confirmation, type Y and Enter. Then remap the drive:

net use X: \\server\share /persistent:yes

Test the drive. If it works, you're done. 90% of the time this is all you need.

The 5-minute fix: clean credential manager

If the quick fix didn't work, the saved credentials are probably garbage. Windows stores network passwords in Credential Manager, and they can get out of sync. Here's how to nuke them:

Open Control Panel, then click User Accounts > Credential Manager.
Click Windows Credentials.
Look under Generic Credentials for anything that mentions your server name or IP address. They'll look like TERMSRV/server or just \\server.
Click the arrow to expand, then Remove. Yes, remove all of them for that server.

After that, open Command Prompt and run the net use delete command again for any leftover mappings. Then remap fresh:

net use X: \\server\share /user:DOMAIN\username *

It'll prompt for a password. Enter your current one. That saves the new credential cleanly.

One real-world example: I had a user who changed their password, but the old hash was still in Credential Manager. Every time they logged in, Windows tried the old password — error 0X000008CA. Removing the credential and remapping fixed it instantly.

The 15+ minute fix: registry clean and group policy check

If you're still stuck, something deeper is wrong. Could be a corrupted registry entry for the mapping, or Group Policy is fighting you. Let's check both.

Registry cleanup

Run regedit as Admin. Navigate to:

HKEY_CURRENT_USER\Network\X

Replace X with your drive letter. If that key exists, delete it. Then also check:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2

Look for any subkeys referencing the same server or share. Delete those too. Close regedit.

Reboot your PC. Then remap the drive fresh using the net use command from earlier.

Group Policy override

If you're on a company network, your IT team might have a Group Policy that maps drives automatically. That policy can conflict with your manual mappings. To check:

Open Command Prompt as admin and run gpresult /H C:\gpresult.html.
Open that HTML file in a browser.
Look under Computer Configuration > Administrative Templates > Network > Network Provider for any drive mapping policies.
If you see one, you can't override it easily — you need to talk to your IT team. But you can work around it by mapping to a different drive letter that the policy doesn't touch.

I've also seen cases where the network share itself needs the SMB1 protocol disabled (it's a security risk anyway). Check with your server admin that SMB2 or SMB3 is enabled on the file server. If it's an old NAS, that might be your root cause.

When to skip all this and just reboot

Honestly, sometimes a full reboot is faster than poking around. If you've tried the first two steps and it's still broken, save your work, restart the PC, and test the mapping again. I've wasted 20 minutes on registry edits only to realize a reboot would've fixed a stuck network service.

Prevent it from coming back

Always use /persistent:yes when mapping with net use.
Don't map drives using IP addresses if the server's name works — names survive DHCP changes better.
If you change your domain password, delete and recreate your mapped drives the same day.
Avoid mapping drives in logon scripts that run before the network is fully ready. Add a timeout /t 5 at the start of the script.

That's it. Error 0X000008CA is annoying but not scary. Start with the 30-second fix, move to credential manager, and only dig into the registry if you have to. You'll be back online in under 10 minutes.