Windows 10: Windows 10 bug - USB Drive vs NAS drive mapping conflict - Why isnt this fixed?

Hello all, I've just spent a good couple of hours diagnosing and resolving an existing bug within Windows 10 https://answers.microsoft.com/en-us...-mapping/f8dc49d5-ad3e-4f46-9341-266074f44a3c - which was reported as a longstanding issue back in 2017.


Can anyone think of a good reason why this isn't fixed yet?
It seems very lax that this bug has existed for so long within a 10th revision of your operating system, Does anyone think this is good enough?

I'm just rather annoyed such a simple bug even exists, let alone has for 3+ years now.

:)

 

Windows 10 bug - USB Drive vs NAS drive mapping conflict

Hello Hector,

NAS Drivers were assigned drive letters using the Command prompt with the /persistent:YES flag.

Internal SDD/HDD/CD/DVD were assigned drive letters using diskmgmt.msc.

My question is not, how to assign drive letters, but, why Windows 10, assigns a currently assigned drive letter (although not connected) to a USB drive, which then can't be seen ?

e.g. H: is assigned to \\HOME\MyUserId

the HOME NAS server isn't online, so the H: drive icon is shown with a Red x, indicating that it's unable to connect to that drive.

I now plug in a USB Drive. The drive is automatically given the drive letter H:, but because H: is already mapped to a NAS drive, the USB Drive isn't displayed until I delete the NAS drive mapping.

Why can't Windows 10, select the next available free drive letter ?

Are there any registry settings involved with the assignment of drive letters to external USB drives ?

 

Windows 10 bug - USB Drive vs NAS drive mapping conflict

Hello,

MY PC has two internal drives that have drive letters assigned to them, and 2 CD/DVD drives, plus one USB Printer Drive (A,B,C,D,E,F)

I also have a couple of NAS drives that I've assigned Drive letters to (H,K,L,P,S,T,U and V) - the NAS drives arent always online, particularly if I disable the internal NAS card that they're hooked up to. Unplugging, and replugging in the drive does not
help.

Now, when I plug in an external USB drive, I find it does not appear, simply because it appears to be getting assigned the drive letter H (which is currently mapped to an offline NAS drive). This unfortunately means I can't access the external USB drive.
Surely this is a bug in the assignment of drive letters to newly plugged in USB drives ?

When I enable the NIC, for those NAS drives, and replug-in the USB drive, it gets assigned the G letter, and becomes available...

What is going on ?

 

Windows 10 bug - USB Drive vs NAS drive mapping conflict

I'm able to replicate the issue quite easily. One thing is that even though the NAS drive mapping for H: remains shown with the red X, clicking upon it, takes me to the contents of the USB Drive. However no drive symbol for the newly plugged in USD drive
is shown under "Devices and drives" - thus giving the impression it's not connected.

Surely, Windows should be choosing the next free unassigned drive letter for the USB drive (i.e. I or if none are available, simply showing the drive symbol under Devices and Drives without an assigned letter.