I'd be very curious to see a deep root-cause-analysis of this, especially because it seems to be SSD-specific and in the "detect if the drive is an SSD and do something slightly different" way, which IMHO is not good behaviour in general as it is leaking the abstraction.

I wonder if a VM simulating a virtual SSD hosted on a machine with a regular HDD would be able to reproduce this bug, but then again, recent Windows versions seem to be doing some detection of whether they are running in a VM (and likely altering behaviour due to this too)... what a mess.