Windows 10: Mapped Network Drives don't show up after reboot until I sign out and sign back in.

As the title saysLately when I reboot my system, my network drives do not reconnect under "Network Locations" in "This PC"The only way I've got them back is by signing out and signing back in.Is there a fix so that the mapped drives show up at reboot.Edition Windows 11 ProVersion 22H2Installed on ‎19/‎02/‎2024OS build 22621.3155Experience Windows Feature Experience Pack 1000.22684.1000.0

:)

 

Mapped Drives Issues

To clarify .... the issue is the Windows 10 OS. It is with Windows File Explorer. The Mapped drives used to appear in File Explorer's left panel list of drives and folders. Two days ago File explorer stopped show the mapped drives. so not they don;t appear in the list of Drives and folders.

- - - Updated - - -

I did, it has no effect. I also check the NAS devices they support SMB 2.0. Also I have several other computers on my home network they work fine with the mapped drives and They do not have SMB 1 turned on. So it is something that happened to the computer in question.

 

Windows 10: Mapped network drives not showing up until sign out/restart?

Exactly what it says on the tin; anyone?

This is what's happening:

After install, suddenly network drive mapping isn't working properly. When I go through the steps to map a network drive, said drive doesn't open like it's supposed to, and doesn't show up in This PC/My Computer until after I either sign out and sign back
in, or restart.

For the record, this is the process:

1) Open This PC

2) Click "Map network drive" and select the option from the dropdown

3) I select the drive letter (let's say I chose R)

4) I enter the network path: \\[computername]\R\ (the local drive letter on the network machine is also R)

5) Something flickers for half a second, but nothing happens

6) If I use the Run command, I can access \\[computername]\R\ just fine, but if I try to go to R:\, I get "Drive not found"

7) If I sign out and then sign back in (or restart), suddenly the mapped drive shows up in This PC, and Run can get to it using R:\

This is the RTM build, upgraded directly from 10041. The network profile is set to Private, so there shouldn't be any sharing or security problems.

 

Windows 10: Mapped network drives not showing up until sign out/restart?

In maybe the same tin...

Stumbled into a problem:

Scenario:

• Mapped a network computer drive to be E:\ on a laptop
• Worked with no obvious problems - plug in a USB stick and it would take the next drive letter up
• Then networked computer serving the mapped drive was not available - showed as not available on the laptop.. OK

Problem:

• Plug a USB drive into the laptop - fails to show in Explorer. It appeared as a device; but not as a file system - guess Windows was trying to assign it to be drive E:\ - but that was held by the Map
• The Map drive letter could not be released - Un-Map or Delete refused to clear it
• Only solution was to put the network server back online and then clear the Map on the laptop.

I was sure I had never had this problem before... but... all of my Windows 8.1 computers are now Windows 10 (10240 and 10525). I cannot test on Win 8.1. I still have a Windows XP computer - tested it... no such problems - dead network drive maps are easily
deleted.