neowin[.]net/news/microsoft-fixes-windows-10-chkdsk-issue-that-corrupted-disks-and-caused-blue-screens
bleepingcomputer[.]com/news/microsoft/microsoft-fixes-windows-10-chkdsk-bug-causing-boot-failures/
Hopefully you haven't experienced this problem -- don't imagine loads of people run chkdsk from the command prompt rather than the error checking in drive properties when running Windows Explorer. The bug is a result of the November &/or December 2020 updates, with Microsoft saying: "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". Until the fix is rolled out, Microsoft says this is the workaround:
To repair their devices' boot capability, users are advised to go through the following procedure:The device should automatically start up into the Recovery Console after failing to start up a few times.
Select Advanced options.
Select Command Prompt from the list of actions.
Once Command Prompt opens, type: chkdsk /f
Allow chkdsk to complete the scan, this can take a little while. Once it has completed, type: exit
The device should now start up as expected. If it restarts into Recovery Console, select Exit and continue to Windows 10.