Fix 0X000008B1: NERR_ResourceExists Already Exists

Quick Answer (for the impatient)

Open Command Prompt as admin, run net share deleteme /delete if you have a dummy share, then net share OldShare /delete for the real one, and recreate it. The error means the permission list entry is stuck in memory.

Why This Happens

I know this error is infuriating. It usually hits you when you're setting up a network share on a Windows 10 or 11 Pro machine—maybe after a reboot or after you've manually edited share permissions. The system already has a resource permission list entry for that share name, even though the share itself might not exist in File Explorer. This is a leftover from a previous share creation that didn't clean up properly, often after a disconnected session or a failed reboot.

The error code 0X000008B1 maps to NERR_ResourceExists (Network Error Resource Exists). It means the internal list of share permissions—stored in the registry under HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares—already contains an entry for that resource name. The OS is trying to be helpful but instead blocks your new share.

Fix Steps (the main fix)

1. Open Command Prompt as Administrator. Press Win+X, click "Terminal (Admin)" or "Command Prompt (Admin)" depending on your Windows version. Yes, you need admin rights.
2. List all current shares by typing net share. Look for your problematic share name. If it's there, skip to step 3. If it's not there, the stale entry is in the hidden permission list.
3. Delete the share with net share YourShareName /delete. Replace YourShareName with the actual name from step 2. If the share doesn't exist in net share output but still throws the error, jump to step 4.
4. Clear the registry key – this is where the ghost lives. Open Regedit (Win+R, type regedit).
   Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares. Find the key named exactly after your share (e.g., MyShare). Right-click it and delete. Be careful—don't delete the whole Shares key, just the entry for your problem share.
5. Reboot or restart the Server service. In Command Prompt (Admin), run net stop lanmanserver && net start lanmanserver. This flushes the in-memory permission list.
6. Recreate the share using net share MyShare=C:\Path /grant:Everyone,Full or through File Explorer. Should work now.

Alternative Fixes (if the main one fails)

Use PowerShell instead

If net share doesn't show the ghost, try PowerShell as admin: Get-SmbShare to list shares, then Remove-SmbShare -Name "YourShareName" -Force. This sometimes catches entries the old command misses.

Check for orphaned file locks

Sometimes the error hides behind an open file handle. Run net file to see active locks. If you see your share's path, close it with net file ID /close (replace ID with the number from the list). Then delete and recreate.

System Restore as a last resort

If you've been messing with permissions and the share still won't budge, a System Restore to a point before the share was created can wipe the stale entry. Go to Control Panel > Recovery > Open System Restore. Pick a date before the error first appeared.

Prevention Tip

To dodge this in the future, always delete a share through the proper channels. Don't just delete the folder or rename it. Use net share or the Sharing tab in File Explorer to remove it. If you're scripting share creation, always delete any existing share with the same name first—even if you think it doesn't exist—using net share OldName /delete 2>nul. That little 2>nul suppresses the "doesn't exist" error and stops the ghost from forming.

This tripped me up the first time I inherited a file server with a hundred shares. Now I always check the registry before creating new ones. Saves you the headache.