Fix 0XC0000480 STATUS_SHARE_UNAVAILABLE: Quick Steps

Quick Fix: Reconnect the Share (30 seconds)

This error usually means Windows lost the connection to a shared folder, often a mapped drive. Let's force a fresh connection.

1. Open File Explorer (Win + E).
2. Right-click the mapped drive or the network location that shows the error.
3. Select Disconnect.
4. Wait 10 seconds.
5. Now map it again: right-click This PC in the left pane and choose Map network drive.
6. Pick the same drive letter, type the full path (e.g., \server\sharedfolder), check Reconnect at sign-in, and click Finish.

After clicking Finish, you should see the drive appear under This PC. Try opening it. If it works, you're done. If not, move to the next step.

Moderate Fix: Check Network and SMB Settings (5 minutes)

Sometimes the share is fine, but your network connection hiccupped. Let's verify the basics.

Test the connection

1. Press Win + R, type cmd, and press Enter.
2. Type ping [server IP or name] and press Enter.

If you get replies, good. If you get timeout or unreachable, that's your problem. The server isn't reachable from your PC. Check your Wi-Fi or Ethernet cable.

Ensure SMB is enabled

Windows 10 and 11 sometimes disable older SMB versions. If the server is older (like Windows Server 2008 or a NAS), you might need SMB 1.0. But only enable it if you know the server needs it—it's insecure.

1. Open Control Panel (search for it in the Start menu).
2. Go to Programs > Turn Windows features on or off.
3. Scroll down to SMB 1.0/CIFS File Sharing Support.
4. Check the box for SMB 1.0/CIFS Client only.
5. Click OK and restart if prompted.

After restart, try connecting again. If you still see the error, the issue might be on the server side or with credentials.

Advanced Fix: Flush DNS, Reset Network Stack, and Check Credentials (15+ minutes)

If we're here, the quick and moderate fixes didn't help. Let's go deeper. You'll need admin rights for these commands.

Flush DNS and reset TCP/IP

1. Right-click Start and choose Windows Terminal (Admin) or Command Prompt (Admin).
2. Run these commands one by one, pressing Enter after each:

ipconfig /flushdns
ipconfig /registerdns
netsh int ip reset
netsh winsock reset

After the last command, restart your PC. You'll see a lot of output, that's normal. After restart, try the share again.

Clear stored credentials

Sometimes Windows cached an old password and it's using that instead of the current one. Let's clear it.

1. Open Control Panel > Credential Manager.
2. Click Windows Credentials.
3. Look for anything under Generic Credentials that matches your server or share name.
4. Click the arrow to expand, then Remove.
5. Reconnect to the share when you try it again.

You'll be asked for your username and password when you reconnect. Use the correct one.

Check the server side

If you're the admin for the server, check if the share is actually available. On the server, open Computer Management > Shared Folders > Shares. See if your shared folder is listed. If not, create it again. Also check the server's event log for disk errors—a failing drive can cause a share to become temporarily unavailable.

Last resort: Change your network profile

Some users report that switching from private to public network and back fixes it, but that's rare. Skip it unless you're desperate.

If none of this works, the share itself might have a problem—like the server is out of disk space or the folder was deleted. Contact whoever manages that server.

When to stop

Try the reconnect first. Most people fix it in 30 seconds. The network checks handle the next batch. The advanced steps are for persistent issues. You shouldn't need to go past resetting winsock unless you're dealing with a broken server.

Remember: this error is temporary by definition. If it keeps coming back, there's an underlying issue—likely a flaky network or a server that's going offline. Watch your Wi-Fi signal or run a constant ping to the server for a few minutes to see if it drops.