Fix Can’t Map a Drive in Windows 10 v2004

If you’re on Windows 10 version 2004 and can’t map a network drive, the fix usually involves updating the SMB signing policy or adjusting your network discovery settings. This article walks you through the most common causes and step-by-step solutions, including registry tweaks and Group Policy changes.

Background: What Changed in Windows 10 v2004

Windows 10 version 2004 (May 2020 Update) introduced a stricter default for SMB (Server Message Block) signing. Microsoft made SMB signing mandatory by default for client connections to improve security. However, this change broke many existing network drive mappings, especially when connecting to older NAS devices, routers with built-in storage, or Linux servers that don’t support SMB signing. If your network device only supports SMB1 or SMB2 without signing, Windows 10 v2004 may refuse the connection entirely, showing errors like “The network drive could not be found” or “Access denied.”

Common Symptoms and Error Messages

Users typically see one of these when trying to map a drive:

• “Windows cannot find the network path”
• “The network name cannot be found”
• “Access is denied” even with correct credentials
• “The mapped network drive could not be created”
• Drive disconnects after reboot, requiring re-mapping

These errors can appear immediately or after a reboot, and they affect both File Explorer’s “Map network drive” wizard and the net use command.

Fix 1: Enable SMB Signing on the Client (Registry Method)

The most direct fix is to disable the SMB signing requirement on your Windows 10 client. This is safe for home networks but not recommended for high-security environments.

1. Press Win + R, type regedit, and press Enter.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters.
3. Look for the DWORD value RequireSecuritySignature. If it doesn’t exist, create it (right-click > New > DWORD (32-bit)).
4. Set its value to 0 (zero).
5. Restart your PC.

After the restart, try mapping the drive again. This change tells Windows to not require SMB signing, allowing connections to devices that don’t support it.

Fix 2: Disable SMB Signing via Group Policy

If you’re on Windows 10 Pro, Enterprise, or Education, you can use Group Policy instead of the registry.

1. Press Win + R, type gpedit.msc, and press Enter.
2. Navigate to Computer Configuration > Administrative Templates > Network > Lanman Workstation.
3. Double-click Enable insecure guest logons and set it to Enabled.
4. Also double-click Microsoft network client: Digitally sign communications (always) and set it to Disabled.
5. Close Group Policy and run gpupdate /force in Command Prompt (as admin).

Note: The “Enable insecure guest logons” setting is often required for older NAS devices that use guest access. If your device uses a username/password, you may only need to disable the signing requirement.

Fix 3: Check Network Discovery and Advanced Sharing Settings

Sometimes the issue isn’t SMB signing but network discovery being turned off. This is common after a fresh install or update.

1. Open Control Panel > Network and Sharing Center > Advanced sharing settings.
2. Under Private (or your current network profile), turn on Network discovery and File and printer sharing.
3. Also enable Turn on automatic setup of network connected devices if available.
4. Save changes and try mapping again.

If you’re on a public network, Windows blocks network discovery by default. Switch to a private network profile via Settings > Network & Internet > Wi-Fi/Ethernet > your connection > Properties.

Fix 4: Use IP Address Instead of Hostname

If you’re using a hostname (like \\MyNAS\Share), try the IP address instead (e.g., \\192.168.1.10\Share). This bypasses DNS and NetBIOS resolution issues that can occur after the v2004 update. To find the IP of your NAS or server, check its admin panel or use a network scanner. If the IP works, the problem is name resolution. You can add a static entry in the hosts file (C:\Windows\System32\drivers\etc\hosts) to map the hostname to the IP permanently.

Fix 5: Re-enable SMB1 (Not Recommended)

Some very old devices only support SMB1, which is disabled by default in Windows 10 v2004. You can enable it via Windows Features, but this is strongly discouraged because SMB1 is insecure and vulnerable to ransomware attacks like WannaCry. Only do this if you have no other option and the device is isolated on a trusted network.

1. Open Control Panel > Programs > Turn Windows features on or off.
2. Check SMB 1.0/CIFS File Sharing Support.
3. Click OK and restart.

After enabling, try mapping again. If it works, consider upgrading your device’s firmware or replacing it.

Frequently Asked Questions

Why did my mapped drive stop working after updating to v2004?

The update changed SMB signing requirements, making Windows refuse connections to devices that don’t support signing. This is a security improvement, but it breaks older hardware. The registry fix above restores compatibility.

I’m getting “Access denied” even with correct credentials. What’s wrong?

This often means the device requires guest access but Windows has guest logons disabled. Enable “Insecure guest logons” via Group Policy (Fix 2) or check your NAS’s sharing settings to allow guest access.

Can I map a drive using the command line instead of File Explorer?

Yes. Use net use Z: \\server\share /user:username password /persistent:yes. This can sometimes bypass GUI issues. If the command fails, the error message may give more detail.

Will these fixes affect my security?

Disabling SMB signing reduces protection against man-in-the-middle attacks. On a home network with trusted devices, the risk is low. For corporate networks, consult your IT department before making these changes.

My drive maps but disconnects after reboot. How do I keep it persistent?

In File Explorer, make sure you check “Reconnect at sign-in” when mapping. If it still drops, run net use Z: /persistent:yes after mapping. Also check your NAS’s power settings—it may be sleeping.

Why can I see the share in Network but can’t map it?

This usually indicates a permission issue or SMB signing mismatch. Try accessing the share directly by typing its UNC path in File Explorer’s address bar. If that works, the mapping wizard might be using a different credential set.

Related

• Why Is iPhone Texting Green to Another iPhone? Fix It
• How to Record Guitar on PC with Reaper DAW
• Outlook 0x80004005 Error: Fix the Operation Failed