Why in the world would you blame Microsoft for something you had control over? Microsoft certainly works hard, as do we beta testers that work unpaid to work through all of the possible combinations of hardware/software that might cause an issue. 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. 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. Restarting your device might help the resolution apply to your device faster. Please note that it can take up to 24 hours for the resolution to propagate to non-managed devices. This issue is resolved and should now be prevented automatically on non-managed devices. The issue has been resolved according to Microsoft: Update: Microsoft confirmed the issue on the KB4592438 support page. 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.
