Microsoft addresses chkdsk bug causing boot failure on Windows 10
Microsoft has acknowledged an issue on Windows 10 devices causing boot failure when chkdsk tool-a command utility for checking volume for file system and file system metadata logical and physical error -has been used to repair logical file system error.
Here is the official statement from the company about the issue, “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.”
The bug was acknowledged as KB4592438 and KB4586853 updates issued for Windows 10 versions 2004 and 20H2 in December and November, respectively.
The issue has now been resolved for all non-managed devices. However, it takes 24 hours to self-propagate to all affected devices.
Microsoft says, “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. To find out more about using Group Policies, see Group Policy Overview.”
The company has provided mitigation measures to the users who damaged their computers file system due to the Chkdsk issue:
- Use Recovery Console for the starting up the device when failing to start up a few times,
- Choose “Advanced” option,
- Open Command Prompt and type chkdsk/f.
- Wait till chkdsk completes the scanning process. Once done, type exit,
- The device will then start up as expected. If it starts up in Recovery Console, click on Exit and continue to Window 10.
Once all these processes are completed, your device will run chkdsk again on the restart and fix any logical and physical errors.
