Windows 10: Maintaining Drive Letters & Network Mappings in Windows Explorer

I have a Surface Pro 7 & want to access the SDXC drive & map a network drive in Windows Explorer. I want the SDXC drive to have the letter E instead of the default, which is D, and I want the network drive to use the letter D. I know how to map a network drive, and I know how to change the drive letter for drives, but after restarting, Windows seems to forget those changes. Also, after restarting, it uses the SDXC icon for the SDXC drive, but it names it as if it were the network drive, and when hovering over it, displays the Space free and Total space for the network drive rather than the SDXC drive. I don't seem to remember drive lettering & mapping being this troublesome in the past although it has been a while since I did these configurations on my previous machine, which was also Windows 10. What can I do to achieve these mappings/letterings and not have them lost when restarting? Thanks.

:)

 

Maintaining Drive Letters & Network Mappings in Windows Explorer

I have a Surface Pro 7 & want to access the SDXC drive & map a network drive in Windows Explorer. I want the SDXC drive to have the letter E (instead of the default, which is D), and I want the network drive to use the letter D. I know how to map a network
drive, and I know how to change the drive letter for drives, but after restarting, Windows seems to forget those changes. Also, after restarting, it uses the SDXC icon for the SDXC drive, but it names it as if it were the network drive, and when hovering over
it, displays the Space free and Total space for the network drive rather than the SDXC drive. I don't seem to remember drive lettering & mapping being this troublesome in the past (although it has been a while since I did these configurations on my previous
machine, which was also Windows 10). What can I do to achieve these mappings/letterings and not have them lost when restarting? Thanks.

 

Cannot Map Network Drive in Explorer

Hello:

Lately, I am having trouble Mapping one of my Network Drives in Windows Explorer. A long time ago (early Windows 10 and before) I could simply click on "Network" and it would bring up my Drive (among others), I would click on it (right click as I recall) and it would bring up a system dialog box wherein I could select a drive letter and choose to always map on boot.

Now, the explorer doesn't list it at all! I can type 'net use Z: "\\Our1stNASServer\Our Shared Folders"' into an Admin cmd window and that partially maps the drive (only 2 out of about 10 folders); the drive still doesn't show up in Explorer, either on the right side or the left!

I am snookered! I hope someone can help me - I spend a good percentage of my time trying to correct this problem!

Thanks in advance.

Sparky

 

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.