Patch Tuesday update is causing some Windows 10 systems to blue screen
(2022/12/20)
- Reference: 1671496207
- News link: https://www.theregister.co.uk/2022/12/20/microsoft_windows_10_crash/
- Source link:
Some users running Windows 10 who installed the KB5021233 cumulative update this month are seeing their operating system crash with the Blue Screen of Death, Microsoft is warning.
In an entry over the weekend in its [1]Windows Health Dashboard , the company wrote that the update might cause "a mismatch between the file versions of hidparse.sys in c:/windows/system32 and c:/windows/system32/drivers (assuming Windows is installed to your C: drive), which might cause signature validation to fail when cleanup occurs."
The result is the system starting up to an error – 0xc000021a – featuring the blue screen (BSOD).
[2]
The problem is affecting multiple versions of Windows 10, including 22H2, 21H2, 21H1, and 20H2.
[3]
[4]
Microsoft wrote that engineers are working on a fix for the problem and, in the meantime, have developed a workaround using 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 doesn't automatically star up into WinRE, the steps for getting into it are found [5]here .
[6]
Select the Troubleshoot button.
Select the "Start recovery, troubleshooting, and diagnostic tools" button.
Select the "Advanced Options" button.
[7]
Select the "Command Prompt" button and wait for your device to restart, if needed.
The device should restart to a Command Prompt window. Users might need to sign into their device with their password before getting to the Command Prompt window.
Run the following command (Important: If Windows is not installed to C:\windows you will need to modify the command to your environment): xcopy C:\windows\system32\drivers\hidparse.sys C:\windows\\system32\hidparse.sys
Once the previous command completes, type: exit
Select the "Continue" button.
Windows should now start up as expected.
Microsoft also warned users not to follow any other workaround or to delete the hidparse.sys from their Windows\System32 folder.
[8]Patch Tuesday updates spark errors when creating Hyper-V VMs
[9]Microsoft ain't the only one squashing exploited-in-the-wild bugs this month
[10]Pwn2Own contest concludes with nearly $1m paid out to ethical hackers
[11]Microsoft: Whoops, Patch Tuesday might screw your database connections
[12]KB5021233 was released December 13 as part of the larger [13]Patch Tuesday rollout. According to Microsoft, the update was aimed at fixing a problem with the Camera app that caused it to stop responding when the memory is low.
This is by now means the first time Microsoft has had to address an issue caused by a Patch Tuesday update. The same day the updates were released, the giant software maker said it was investigating [14]problems for some Windows Server 2019 and 2022 users who wanted to spin up 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 software-defined networking (SDN)-enabled environments with a network controller. As with the Windows 10 problems, Microsoft issued a workaround while working on a fix. ®
Get our [15]Tech Resources
[1] https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22H2
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/patches&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Y6FBcLwy84iiv-NYjrW4gQAAAAI&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/patches&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Y6FBcLwy84iiv-NYjrW4gQAAAAI&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/patches&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Y6FBcLwy84iiv-NYjrW4gQAAAAI&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[5] https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference?view=windows-11#entry-points-into-winre
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/patches&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Y6FBcLwy84iiv-NYjrW4gQAAAAI&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/patches&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Y6FBcLwy84iiv-NYjrW4gQAAAAI&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[8] https://www.theregister.com/2022/12/14/microsoft_patch_tuesday_vm/
[9] https://www.theregister.com/2022/12/14/microsoft_december_patch_tuesday/
[10] https://www.theregister.com/2022/12/13/pwn2own_wraps/
[11] https://www.theregister.com/2022/12/08/microsoft_windows_update_odbc/
[12] https://support.microsoft.com/en-us/topic/december-13-2022-kb5021233-os-builds-19042-2364-19043-2364-19044-2364-and-19045-2364-44e774aa-60c4-4e38-b7e7-c886d210db3b
[13] https://www.theregister.com/2022/12/14/microsoft_december_patch_tuesday/
[14] https://www.theregister.com/2022/12/14/microsoft_patch_tuesday_vm/
[15] https://whitepapers.theregister.com/
In an entry over the weekend in its [1]Windows Health Dashboard , the company wrote that the update might cause "a mismatch between the file versions of hidparse.sys in c:/windows/system32 and c:/windows/system32/drivers (assuming Windows is installed to your C: drive), which might cause signature validation to fail when cleanup occurs."
The result is the system starting up to an error – 0xc000021a – featuring the blue screen (BSOD).
[2]
The problem is affecting multiple versions of Windows 10, including 22H2, 21H2, 21H1, and 20H2.
[3]
[4]
Microsoft wrote that engineers are working on a fix for the problem and, in the meantime, have developed a workaround using 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 doesn't automatically star up into WinRE, the steps for getting into it are found [5]here .
[6]
Select the Troubleshoot button.
Select the "Start recovery, troubleshooting, and diagnostic tools" button.
Select the "Advanced Options" button.
[7]
Select the "Command Prompt" button and wait for your device to restart, if needed.
The device should restart to a Command Prompt window. Users might need to sign into their device with their password before getting to the Command Prompt window.
Run the following command (Important: If Windows is not installed to C:\windows you will need to modify the command to your environment): xcopy C:\windows\system32\drivers\hidparse.sys C:\windows\\system32\hidparse.sys
Once the previous command completes, type: exit
Select the "Continue" button.
Windows should now start up as expected.
Microsoft also warned users not to follow any other workaround or to delete the hidparse.sys from their Windows\System32 folder.
[8]Patch Tuesday updates spark errors when creating Hyper-V VMs
[9]Microsoft ain't the only one squashing exploited-in-the-wild bugs this month
[10]Pwn2Own contest concludes with nearly $1m paid out to ethical hackers
[11]Microsoft: Whoops, Patch Tuesday might screw your database connections
[12]KB5021233 was released December 13 as part of the larger [13]Patch Tuesday rollout. According to Microsoft, the update was aimed at fixing a problem with the Camera app that caused it to stop responding when the memory is low.
This is by now means the first time Microsoft has had to address an issue caused by a Patch Tuesday update. The same day the updates were released, the giant software maker said it was investigating [14]problems for some Windows Server 2019 and 2022 users who wanted to spin up 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 software-defined networking (SDN)-enabled environments with a network controller. As with the Windows 10 problems, Microsoft issued a workaround while working on a fix. ®
Get our [15]Tech Resources
[1] https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22H2
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/patches&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Y6FBcLwy84iiv-NYjrW4gQAAAAI&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/patches&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Y6FBcLwy84iiv-NYjrW4gQAAAAI&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/patches&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Y6FBcLwy84iiv-NYjrW4gQAAAAI&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[5] https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference?view=windows-11#entry-points-into-winre
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/patches&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Y6FBcLwy84iiv-NYjrW4gQAAAAI&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/patches&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Y6FBcLwy84iiv-NYjrW4gQAAAAI&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[8] https://www.theregister.com/2022/12/14/microsoft_patch_tuesday_vm/
[9] https://www.theregister.com/2022/12/14/microsoft_december_patch_tuesday/
[10] https://www.theregister.com/2022/12/13/pwn2own_wraps/
[11] https://www.theregister.com/2022/12/08/microsoft_windows_update_odbc/
[12] https://support.microsoft.com/en-us/topic/december-13-2022-kb5021233-os-builds-19042-2364-19043-2364-19044-2364-and-19045-2364-44e774aa-60c4-4e38-b7e7-c886d210db3b
[13] https://www.theregister.com/2022/12/14/microsoft_december_patch_tuesday/
[14] https://www.theregister.com/2022/12/14/microsoft_patch_tuesday_vm/
[15] https://whitepapers.theregister.com/
It's nearly 2023 and still ...
... the fine folks in Redmond don't properly test patches before rolling them out.
I'm absolutely astonished that the Corporate World keeps falling for it, year after year, decade after decade. You'd think they'd have learned by now.
I wonder how many tens of billions of dollars have been lost in man-hours alone due to Microsoft incompetence. And the Corporate Lawyers allow this crap in the building? Still? Mind boggling.