Running ChkDsk on Windows 10 20H2 can damage the file system and cause Blue Screen

Microsoft ‘s latest version of Windows 10, Windows 10 20H2, appears to have a bug that could damage the Windows partition file system and cause blue screens during reboots. Reports suggest that running ChkDsk on these devices could damage the file system and cause blue screens on the first restart of the system after terminating the operation of the scan disk.

Günter Born details the issue on his blog.

It tells how one administrator (German forum link) found the issue after updating systems to Windows 10 20H2 and running the chkdsk command c: / f after the update installation. The command checks drive c: for errors to repair them immediately if any are found.

checkdisk windows bug blue screen

The command found several errors in a file called “9” and an error in the BITMAP feature of the Main File Table according to the report.

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

Further analysis provided the following information:

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

Other factors are unclear at this time. It is unclear whether all devices running Windows 10 version 20H2 are affected or whether there is a subset of devices that match specific features. It has been confirmed that the new installation of Windows 10 20H2 is not affected.

Windows backup administrators should reboot before running Check Disk on devices running Windows 10 20H2 with the December 2020 update installed.

Microsoft has not confirmed the case.

Now You.: Have you noticed anything like this on Windows 10 20H2 systems?

Summary

Running ChkDsk on Windows 10 20H2 can damage the file system and cause Blue Screen

Article Name

Running ChkDsk on Windows 10 20H2 can damage the file system and cause Blue Screen

Description

Microsoft ‘s latest version of Windows 10, Windows 10 20H2, appears to have a bug that could damage the Windows partition file system and cause blue screens during reboots.

Author

Martin Brinkmann

Publisher

Ghacks Technology News

Logo

Sanas

Source