IT Support Faces First Windows 10 Update Glitch After Paying for Security
296Some IT teams that recently started paying for Windows 10 security updates ran into their first support hiccup last week. Microsoft released a patch on November Patch Tuesday, but it didn’t go smoothly for everyone. The update, KB5068781, was meant for Windows 10 22H2 builds 19044.6575 and 19045.6575, but some devices couldn’t install it.
When trying to install the update, users saw an error message saying “error 0x800f0922 (CBS_E_INSTALLERS_FAILED).” Microsoft explained this problem mainly affects devices activated through Windows subscription activation via the Microsoft 365 admin center. This patch includes security fixes and improvements from October’s updates, but some devices couldn’t get it installed without issues.
Microsoft Fixes the Problem with a New Update
On November 17, Microsoft announced that they had fixed the issue with a new update called KB5072653, the Extended Security Updates (ESU) Licensing Preparation Package for Windows 10. Once this preparation package is installed, users can then successfully deploy the original security update (KB5068781). This means IT teams should first install KB5072653 before trying again to get the security fixes.
What IT Teams Can Do to Fix the Issue
Jack Bicer, who specializes in vulnerability research at Action1, says IT managers who faced this error before Microsoft released the fix should check if they have the latest servicing stack update (SSU). If not, they should install it first and then try the update again. Running the Windows Update Troubleshooter can also help identify and fix issues automatically.
For more stubborn problems, administrators can download the KB5068781 update manually from the Microsoft Update Catalog. To do this, they should run the command wusa.exe with the filename of the update, making sure they match their device’s architecture and version. If the update was installed but problems persist, it’s worth verifying the build number using the “winver” command. The correct build numbers are 19045.6575 for 22H2 and 19044.6575 for 21H2.
This situation highlights how even paid security updates can encounter unexpected bugs. But with the right steps, IT teams can get their systems fully protected again.
What do you think?
It is nice to know your opinion. Leave a comment.