If your mapped network drives stop working or show a red X after updating to Windows 10 version 1809, the fix is to adjust Group Policy settings or registry values for the “Enable linked connections” option, and then reconnect the drives. This article explains why the October 2018 Update broke mapped drives, how to apply the permanent fix, and what to do if the problem persists.
Why Windows 10 v1809 Broke Mapped Drives
Windows 10 version 1809 (the October 2018 Update) introduced a security change that affects how Windows handles credentials for mapped network drives. Prior to this update, Windows automatically used the same session for both the network logon and the drive mapping, which allowed drives to reconnect silently in the background. Starting with v1809, Windows separates the administrative session from the user session by default, so mapped drives that rely on cached credentials or that are mapped with “different credentials” often fail to reconnect at sign-in.
This is not a bug in the traditional sense—Microsoft deliberately hardened the behavior to reduce credential theft (the “Pass-the-Hash” attack vector). But it broke a common workflow for many users, especially those in small offices or home networks who map drives to NAS devices or shared folders on other PCs.
How Mapped Drives Work in Windows 10
When you map a network drive (for example, Z: pointing to \\Server\Share), Windows stores the mapping in the registry under HKEY_CURRENT_USER\Network. At sign-in, Explorer tries to reconnect each mapped drive. For this to work silently, Windows must have a valid session with the remote server. If the server requires credentials and Windows cannot supply them automatically (because the session is not yet established), the drive shows as disconnected with a red X.
Windows 10 v1809 changed the default behavior of the Enable linked connections policy. This policy controls whether Windows shares the same network connection for the logged-on user and for the elevated (admin) session. When disabled (the default in v1809), Windows may not pass the user’s credentials to the drive mapping process, especially if you are using a Microsoft account or if the server is not part of an Active Directory domain.
The Permanent Fix: Enable Linked Connections
The most reliable fix is to enable the “Enable linked connections” policy. This restores the pre-1809 behavior for all users on the machine. Here are the steps:
- Press Win + R, type
gpedit.msc, and press Enter. (If you have Windows 10 Home, skip to the registry method below.) - Navigate to Computer Configuration > Administrative Templates > System > Logon.
- Double-click Enable linked connections.
- Set it to Enabled, then click OK.
- Restart the computer.
After restarting, open File Explorer and manually reconnect any mapped drives that show as disconnected. Right-click the drive, choose Disconnect, then map it again using the same drive letter and path. From now on, the drive should reconnect automatically at sign-in.
Registry Method for Windows 10 Home
Windows 10 Home does not include the Group Policy Editor. You can achieve the same result by editing the registry:
- Press Win + R, type
regedit, and press Enter. - Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System. - If the System key does not exist, create it.
- Right-click in the right pane, select New > DWORD (32-bit) Value.
- Name it
EnableLinkedConnections. - Set the value to
1(decimal). - Click OK and close the registry editor.
- Restart the computer.
After the restart, reconnect the mapped drives as described above. The registry change has the same effect as the Group Policy setting.
Other Common Causes and Quick Checks
If the linked connections fix does not solve the problem, check these common issues:
- Credential Manager: Open Control Panel > Credential Manager and remove any stale credentials for the server. Then remap the drive with “Connect using different credentials” and check “Remember my credentials”.
- Drive letter conflict: Make sure the drive letter you are using is not already assigned to a local disk or a removable drive. Change the letter in Disk Management if needed.
- Network discovery: Ensure that network discovery and file sharing are turned on for the network profile (Private, not Public). Go to Control Panel > Network and Sharing Center > Advanced sharing settings.
- Server availability: If the server is a NAS or a PC that sleeps, the drive may not reconnect because the server is unreachable at sign-in. Set the server to never sleep or use a scheduled task to reconnect the drive after boot.
- Group Policy refresh: After changing the policy, run
gpupdate /forcein an elevated Command Prompt to apply it without a restart (though a restart is still recommended).
Using a Scheduled Task as a Workaround
If you cannot change Group Policy or the registry (for example, on a managed corporate machine), you can create a scheduled task that runs at logon and reconnects the drives. This is a workaround, not a fix, but it works reliably.
- Open Task Scheduler and click Create Task.
- Under the General tab, name it “Reconnect Mapped Drives”.
- Check Run whether user is logged on or not and Run with highest privileges.
- Under Triggers, add a trigger at Log on for your user account.
- Under Actions, add a new action: Start a program.
- In the Program/script field, type
powershell.exe. - In the Add arguments field, paste the following (replace the drive letter and UNC path with your own):
-Command "New-SmbMapping -LocalPath 'Z:' -RemotePath '\\Server\Share' -Persistent $true" - Click OK and test by logging off and back on.
This command re-establishes the SMB mapping at logon, even if Explorer fails to do so. It is especially useful if you cannot modify the registry or policy.
Frequently Asked Questions
Why do my mapped drives show a red X even after I click on them?
The red X means the drive is not currently connected. Clicking on it may trigger a reconnect attempt, but if the credentials are not cached or the session is blocked, it will fail. Enabling linked connections or using the scheduled task usually resolves this.
Will this fix affect my security?
Enabling linked connections slightly reduces the security boundary between the user and admin sessions. For most home and small business users, the risk is minimal. If you are in a high-security environment, consult your IT department before making the change.
I have Windows 10 Home; can I still use Group Policy?
No, Windows 10 Home does not include the Group Policy Editor. Use the registry method described above, which works identically.
Do I need to remap all my drives after the fix?
Yes, it is recommended to disconnect and remap each drive once after the fix. This ensures the mapping is stored with the correct settings for the new behavior.
What if the fix still doesn’t work?
If the drives still fail, try mapping the drive using the IP address instead of the hostname (e.g., \\192.168.1.10\share). This avoids DNS or NetBIOS resolution issues. Also, check that the server’s firewall allows SMB traffic (port 445).
Is there a way to make the drive reconnect without any fix?
You can try using the net use command in a startup script, but that is essentially the same as the scheduled task workaround. The linked connections policy is the only true fix for the v1809 change.
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
- Show User Library in macOS High Sierra & Sierra
- Device Manager Shortcut: Windows 10 Desktop
- How to Remove Forgotten Passcode from iPhone
- Fix Slow Wi-Fi Problem iPhone X: 9 Steps
- How to Check if a Candidate Accepts Crypto Donations
- How to Listen to Deleted Voicemails on iPhone