Windows 10 Guest additions 6.0.2 scramble drive mappings into shared folders

[BBoyar]

Running Win 10 Pro (October 2018 Update, build 17763) on both host and guests, updated host from 5.2.22 to 6.0.2 with 6.0.2 guest additions. Upgrading guest VMs to 6.02 guest additions scrambled the mapped drives into shared folders. The windows drive mappings no longer corresponded to the originally assigned shared folders,. Rolling back to a previous version of the VM (which still had 5.2.22 guest additions installed restored correct behavior.

FWIW:

net use v:
vboxsrv\bbj5-c /persistent:yes net use w:
vboxsrv\data /persistent:yes net use x:
vboxsrv\bbj5-e /persistent:yes net use y:
vboxsrv\a /persistent:yes net use z:
vboxsrv\aa /persistent:yes

Reproduced this behavior on a second (and different) vin 10 pro vm: changing nothing other than upgrading guest additions from 5.2.22 to 6.0.2 corrupted the mappings into shared folders.

two logs w10p-1-2019-01-18-21-21-45.log scrambled VM 6.02 guest additions w10p-1-2019-01-18-21-41-13.log correctly mapped VM 5.2.22 guest additions

[Socratis]

It's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

That being said, there was never a guaranteed order that the Shared folder should have, in order to get a specific letter assigned to them, in previous VirtualBox versions. Now, with 6.0.0, they do. Just look at their properties and the MountAt option.