Mapped Drives not appearing in File Explorer Win10

_{Tuesday, September 5, 2017 9:07 PM | 1 vote}

Windows 10 1703 - recent update from several major builds back

Some, but not all, mapped drives appear in Windows Explorer under This PC

The PC is in a domain and group policy is doing the drive mapping.

Mapping works fine for the same login on other PCs.

Exlploer has been open 3+ minutes (sometimes on other PCs I see the drives show up "late") and has been refreshed.

Net Use shows all the drive mapped.  Two (G: and H:) are missing from the Explorer, these are on a windows server 2012. one shows from server 2008 R2.

I can get to H: from CMD. Existing shortcuts to H:\object> work. Programs using Process.Start("H:\object>") work. From Word 2016 Open and browse can see all mapped drives. Explorer can access the UNC share path on he server.

Set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLinkedConnections = 1, no joy.

Any ides on why some mapped drives are not showing?

_{Tuesday, September 5, 2017 11:05 PM}

Not seen this issue with mapped drives and Explorer on Windows 10.

How are they being mapped via GPO? User Configuration > Preferences > Windows Setting Drive Maps or a script of some type?

_{Wednesday, September 6, 2017 3:17 AM}

Hi,

Have you turn on network discovery through Control Panel\Network and Internet\Network and Sharing Center\Advanced sharing settings?

Try to restart service “Function Discovery Provider Host “  and  “Function Discovery Resource Publication” in Service control panel.

Try to remap your network drive and assign a different letter to it to check the issue again.

Best regards,

Joy.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

_{Wednesday, September 6, 2017 2:42 PM}

After a reboot today the drives mapped properly.So the problem resolved itself. I have similar problem on a laptop, and given that the laptop is only attached for minutes at a time, the drives never map. 

It would be nice to speed up the mapping. I now about GPUPDATE /force but it doesn't map the drives. GPRESULT /r show the drive mapping GPO is being applied.

The drive is being map by Group Policy. This GPO is working fine for 30+ PCs, aboput 1/4 Win 10.

No good GPO report for posting but here is the best I can do:

Drive Map (Drive: H)

H: (Order: 3)

General

Action   Update

Properties

Letter    H

Location               \apcd04\data

Reconnect           Disabled

Label as               LAN

Use first available            Disabled

Hide/Show this drive      No change

Hide/Show all drives      No change

Common

Options

Stop processing items on this extension if an error occurs on this item                No

Run in logged-on user's security context (user policy option)     No

Remove this item when it is no longer applied  No

Apply once and do not reapply No

_{Friday, September 8, 2017 1:03 PM}

Ony differnce I have on the drive map settings is Reconnect Enabled.

Hopefully the problem has not reappeared for you, might just be one of those thing.

_{Thursday, November 29, 2018 6:06 PM}

I am having this problem on Win10 1803 - only on one computer, affects multiple users. Manually executing
GPUpdate /target:user /force
Resolves the issue for that user

Just to confirm details:

• the drive is not listed in file explorer's tree or My PC page
• Shortcuts to the drive & sub-folders work as if nothing was out of the ordinary.

_{Thursday, November 29, 2018 10:53 PM}

Exact same issue here.. 

Just to confirm details:

• the drive is not listed in file explorer's tree or My PC page
• Shortcuts to the drive & sub-folders work as if nothing was out of the ordinary.

What's the prob?

_{Monday, January 7, 2019 12:10 AM}

Having the same issue in our environment

• the drive is not listed in file explorer's tree or My PC page
• Shortcuts to the drive & sub-folders work as if nothing was out of the ordinary.

Only affects some computers. Logging off/back on or rebooting the PC will temporarily resolve the issue.

Another workaround is to kill explorer.exe and run the task again however this is only a temporary fix.

From command prompt > taskkill /f /im explorer.exe

Start > explorer.exe

Would be great if we can get a proper fix for this.

_{Wednesday, February 6, 2019 2:23 PM}

Anyone figure it out? I have the exact same problem. I can see/access the drives if I type in the drive letter, net use shows the drives mapped out, however under This PC they do not show.

What I also observed is that the profile mapped drive appears however any created by a GPO do not. I can do the same thing regarding killing explorer and having the drives show up in This PC. Lucky for me it's only one user at this time but I'd like to get it resolved.

Another note, it does show the mapped drives if you open an app and go to save a file.

_{Wednesday, February 6, 2019 8:42 PM}

Hi,

We were able to resolve this issue by changing the drive mapping GPO Action from "Reconnect" to "Update"

Hope this helps.

_{Tuesday, October 22, 2019 3:42 AM}

Windows 10 1703 - recent update from several major builds back

Some, but not all, mapped drives appear in Windows Explorer under This PC

The PC is in a domain and group policy is doing the drive mapping.

Mapping works fine for the same login on other PCs.

Exlploer has been open 3+ minutes (sometimes on other PCs I see the drives show up "late") and has been refreshed.

Net Use shows all the drive mapped.  Two (G: and H:) are missing from the Explorer, these are on a windows server 2012. one shows from server 2008 R2.

I can get to H: from CMD. Existing shortcuts to H:\object> work. Programs using Process.Start("H:\object>") work. From Word 2016 Open and browse can see all mapped drives. Explorer can access the UNC share path on he server.

Set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLinkedConnections = 1, no joy.

Any ides on why some mapped drives are not showing?

Your post here helped me find a workaround, we are running the same setup for one of our clients and found that using net use X: /delete on all mapped drives before running gpupdate /force allowed the drives to re-connect correctly.

It might be worth trying to turn persistence off on the mappings?

_{Friday, November 22, 2019 7:45 PM}

We are also running into this issue.

Does anyone know if an official bug has come out on this?

_{Friday, March 6, 2020 9:36 AM}

Hi Jimmy411,

We are having the same issue.

Have you solved the issue? Could you advise a soultion?

_{Thursday, March 12, 2020 12:11 AM}

Hi,

We changed our drive mapping GPO action from reconnect to "Update" and this resolved the issue.

Cheers