Microsoft Addresses Windows 10 CHKDSK Bug That Damages File Systems on SSDs and Prevents OS from Booting

[Tsing]

Image: Microsoft



Over the weekend, Born’s Tech and Windows World warned of a nasty bug stemming from Windows 10 20H2’s recent KB4592438 cumulative update, whereby running CHKDSK would destroy the file system on an SSD and prevent the OS from starting after a reboot. A fix for that problem is now rolling out to all affected devices.



“A small number of devices that have installed this update have reported that when running chkdsk /f, their file system might get damaged and the device might not boot,” Microsoft explained. “This issue is resolved and should now be prevented automatically on non-managed devices.”



CHKDSK is a classic command that’s used to...

Continue reading...

 

[ThreeDee]

ouch!

 

[AntiQuark]

If I boot Windows 10 with any drive from a Windows 7 machine in the system, or boot windows 10 on my windows 7 machine, every single drive other than the initial windows 10 drive(s) automatically are scandisked.
Then when used on windows 7 again, it runs scandisk to revert whatever it was that windows 10 decided to **** up.
Its really annoying.
This has happened since Windows 10 was released and still happens.