Tuesday’s update causes Windows 10 to blue screen • Registry

[ad_1]

Some Windows 10 users who installed cumulative update KB5021233 this month are experiencing their operating system crashing with the Blue Screen of Death, warns Microsoft.

In an entry over the weekend in the Windows Health Dashboard, the company wrote that the update could cause “a mismatch between the versions of the hidparse.sys file in c:/windows/system32 and c:/windows/system32/drivers (assuming Windows is on a C: drives), which can cause signature validation to fail when cleanup occurs.”

The result is that the system starts to an error – 0xc000021a – marked by a blue screen (BSOD).

The issue affects multiple versions of Windows 10, including 22H2, 21H2, 21H1, and 20H2.

Microsoft writes that engineers are working on a fix, and in the meantime, they’ve developed a workaround using the Windows Recovery Environment (WinRE), a tool used to fix problems with operating systems that won’t boot:

The user will need to enter WinRE. If the device does not appear automatically in WinRE, here are the steps to enter it.

Select the Troubleshoot button.

Select the “Start Recovery, Troubleshooting, and Diagnostic Tools” button.

Select the “Advanced” button.

Select the Command Prompt button and wait for your device to restart, if necessary.

The machine should restart to the command prompt window. Users may need to sign in to their machines with their password before accessing the Command Prompt window.

Run the following command (IMPORTANT: If Windows is not installed to C:\windows, you will need to modify the command for your environment): xcopy C:\windows\system32\drivers\hidparse.sys C:\windows\system32\hidparse.sys

Once the previous command is complete, type: exit

Select the Continue button.

Windows should now start as expected.

Microsoft also warned users not to follow any workaround or delete hidparse.sys from their Windows\System32 folder.

KB5021233 was released on December 13 as part of the Big Tuesday patch release. According to Microsoft, the update was meant to fix an issue with the camera app that caused it to stop responding when memory was low.

This isn’t the first time Microsoft has had to address an issue caused by Patch Tuesday’s update. On the same day the updates were released, the software giant said it was looking into issues with some 2019 and 2022 Windows Server users who wanted to develop new virtual machines in some Hyper-V hosts.

The issue arose after installing two updates on Windows Server or Azure Stack HCI hosts managed by System Virtual Machine Manager (SCVMM) and in SDN-enabled environments with a network controller. As with Windows 10 problems, Microsoft has released a fix while it’s working on a fix. ®

Sources

1/ https://Google.com/

2/ https://news.google.com/__i/rss/rd/articles/CBMiQmh0dHBzOi8vd3d3LnRoZXJlZ2lzdGVyLmNvbS8yMDIyLzEyLzIwL21pY3Jvc29mdF93aW5kb3dzXzEwX2NyYXNoL9IBRmh0dHBzOi8vd3d3LnRoZXJlZ2lzdGVyLmNvbS9BTVAvMjAyMi8xMi8yMC9taWNyb3NvZnRfd2luZG93c18xMF9jcmFzaC8?oc=5

The mention sources can contact us to remove/changing this article

[ad_2]

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts