NERR_ShareNotFound (0X00000958) Fix: Shared Resource Not Found

The 30-Second Fix: Reconnect Your Mapped Drive

This error pops up when your PC tries to reconnect a mapped network drive, but that share isn't available. It's usually a temporary glitch—maybe the server rebooted, or your VPN dropped for a second.

1. Open File Explorer. You can press Windows + E or just click the folder icon on your taskbar.
2. Look at the left sidebar under "This PC." You'll see a drive letter with a red X or a disconnected icon next to it. That's your problem.
3. Right-click that mapped drive and select Disconnect.
4. Now go to the toolbar at the top of File Explorer. Click the three dots (...) and pick Map network drive.
5. Pick the same drive letter that was failing. In the "Folder" box, type the full network path. Something like \ServerName\SharedFolder.
6. Check the box that says Reconnect at sign-in. Leave the other boxes unchecked.
7. Click Finish. You might need to enter a username and password—use the credentials that have access to that share.

What you should see: After you click Finish, the drive should show up under This PC with a normal drive icon. No red X. Try opening it—you should see the files inside.

If this worked, you're done. If the error comes back, move on to the next fix.

The 5-Minute Fix: Check Network Discovery and SMB Settings

Sometimes Windows just forgets it's supposed to talk to other computers. Let's wake it up.

Step 1: Turn on Network Discovery

1. Open Control Panel. Press Windows + R, type control, and hit Enter.
2. Click Network and Sharing Center.
3. On the left side, click Change advanced sharing settings.
4. Make sure Turn on network discovery is selected. Also check Turn on file and printer sharing.
5. Click Save changes. You might get a UAC prompt—click Yes.

What you should see: After saving, go back to File Explorer and click "Network" in the left sidebar. You should see other computers listed. If you don't, your network profile might be set to Public. That's fine—just know that Public networks block discovery by default.

Step 2: Make Sure SMB 1.0 Isn't Messing Things Up (Yes, It's Still a Thing)

Windows 10 and 11 disable SMB 1.0 by default. Good. But if your file server is ancient—like a Windows 7 or an old NAS from 2010—it might need SMB 1.0. I've seen this on a Synology DS212j. Here's how to check:

1. Press Windows + R, type optionalfeatures, and hit Enter.
2. Scroll down to SMB 1.0/CIFS File Sharing Support. If it's unchecked, leave it unchecked. If it's checked, uncheck it and restart.
3. For most setups, you don't need SMB 1.0. It's old, slow, and insecure. If your server is modern (Windows 10 or newer, or a NAS from the last 8 years), SMB 2 or 3 is what you want.

What you should see: After restarting, try re-mapping the drive using the 30-second fix above. If the error stays, move to the next step.

The 15+ Minute Fix: Deep Clean Mapped Drive Credentials and Registry

This is for when the drive disconnects every time you restart. The problem is often stale credentials stored by Windows. Let's nuke them.

Step 1: Clear Saved Credentials in Credential Manager

1. Open Control Panel. Type credential in the search box and click Credential Manager.
2. Click Windows Credentials.
3. Look under "Generic Credentials" for anything that matches your file server. They'll look like TERMSRV/ServerName or MicrosoftAccount:user@domain.com or just the server IP.
4. Click the arrow to expand each one, then click Remove. Confirm when asked.
5. Close Credential Manager.

What you should see: After removing them, restart your PC. Then re-map the drive using the 30-second fix. This time, enter the credentials fresh. Don't check "Remember my credentials"—I know it's tempting, but that's what causes this mess.

Step 2: Delete Stale Mapped Drive Registry Keys (Only If You're Comfortable)

If step 1 didn't work, there's a registry key that keeps trying to reconnect drives even after you disconnect them. I've seen this on Windows 10 22H2 and Windows 11 23H2.

1. Open Registry Editor. Press Windows + R, type regedit, and hit Enter.
2. Navigate to this key:
   HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2
3. Under MountPoints2, you'll see subkeys with names like ##ServerName#SharedFolder. Those are your stale network shares.
4. Right-click each one that matches your failing drive and choose Delete. Confirm.
5. Close Registry Editor and restart your PC.

What you should see: After restart, the mapped drive should be completely gone from File Explorer. Now re-map it using the 30-second fix. If you still get the error, the problem is on the server side—talk to your network admin.

One Last Thing: The Server Might Be Down

I've spent an hour troubleshooting a "shared resource not found" error only to discover the file server had a dead power supply. Before you go too deep, test the server directly.

1. Open Command Prompt. Press Windows + R, type cmd, and hit Enter.
2. Type ping ServerName (replace ServerName with the actual server name).
3. If you get replies, the server is alive. If you get "Request timed out," the server or network is down.
4. Also try net view \\ServerName. If you get an error there, the server isn't sharing anything—or your credentials are wrong.

What you should see: A successful ping shows replies with times in milliseconds. A successful net view shows a list of shared folders.

If the server is down, you're not fixing this from your desk. Call your IT team. But if the server is up and you still get error 0X00000958, the fixes above will sort you out. Start with the 30-second fix. It works for about 70% of cases I've seen.