Windows 10: Mapped Drives not showing in File Explorer

Hi,I am setting up a new MS Surface with Windows 10 Pro that is joined successfully to our corporate domain with a domain user profile configured. I've done this hundreds of times, but for some reason, this particular machine won't show the mapped drives, which are in Azure I can connect to them by typing in the Search box, and I have Network Discovery turned on for the domain. No other machine has this problem. I did the regedit for Enable Linked Connections in llHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\SystemI enabled SMB 1 in Programs and FeaturesI enabled Show

:)

 

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.

 

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.

 

Problems with mapped drive

Well I got one step closer to getting the mapped drive working.

Instead of using Windows 10 File Explorer to map the Network Drive, I do it manually from a Command Prompt run as Administrator:

net use G: \\XP07\XP_Dev

After executing this command I can copy files to and from the mapped drive to the system disk. And while this is a huge step forward there are still other problems with the mapped drive.

Opening a jpg file in Paint by clicking it from File Explorer loads the picture just fine, but I can't save it. When Paint tries to save the file it can't find the mapped drive, it doesn't even show up when browsing for a place to save it.

There are a few links on the web discussing this very issues of not being able to browse a mapped drive from within a program. There is supposed to be a registry fix for this by adding EnableLinkedConnections and settings it's value to 1 but it didn't work.

So the next step after getting File Explorer working is to somehow get programs to see the mapped drive.