KB5021233 triggers blue screens with 0xc000021a faults
Microsoft is investigating a regarded situation foremost to Blue Display of Loss of life (BSOD) crashes with 0xc000021a mistakes soon after putting in the Home windows 10 KB5021233 cumulative update launched throughout this month’s Patch Tuesday.
The firm warned about the weekend that “following setting up KB5021233, some Windows units could possibly start up to an mistake (0xc000021a) with a blue screen.”
This comes following a stream of end users stories on Redmond’s very own local community web-site [1, 2, 3] and Reddit [1, 2, 3], some of them reporting that the update reverted quickly or that they’ve been in a position to fix the problem immediately after a technique restore.
The recognized difficulty is probably triggered by a mismatch among the file versions of hidparse.sys in system32 and procedure32/motorists in the Home windows folder, “which may possibly trigger signature validation to fail when cleanup takes place.”
The list of influenced platforms consists of only shopper Home windows 10 versions, from Home windows 10 20H2 to the hottest launch, Windows 10 22H2.
Redmond included that it is really now operating on a fix to deal with this recently acknowledged concern but hasn’t yet shared when it will be available.
Workaround for impacted Windows 10 methods
Even so, the organization did share a short term remedy to workaround the blue monitor issue and revive the afflicted techniques to get started as envisioned.
This necessitates users to duplicate the hidparse.sys file from the procedure32motorists folder into technique32 by way of the Home windows Recovery Ecosystem (WinRE) so that the signature validation no more time fails all through cleanup.
To mitigate this difficulty on impacted products, you require to go by the next techniques:
- You will require to enter Windows Recovery Natural environment. If your machine has not instantly started off up into WinRE, please see Entry points into WinRE.
- Find the Troubleshoot button.
- Pick out the “Start out recovery, troubleshooting, and diagnostic resources” button.
- Select the “Superior Alternatives” button.
- Find the “Command Prompt” button and wait for your product to restart, if required.
- Your unit need to restart to a Command Prompt window. You may need to have to signal into your unit with your password prior to finding to the Command Prompt window.
- Run the following command (Significant: If Windows is not installed to C:windows you will need to modify the command to your setting): xcopy C:windowssystem32drivershidparse.sys C:windowssystem32hidparse.sys
- Once the previous command completes, form: exit
- Choose the “Carry on” button.
- Windows really should now start off up as expected.
“It is not suggested to follow any other workaround than individuals advised above. We do not advise deleting the hidparse.sys from your WindowsSystem32 folder,” Microsoft additional.
Redmond is also investigating a recognized issue linked to this month’s Windows Server Patch Tuesday updates that triggers mistakes when developing new digital devices on some Hyper-V hosts.