Following Windows 10 upgrade, mapped drives disconnect briefly

One of our clients reported that their computers were presenting an error message warning that mapped drives (in this case it was the N: drive for example) was unavailable (location unavailable) when they happened to be working on it. This started occurring after we had upgraded them from Windows 7 to Windows 10. The issue was happening several times per day. The drive would only disconnect for a moment and then everything would be okay once more. However it caused this annoying pop up. In our example the mapped drive was pointing at a share on a Windows Server 2012 R2 machine.

We investigated network issues, restarted switches, ran ping tests, etc, but nothing obvious showed up.

The culprit was in fact caused by Group Policy settings whereby drive mappings were set to "Replace". Since Windows 8, the system automatically runs GP updates in the background and will disconnect and reconnect the drive to replace it.

The fix is to find the responsible Group Policy object (the easiest way to check is by running RSOP from the command line). Then edit the offending GPO and change the drive mapping action to "Update" and the issue will disappear! The required settings are within User Configuration > Preferences > Windows Settings > Drive Maps.

Credit to 'Shane8960' for posting the fix on Spiceworks community. The original post that helped us can be found here

I hope this helps someone out there!


Did this article help you today?

Yes, thank you :)No, sadly not :(



Thanks for posting this! This issue had been driving me crazy. Re-blogged:

For us, the issue began after moving from win7-pro to win10-pro. Our issue was a tad more severe than merely losing a mapped drive. We have client-side apps that have db-s on share drives. The disconnect (even for a moment) screwed the app's access to that data. Our disconnects consistently occurred after about 20 mins of client idle time. A small shop - 6 desktops - all the exact same machines, config & software. File history is disabled. Winserver 2012 R2. No probs at all in win7. We tried: - update instead of replace - no luck - registry changes to maxes in keepconn and disconn - no luck - uninstall/reinstall nic drivers - no luck - mapped drives on client side as persistent - only thing that worked for us. I've seen stuff claiming that the architecture was changed in Vista and others claiming it was changed in win-ape.1. I have no experience with ape but we had no issues at all in win-7. I have a feeling this is somehow related to internal hooks for file history or cloudy stuff that require a regular drive refresh.

One thing to check also is the fast boot option in Windows 10. I disabled fast boot and had no more problems with mapped drives.

This fixed my map network drives. I just want to post it somewhere, as I searched months for an answer, maybe it could help someone. Windows 10 settings; network and sharing center; ethernet right click and click on ethernet properties. Under the Networking look for Internet Protocol Version 4 (TCP/IPv4), right click open its properties. Set it up manually. I used ipconfig in the cmd. to find IP address, subnet mask and default gateway. Then set up the DNS server manually to 9 . 9 . 9 . 9. I am no IT tech, but this solved the problem of map drives being dropped. Mine is stable now.

DON'T listen to "Karina", changing your DNS will NOT FIX a network drive issue. The DNS is probably taking you to somewhere DANGEROUS.

Thanks for sharing this Karina. It sounds like your issue was with the DHCP server on your LAN (which you overcame by hard-coding your IP settings). Doing this can cause IP address conflicts so I wouldn't recommend it for others unless you know what you're doing with your DHCP server. Manually setting the DNS server to is not a bad idea but shouldn't have any specific impact on the dropping of the mapped drives on the network.

Thank you loadOfBS for flagging up the concern, but is not dangerous - it's actually safer than most DNS servers. It's is Quad9 and checks DNS lookups against IBM X-Force's threat intelligence database. Check it out

Add new comment