Windows 10: Mapped Drives not showing untill Explorer is restarted

I have a few machines in our network that can not view our mapped drives until their explorer.exe are restarted. They are receiving mapped drives via a GPO through update.


I have tried setting my registry entry to

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLinkedConnections to a DWORD of 1


The network locations are accessible if you enter them manually but the drives don't show up in explorer even after group policy update.

Windows 10 ver 1909

:)

 

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

 

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 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.