Windows 10: Mapped drives not showing in explorer until explorer restarted?

Anyone find a solution for this issue? Previous thread now locked:https://answers.microsoft.com/en-us/windows/forum/all/mapped-drives-not-showing-in-explorer-until/dcb20da0-a0b5-4ba9-a535-6af713e2041a?auth=1

:)

 

Mapped drives not showing up on Explorer

Wanted to mention that I'm experiencing this same issue. Environment here is a Windows Server 2012 R2 domain with network shares and printers mapped by GPO. GPO drive mappings are not on a per-user basis and instead are global for all users.

Affected user can not access mapped drives via explorer, yet NET USE shows drives mapped as expected. Attempting to remap network drives via explorer results in a prompt stating that the connection is already mapped to that drive letter, do I want to disconnect and reconnect it?

Oddly, using applications that provide an 'open document' dialogue can see and access mapped network drives normally. For example, open Word, file -> open -> browse: Left pane shows network shares, clicking on network share shows share contents. Clicking on 'This PC' shows all mapped drives which are navigable and documents can be opened normally. Doing this does not correct the issue with Explorer. Similarly, a command prompt also operates as expected, so it's possible to change to a mapped network drive by the associated letter and to list / copy / delete files normally.

Issue appears to be limited to a single user profile on the workstation displaying the described symptoms. Logging in as another user results in the drives being mapped and accessible as usual. Symptoms persist through reboot. User account with symptoms does not have admin access locally or on the domain.

 

Mapped drives not showing up on Explorer


Huh?

Let me restate the problem, a bit more simply. Since at least Windows XP through Windows 8.1, using Windows Explorer you are able to open the Network View, expand a displayed computer, right click on a drive or folder that has been set up as shared under the displayed computer, select "Map Network Drive...", assign a drive letter using the "Drive" drop-down menu, select "Reconnect at logon", and !wow! you have a mapped network drive that shows up every time you start up your computer as long as that network drive is accessible on the network. You can do this also with Windows 10, just as with the earlier OS levels.

But with Windows 10, on my SP3, those mappings sometimes disappear from Windows Explorer after the SP3 is awakened from sleep. To get to them again with Windows Explorer as mapped network drives, I must repeat the mapping operation, just like in the paragraph above. But unlike with the original mapping, the drive assignments still show up like I had set them previously under the "Map Network Drive..." dialog in the list of drive letter possibilities that show up when the "Drive:" drop-down menu is expanded. (As an aside, this means that I don't have to remember the drive letter I had previously used when remapping them, which makes it a bit easier to do.)
DaveD

 

Mapped drives don't show in Explorer until Explorer restarted

Hi there,

I've been experiencing a strange issue lately for multiple users.

First, our drives are mapped via GPO. All drives map settings in the policy are consistent for all drives.

A mapped network drive is not visible at all in Explorer. Other drives are visible and connected. This includes mapped locations on the same server.

If I run 'net use' from the command prompt, I can see that the drive is mapped and the status is OK.

If I attempt to browse to the drive letter, eg G:, in Explorer, it says that it cannot be found.

If I then kill Explorer from the task manager and start it again, the drive will now show up in Explorer, and can be accessed.

There doesn't appear to be a pattern for this, I have only had it happen for random people at random times.

Has anyone else come across this issue before?

Thanks,

Adam