sodcalculator

10 Tech How-To

Fix 0x80004005 SMB Unspecified Error in Windows

Guide 10-57991 · Updated · Step by step

This guide walks you through fixing the Windows SMB (Server Message Block) error 0x80004005, which typically appears when trying to access a shared folder or network drive and is labeled as an “Unspecified error.” The fix usually involves adjusting security policies, clearing cached credentials, or modifying registry settings. No special tools are required beyond administrative access to your Windows PC.

What You’ll Need

  • Administrator account on your Windows PC
  • Access to the shared resource’s host computer (if you need to change its settings)
  • Knowledge of the shared folder’s network path (e.g., \\server\share)

Step-by-Step

  1. Check if SMB is enabled. Open the Start menu, type Windows Features, and select “Turn Windows features on or off.” Scroll to “SMB 1.0/CIFS File Sharing Support” and ensure it’s checked. For most modern networks, you only need SMB 1.0 if you’re connecting to older devices (like Windows 7 or some NAS units). If it’s already enabled, leave it as is; if not, enable it and restart your PC.
  2. Verify the network discovery and file sharing settings. Go to Settings > Network & Internet > Network and Sharing Center > Advanced sharing settings. Under “Private” (or “All Networks”), ensure “Turn on network discovery” and “Turn on file and printer sharing” are both selected. Save changes.
  3. Clear cached credentials. Open the Start menu, type Credential Manager, and open it. Under “Windows Credentials,” look for any entries related to the server or IP address you’re trying to access. Click the arrow next to the entry and select “Remove.” Then try connecting again—Windows will prompt for fresh credentials.
  4. Reset the SMB connection. Open Command Prompt as Administrator (right-click Start > Command Prompt (Admin) or Windows PowerShell (Admin)). Type net use * /delete and press Enter. This disconnects all existing SMB sessions. Then reconnect to the share manually by typing net use Z: \\server\share (replace Z: with a drive letter and the path with your actual share).
  5. Adjust the Local Security Policy. Press Win + R, type secpol.msc, and press Enter. Navigate to Local Policies > Security Options. Look for “Network security: LAN Manager authentication level.” Double-click it and set it to “Send LM & NTLM – use NTLMv2 session security if negotiated.” If that doesn’t help, try “Send NTLMv2 response only.” Click OK and restart the PC.
  6. Edit the registry to allow insecure guest logons (if needed). If the error occurs when connecting to a device that uses guest access (like some NAS drives), press Win + R, type regedit, and press Enter. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters. Create a new DWORD (32-bit) value named AllowInsecureGuestAuth and set its value to 1. Close the registry and restart.
  7. Check the host computer’s firewall. On the computer hosting the share, ensure that “File and Printer Sharing” is allowed through Windows Defender Firewall. Go to Control Panel > Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall. Find “File and Printer Sharing” and check both Private and Public boxes. If it’s not listed, click “Allow another app” and add it from C:\Windows\System32\fswshare.exe (or search for it).
  8. Restart the SMB services. On the client PC, open Services (Win + R, type services.msc). Find “Server” and “Workstation” services. Right-click each and select “Restart.” This can resolve temporary glitches.
  9. Try a different access method. Instead of using the UNC path (\\server\share), map the network drive via File Explorer. Right-click “This PC” > “Map network drive,” choose a drive letter, enter the path, and check “Connect using different credentials.” This sometimes bypasses the error.
  10. Disable IPv6 temporarily (if all else fails). In Network Connections (Control Panel > Network and Sharing Center > Change adapter settings), right-click your active adapter, select Properties, uncheck “Internet Protocol Version 6 (TCP/IPv6)”, and click OK. Restart the PC and try again. If it works, you can leave it disabled or re-enable it after the connection is established.

Common Mistakes

  • Enabling SMB 1.0 unnecessarily. SMB 1.0 is outdated and insecure; enabling it can cause more problems. Only enable it if you’re connecting to a legacy device that requires it.
  • Editing the registry without backing up. Always export the registry key before making changes so you can revert if something goes wrong.
  • Forgetting to restart after policy changes. Many security policy and registry changes require a full restart to take effect.
  • Assuming the error is on the client only. The problem could be on the server side (e.g., SMB disabled, firewall blocking). Check both ends.
  • Using the wrong authentication level. Setting the LAN Manager authentication level too high or too low can cause mismatches. Start with the recommended setting and adjust gradually.

Tips

  • Always use the IP address instead of the hostname if the error persists—DNS issues can cause this error.
  • If you’re on a domain, check with your network administrator—Group Policy might be overriding local settings.
  • Keep Windows updated. Microsoft regularly patches SMB-related bugs that can cause this error.
  • For temporary access, you can try using the IP address in the path (e.g., \\192.168.1.10\share) to rule out name resolution issues.
  • If the share requires a specific user account, make sure you’re typing the credentials in the format DOMAIN\username or COMPUTERNAME\username.

Troubleshooting

If the error persists after trying all the steps above, consider these additional checks:

  • Check the SMB protocol version. Windows 10/11 supports SMB 3.1.1 by default. If the server only supports SMB 1.0, you may need to enable it on the client (Step 1) but also ensure the server has it enabled.
  • Look at the event logs. Open Event Viewer (Win + R, type eventvwr). Under “Windows Logs > System,” look for errors with source “SMBClient” or “MrxSmb.” The details may give a more specific reason.
  • Test with a different device. Try accessing the same share from another PC or phone. If it works, the issue is isolated to your Windows settings. If it fails, the server is likely the problem.
  • Run the Windows Network Diagnostics. Right-click the network icon in the system tray and select “Troubleshoot problems.” This can sometimes automatically detect and fix connectivity issues.
  • Check for third-party security software. Antivirus or firewall software can block SMB traffic. Temporarily disable them (if safe) to test.
  • Consider a network reset. As a last resort, go to Settings > Network & Internet > Status > Network reset. This reinstalls network adapters and resets all network settings. You’ll need to reconnect to Wi-Fi and re-enter passwords.

Frequently Asked Questions

What exactly is the 0x80004005 SMB error?

It’s a generic Windows error code that means “Unspecified error.” In the context of SMB, it usually indicates a failure in the network communication between your PC and the shared resource, often due to authentication or protocol mismatches.

Is this error a sign of a security breach?

No, it’s typically a configuration or compatibility issue. It doesn’t indicate that your system is compromised, but you should still keep your system updated to avoid real vulnerabilities.

Do I need to enable SMB 1.0 to fix this?

Only if you’re connecting to a very old device (like a Windows XP machine or an older NAS). For modern devices, SMB 2/3 is sufficient and more secure. Enabling SMB 1.0 is not recommended unless absolutely necessary.

Can this error occur on Windows 11 as well?

Yes, the error can appear on any Windows version that supports SMB, including Windows 11. The steps above apply to both Windows 10 and 11.

Why does the error happen only sometimes?

Intermittent errors often point to network instability, IP address conflicts, or the server being busy. Try pinging the server to check latency and packet loss. Also, ensure the server’s IP address hasn’t changed.

Will resetting my network fix the problem?

It can, but it’s a drastic step that removes all your network adapters and settings. Try the other steps first, and only use network reset as a last resort.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →