Running ChkDsk on Windows 10 20H2 may damage the file system and cause Blue Screens

[steve2470]

Running ChkDsk on Windows 10 20H2 may damage the file system and cause Blue Screens

https://www.ghacks.net/2020/12/19/running-chkdsk-on-windows-10-20h2-may-damage-the-file-system-and-cause-blue-screens/

by Martin Brinkmann on December 19, 2020 in Windows - Last Update: December 19, 2020 - 22 comments

Microsoft's newest version of Windows 10, Windows 10 20H2, appears to have a bug that may damage the file system of the Windows partition and cause blue screens during reboots. Reports suggest that running ChkDsk on these devices may damage the file system and cause blue screens on the first reboot of the system after the check disk operation completes.

Günter Born provides details on the issue on his blog.

He narrates how one administrator discovered (German forum link) the issue after upgrading systems to Windows 10 20H2 and running the command chkdsk c: /f after the update installation. The command checks drive c: for errors to repair them right away if any are found.

AFAIK, Mr. Brinkmann is reputable. I use chkdsk at times. FYI.

[lpbk2713]

1. Something like this is always good to know.

Thanks for the info.

[OAITW r.2.0]

2. Haven't used that command in 20 years....thankfully.