[German]Security update KB5012599, released by Microsoft on April 12, 2022, for Windows 10 and Windows Server causes issues on some systems. The installation aborts with the error code 0x800F0831 or the error code 0x8024200B. I had pointed out the problem and outlined suggested solutions for an individual fix. However, this becomes a problem especially in enterprise environments when several hundred clients refuse to install the update. I now have unofficial information that this issue will be fixed by Microsoft on the upcoming patchday, May 10, 2022.
Update KB5012599 installation error
Cumulative update KB5012599 is available for Windows 10 version 20H2 – 21H2 and Windows Server 20H2. The update contains security fixes, but no new operating system features. The patch is offered automatically via Windows Update, but is also available from the Microsoft Update Catalog and via WSUS and WUfB (see also my blog post Patchday: Windows 10 Updates (April 12, 2022)).
Regarding update KB5012599, however, there are various user reports that it cannot be installed, but is aborted with the error code 0x8024200B. After initial comments here on the blog, I addressed the issue in the post Windows 10 Update KB5012599 stalls with install error 0x8024200B and 0x800F0831. Administrators were able to reset incorrect registry entries for the Component Based Servicing stack using the instructions given. This allowed the 0x8024200B and possibly 0x800F0831 installation errors to be resolved. However, the effort required for this solution is sometimes considerable.
Microsoft plans a fix
My German and English blogs now acts as a honeypot, where reader confirmations of problems are frequently posted. In the case outlined above, I was getting informed via various channels that individual administrators have opened a support ticket with Microsoft regarding the installation errors. As a result, Microsoft is aware of the error and it has been investigated.
In the comments of my blog post Windows 10 Update KB5012599 stalls with install error 0x8024200B and 0x800F0831, two users came forward with more information last week. On May 4, 2022, blog reader Sherman reported that Microsoft had told his company that a fix was planned for the May 2022 patchday. Blog reader Harris followed up with more concrete information on May 5, 2022, writing:Just got the same confirmation today.
Root Cause Category: Code Defect
Root Cause Details: "This is a regression caused by SSU changes made in ioT DCR change."
Mitigation Steps: "Fix has been checked in and on track for 5B"
The cause is a broken code that was distributed to the Windows 10 clients by a Servicing Stack Update (SSU). What exactly is behind the change in the IoT DCR code, I could not find out. Anyway, the message is that a fix is being planned for B-week in May 2022 – and that would be May 10, 2022.
Cookies helps to fund this blog: Cookie settings