Windows 10: Windows 10 keeps disconnecting my Mapped Drives?

Recently, I believe after the last update, Windows 10 keeps disconnecting my mapped drives forcing me to disable and reenabling my network adapter, which is only a temporary fix.


I have a Windows 10 Pro 64-bit Version 1909

Tried updating to 20H2 and the one before that, but kept getting the 0xc000005


I have seen something about changing the Mapped Drive policy to "update" but as I'm not on a server, I don't have access to the Group Policy Manager only the Group Policy Editor, which doesn't have the GP settings for mapped drives.

:)

 

Unable to Open/Disconnect a Mapped Drive in Windows 10

Hi Landon,

To resolve this issue, please follow the steps on how to disconnect a Mapped drive below:

• Right click on Start button > select
  Command Prompt (Admin).
• Type " mountvol /r "
• Reboot your computer.

Regards.

 

Unable to disconnect Mapped drive

Hi,



Thank you for writing to Microsoft Community Forums.



As you have mentioned that you have removed the mapped drives through GPO and still the drive keeps appearing, I suggest you to try removing the mapped drive by running the Net use command in Command Prompt and see if that helps. Please follow the
steps mentioned below:

1. Press Windows key + S, and type Command Prompt.
   
2. Right click on the Command Prompt icon and select
   Run as administrator.
   
3. Now, type net use f: \\financial\public /delete
   (Replace f: \\financial\public with the drive name)
   

For more information on Net use command, you can refer the article
Net use.



If the issue persists, I suggest you to post your query in TechNet
forums, where we have support professionals who are well equipped with the knowledge on the GPO and mapped drivers to assist you with the appropriate details.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

How do I prevent Windows 10 from disconnecting mapped drives?

I have a mapped drive on Windows 10 Enterprise that keeps disconnecting itself, sometimes even when I'm in the middle of doing things using files on that share. I have a desktop shortcut to it; if I click that after the drive has disconnected, I get this error message:





What's actually happening is that when I click the shortcut, the system re-maps the drive immediately, but not before displaying the error message. If I keep a "This PC" window open, I can see the drive appear in the list a moment later. So if I click "No", then the shortcut will work until Windows decides to disconnect the drive again, after which I'll have to go through the same stupid error message again.

When I created this mapped drive, I checked the "Reconnect at sign-in" box. It doesn't seem to have helped.

I have tried issuing the command net config server /autodisconnect:-1 to turn off automatic disconnecting; it had no effect.

I've tried deleting the mapping and recreating it with net use Z: \\sharename\path /user:SHIRE\baggins /persistent:yes, but the problem continues.

This is super-annoying, not just because of the "Problem with Shortcut" dialog, but because it keeps disrupting my work flow. Any open file explorer windows showing the mapped drive's contents get closed. If I have a file open in Notepad++, it will inform me that the file I'm editing no longer exists, and ask what to do with the copy in memory (keep/discard).

In case it's relevant, this particular share lives on a Linux server running Samba. I can post the config file for that if needed.

Any suggestions?