Showing results for 
Search instead for 
Did you mean: 

General Discussions

Esteemed Contributor III

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

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.

Update: Microsoft confirmed the issue on the KB4592438 support page. The issue has been resolved according to Microsoft:

This issue is resolved and should now be prevented automatically on non-managed devices. Please note that it can take up to 24 hours for the resolution to propagate to non-managed devices. Restarting your device might help the resolution apply to your device faster. For enterprise-managed devices that have installed this update and encountered this issue, it can be resolved by installing and configuring a special Group Policy.

The issue can be resolved on devices that experience the issue already by running the command chkdsk /f by selecting the Command Prompt option in the Recovery Console under Advanced Options. End

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.

checkdisk windows bug blue screen

The command would find numerous errors in a file called "9" and an error in the BITMAP attribute of the Master File Table according to the report.

The devices threw the stop error NTFS File System on reboot. Analysis of an active device, with check disk run already, showed that the Windows drive partition was returned as a RAW partition, suggesting that the repairs of the Check Disk tool damaged the NTFS file system.

Further analysis provided the following information:

  • Systems with Windows 10 20H2 appear to be affected.
  • The issue seems to affect Solid State Drives. One user reported that a VM system with a platter-based hard drive was affected as well.
  • The cumulative update KB4592438, released on December 8, 2020 as part of the December 2020 Patch Tuesday, seems to be the cause of the issue.

Other factors are not clear at this point in time. It is unclear if all devices running Windows 10 version 20H2 are affected or if a subset of devices that match certain characteristics are. It has been confirmed that a fresh Windows 10 20H2 installation is not affected.

Administrators should back up the Windows partition prior to running Check Disk on devices running Windows 10 20H2 with the December 2020 update installed.

1 Reply
Esteemed Contributor III

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

That explains the strange issues I had when I ran CHKDSK /R/F on my wife's Windows drive due to Windows taking over 3 hours to load due to HDD running at `100% all the time with the CPU load at less than 4%.

I did a Windows In-Place Repair with no change in HDD running at 100%. So I decided to run CHKDSK /F/R. When my wife's computer booted into Repair mode and started Chkdsk I went to bed.

In the morning I woke up to a BSOD on my wife's computer. Restarted and again started Repair mode with Chkdsk running. Let it run a second time and rebooted but again started up with Repair mode and started running Chkdsk. Rebooted a third time before letting Chkdsk run again and this time it loaded into Windows Desktop normally.

I then was able to run Windows Backup and Macrium Backup successfully and the HDD was now running normally.

0 Kudos