If you still have Windows 10 installed on your computer and you have installed KB5021233, the latest update released on December 13, you may be experiencing an issue that causes your computer to boot and crash to a blue screen. If so, don’t worry (too much), you’re not alone. With this update, Microsoft has officially acknowledged the issue and added the issue to the release status dashboard along with the steps needed to resolve the issue.

According to Microsoft, the problem occurs because of versions of the named file. hidparse.sys, stored in folders windows/system32 and windows/system32/drivers It may differ on the drive where Windows is installed. This causes the signature verification to fail, which means the computer cannot boot.

Fortunately, the problem can be fixed without reinstalling the operating system or anything like that. You will need to boot into the Windows Recovery Environment (WinRE) first; this should happen automatically after your device fails to boot correctly several times. After that do the following:

1. Click “Troubleshooting“, and “Run recovery, troubleshooting and diagnostic tools“.
2. Choose “Additional parameters“, and “Command Line“. This will reboot the device in the command line interface.
3. When you see a command prompt window, type the following command (you may need to change the drive letter from C to another if Windows is installed on a different drive): xcopy C:\windows\system32\drivers\hidparse.sys C: \windows\system32\hidparse .sys ​This will copy the file from one folder to another so that both locations have the same version.
4. To enter exit and press Enter to close the Command Prompt window and restart the computer.
5. click “Go on”and your computer should start Windows normally.

While following these steps may seem a bit daunting if you’ve never done it before, it’s actually pretty painless and you won’t have to lose any data or wait too long to get your PC back up and running. Once you’ve done that, you’re all set. With all that being said, Microsoft should address this issue in a future update, but that probably won’t be until January as we’re in the middle of the holiday season and there won’t be any additional updates in the second half of December. Windows 11 doesn’t have this problem, so if you have this version you don’t have to worry.