Windows 10: Mapped drive disconnected after reboots

Since fall creators update I am seeing one of my mapped NAS drives always in a disconnected state after a reboot. It’s easily fixed by clicking the drive displaying the red x in explorer to establish the connection. But it seems strange that this has only started after fall creators and is the only one of three mapped drives doing this. And this same mapped drive is mapped in identical state to another machine running fall creators with no such issue. Any ideas on how to fix this? Or why it is happening. It’s only a minor niggle and can live with it as there are no pressing dependencies on the mapped drive but would be nice if there was an easy quick fix

thanks, Wayne

:)

 

Windows 10 losing access to network drives

This worked for me. For about 10 minutes, rebooting my cable modem resolved the issue but then my mapped drives disconnected again and wouldn't reconnect. Then I tried:

sc.exe config lanmanworkstation depend=bowser/mrxsmb10/nsi

sc.exe config mrxsmb20 start=disabled

reboot

and that resolved my problem for now anyway - we'll see how it goes after a while.

 

W10 Home: Can only map ONE WD My Book Live share at a time??

I have some wonky things going on with my new Dell Inspiron 13 7000 running Windows 10 Home. When I map a share on my 3TB WD My Book Live network storage, it works fine. When I attempt to map a second share with different credentials on the same WD storage
device, Windows comes up with an error that the share requires a different user name or password. This happens for any of several shares on the WD device, and I am certain that I am using the correct credentials... I even accessed the WD unit's admin portal
and reset the passwords, with no luck.

However, once I disconnect the first successfully mapped drive, I can map another share (but only one other share).

Related to this glitch...

• With one network drive properly connected, and after unsuccessfully attempting to map a second drive (with different credentials), i rebooted Windows 10 Home. When it booted back up, the network drive that was successfully mapped and connected before the
  reboot had a red X and I couldn't access it. It prompted me for a user name and password when I tried to open it, and the user name for the OTHER share (that I had tried unsuccessfully to map for the reboot) was in the credential dialog that came
  up.
  
• When I tried to unmap/disconnect the mapped drive that I could no longer access (right-click/Disconnect), no error for disconnecting came up - it acted as if the disconnect was successful. However the drive (still with the red X) stayed listed in Windows
  Explorer (left and ride sides under This PC). When I tried to open it, it said that the drive was not connected, yet it was still listed.
• Even when I disconnect a network drive that is properly connected in Windows Explorer, the drive disappears from the right side listing of drives under This PC, but isn't removed from the left side list of items under This PC.

Windows 10 Home is apparently having trouble keeping credentials straight for mapped drives, as would be indicated in my first bullet, above. It seems that when one attempts to map a second network drive, even though that process prompts for user credentials
for the second network share, Windows seems to use the credentials for the first, successfully mapped share instead, which is, of course, unsuccessful.

Additionally, as my second and third bullets point out, adding/removing network shares in Windows Explorer is just wonky and needs some bugs fixed. Removing share drives should remove their icons from both sides of Windows Explorer and not leave a remnant
icon behind.

Anyway, are these known issues in Windows 10 Home? If so, are they slated to get fixed? Or, am I doing something wrong?

Thank you

 

Remove it and then reboot and see if you can map it again. It should have reconnect at login checked. You can always do it from the Command Window.