About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Users sign in and their mapped drives show a red X. Sometimes the drive opens when they click it. Sometimes it does not, or it is missing altogether. Microsoft documents several different causes behind the same red X, and each has a different fix. The first job is to work out which one you have.
What you see
Microsoft lists these symptoms on its mapped-drive reconnect page (Microsoft Learn, Mapped network drive may fail to reconnect in Windows 10, version 1809):
- A red X on the mapped drives in File Explorer.
net useat a command prompt shows the drives as Unavailable.- A notification: Could not reconnect all network drives.
Related symptoms on other Microsoft pages:
- The drive shows a red X after a period of not being used, but opens quickly when you browse to it.
- The drives work in File Explorer but are missing in an elevated (run as administrator) command prompt or program.
- Drives the user mapped by hand are gone after the next sign-in, or only some of the Group Policy drive maps appear.
Why it happens
1. The connection was idle and was dropped. Microsoft says systems can drop idle connections after a time-out (15 minutes by default on the server side) to avoid wasting server resources. File Explorer then shows a red X, but the drive reconnects quickly when it is opened (Microsoft Learn, Mapped drive connection to network share may be lost). The page also describes a client-side value, KeepConn (default 600 seconds), and says the session drops at whichever of the two time-outs is shorter. That page is written for Windows 7 SP1 and Windows Server 2012 R2.
2. The network was not ready when the drives tried to reconnect. Microsoft's reconnect workaround for Windows 10 version 1809 is a script that runs at sign-in. The page notes that the startup version "works only for the device that has network access at logon", and its scheduled-task versions wait for a network connection, or for a VPN connection to come up. It follows that a drive cannot reconnect at sign-in if the device has no network path to the server yet, such as a laptop before its VPN connects.
3. Windows 10 version 1809 had a known reconnect fault. The same page describes a specific issue in Windows 10 version 1809 with these symptoms. It is an older page written while a fix was pending, and it applies to that version only.
4. The program is running elevated. When User Account Control (UAC) is on, Windows creates two linked sign-in sessions for an administrator. Drive mappings belong to a single session. Microsoft documents a case where drives mapped by Group Policy Preferences (GPP) or a logon script are missing from an elevated prompt, when the UAC elevation prompt for administrators is set to Prompt for credentials (Microsoft Learn, Mapped drives are not available from an elevated prompt). The reconnect page makes the same point from the other side: scripts run elevated create mappings that are not available to the standard user.
5. A Group Policy drive map clears other drives. In a GPP Drive Map item, the setting Use first available, starting at clears all mapped drives from that letter through Z. Microsoft says this is by design. With more than one GPP drive map policy applied, only some of the drives may appear (Microsoft Learn, Group Policy Preferences removes manual drive mappings).
6. Group Policy did not apply at all. If the drive maps come from Group Policy and policy processing failed, the drives are not mapped. Microsoft's Group Policy guidance describes Event ID 1129, logged when Group Policy fails because of a lack of network connectivity to a domain controller (Microsoft Learn, Applying Group Policy troubleshooting guidance).
How to prove the cause
1. Look at the state, not just the icon. At a normal (not elevated) command prompt:
net use
In PowerShell, Microsoft's reconnect script uses this cmdlet to find mappings whose status is Unavailable:
Get-SmbMapping
2. Open the drive. If it opens quickly and the red X goes away, this matches Microsoft's description of an idle disconnect (cause 1). The data was reachable all along.
3. Note when and where it fails. If the drives fail only at sign-in, and only on devices that connect later (wireless, VPN, a slow start), cause 2 fits. If the device is on Windows 10 version 1809, cause 3 also fits.
4. Elevated or not? Compare a normal command prompt with an elevated one. If net use shows the drives in the normal prompt but not in the elevated one, check the UAC setting User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode (cause 4).
5. Check the drive map settings. In the Group Policy object that maps the drives, open each Drive Map item and check whether Use first available, starting at is selected. Note the letters used by drives users map by hand (cause 5).
6. Did Group Policy apply? On the affected computer, in an elevated prompt, Microsoft's guidance uses:
gpresult /h gp.html
Look for the GPO that maps the drives, and for an error saying why it was not applied. Then check the System event log for Group Policy errors such as Event ID 1129 (cause 6).
The fix
Match the fix to the check that failed:
Idle disconnect: Microsoft notes that some older programs may not save files or read data while the drive is disconnected. If that is happening, Microsoft's page gives two ways to change the server-side time-out:
Registry: set
autodisconnectunderHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parametersto a longer time-out. This method cannot turn the feature off.Command line, on the server that holds the share:
net config server /autodisconnect:<minutes>-1turns the feature off. Microsoft warns that0does not turn it off: the server then disconnects after only a few seconds of idle time. Microsoft also says this method may turn off autotuning for the Server service.
If no program is affected, it follows from Microsoft's description that the red X alone is not a fault: the drive reconnects when it is used.
Network not ready at sign-in: Microsoft's reconnect page offers a script that reconnects Unavailable drives at sign-in, with three ways to run it: a startup item, a scheduled task that starts only when a network connection is available, or a scheduled task triggered by RasClient Event ID 20225, which means a VPN connection succeeded. Run it as the standard user, not elevated.
Windows 10 version 1809: use the same workaround and bring the device up to date. Microsoft's page points to the Windows 10 version 1809 update history for the fix.
Elevated program: Microsoft gives two workarounds. Set the UAC elevation prompt for administrators to Prompt for consent, or map the drives again inside the elevated session, for example with a batch file.
GPP clears drives: give each Drive Map item a specific drive letter and do not use Use first available, starting at. Microsoft says any number of GPP drive map policies can then apply without losing manual drives. If you must keep the setting, Microsoft says manual drives must use letters earlier in the alphabet, and only one GPP drive map policy may apply to the user.
Group Policy did not apply: fix the cause the event or
gpresultnames first, such as connectivity to the domain controller for Event ID 1129. The drive maps follow once policy applies.
How to confirm the fix
- After a fresh sign-in,
net useshows the drives as OK, not Unavailable, and the notification does not appear. Get-SmbMappingshows no mappings with status Unavailable.- For the elevated case, the drives appear in the elevated prompt as well.
- For the GPP case, manual drives and all GPP drives are present after the next sign-in.
- For the Group Policy case,
gpresult /hlists the drive map GPO as applied.
What to watch afterwards
- Laptops and VPN users. It follows from Microsoft's notes that devices without a network path at sign-in are the ones that miss reconnection. Check them after VPN or wireless changes.
- New drive map policies. Any new GPP Drive Map item set to Use first available can clear drives again.
- Group Policy errors in the System log, such as Event ID 1129, on computers that start before the network is ready.
Read next
Related articles you may want next.
- TroubleshootingSystem error 53 "The network path was not found": name, port 445 or the Server serviceSystem error 53 means the client could not reach the share. Check the server's name, TCP port 445, the Server service and the firewall at the other end, and the client's own TCP/IP NetBIOS Helper service. Prove each one in turn.Read article
- TroubleshootingGroup Policy Not Applying: gpresult, Events and SYSVOLA Group Policy setting missing on a hosted server: read gpresult as the affected user, check loopback, filter one run's events, then check SYSVOL state.Read article
- TroubleshootingNetlogon event 5719 or Group Policy event 1129 at start-up: network not ready, or a broken trust?"This computer was not able to set up a secure session with a domain controller" at boot, or Group Policy failing at start-up. Tell a harmless start-up race from a broken trust relationship, prove which one you have, and fix the right thing.Read article
Risks and limits
- Microsoft's reconnect script starts with a line that sets the current user's PowerShell execution policy to Unrestricted. That loosens a security setting for that user. Treat it as a workaround for the case it was written for, and keep the script in a location users cannot change.
- The page's third workaround spells the PowerShell switch
-windowsstyle; its second workaround spells it-windowstyle. Use the second spelling. - Turning off
autodisconnectkeeps idle sessions open on the server. Microsoft says the feature exists to save server resources. - Microsoft's elevated-prompt page also describes the
EnableLinkedConnectionsregistry entry. Its two documented workarounds are the UAC prompt setting and mapping the drives again in the elevated session. - Several of these Microsoft pages state older versions in their "Applies to" lines (Windows 10 version 1809; Windows 7 SP1 and Windows Server 2012 R2). Check the page against the versions you run.
- If the drive never connects, even when opened and with the network up, that is a reachability problem. Start with the error message
net usegives you.
Sources
- Microsoft Learn, "Mapped network drive may fail to reconnect in Windows 10, version 1809", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-network-drive-fail-reconnect
- Microsoft Learn, "Mapped drive connection to network share may be lost", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drive-connection-to-network-share-lost
- Microsoft Learn, "Mapped drives are not available from an elevated prompt when UAC is configured to Prompt for credentials", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command
- Microsoft Learn, "Group Policy Preferences removes manual drive mappings if the use first available setting is enabled", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/group-policy/manual-drive-mappings-removed
- Microsoft Learn, "Applying Group Policy troubleshooting guidance", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/group-policy/applying-group-policy-troubleshooting-guidance
Next step
A red X has several causes: open the drive, compare normal and elevated prompts, then check the drive map settings and Group Policy results. NetLeverage has looked after business servers since 2002. If your drives still fail at sign-in, talk to us through managed support with the net use output and the gpresult report.
This article was originally published on .