Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,195 questions
Is automount behaviour changed in 20H2?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 21%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJV%3C/text%3E%3C/svg%3E)
Jussi Vänskä
1
Reputation point
Using an external card reader works without an hitch on 1809 and 1903 builds but not on 20H2.
When creating a totally blank MMC card and writing a new media image on it using Rufus or Linux dd the automount no longer is capable of assigning a drive letter to the volumes in the image. After assigning a drive letter(s) manually in Disk Management the drive works as expected until a new image is written on to the device. This is tested to be not related to policies as the same issue persists in corporate IT machines, virtualized machines and COTS sourced machines.
What has changed and is this a bug or a feature? We need to adapt our customer documentation according to the answer and expected fix if this is a bug.
I'm aware of this https://answers.microsoft.com/en-us/windows/forum/all/windows-10-will-not-assign-a-drive-letter-when/a12d4cb5-5c9c-4c2e-8a37-37eb2da48a47