Microsoft pulls Microsoft Windows 11 and Microsoft Windows 10 updatess failing with 0x80070643

Microsoft has lastly pulled the botched Microsoft Windows updatess that triggered the 0x80070643 error message for hundreds. It’s insane that it took Microsoft about seven months to even acknowledge that three updatess it launched nowin the previous— Microsoft Windows 10 KB5034441, Microsoft Windows 11 KB5034440, and Microsoft Windows Server 2022 KB5034439—have been a damaged mess.

Microsoft shipped Microsoft Windows 10 KB5034441 and different updatess in January in an try to handle potential issues with the Microsoft Windows Recovery Environment. In the identical week, Microsoft confirmed that there have been set up issues with KB5034441, KB5034440, and KB5034439, the place the updatess might fail to put in with a 0x80070643 error.

For these unware, putting in KB5034441 or the opposite two updatess was obligatory, as they patched a vital BitLocker bypass flaw (CVE-2024-2066).

Unfortunately, a Microsoft Windows bug incorrectly affected some gadgets with an error message “‘0x80070643 – ERROR_INSTALL_FAILURE”, which suggests lack of house on the recovery partition, however folks with enough storage additionally encountered the bug.

“The WinRE partition requires 250 megabytes of free space. Devices which do not have sufficient free space will need to increase the size of the partition via manual action,” Microsoft beforehand stated. The firm revealed a protracted workaround that manually will increase the dimensions of the partition.

This problem affected hundreds of customers, with one of many affected customers explaining the issue in a Feedback Hub publish:

“After resolving the lack of free disk space on my recovery partition, the patch appears to apply with a success message in the updatess log. However, it keeps re-applying every time I check for updatess. Also, when I mount the recovery image and search for packages with a date of January 2024, I can’t find any,” one of many affected customers identified.

In February, we observed that these three updatess have been damaged and failing to put in on hundreds of PCs. Nothing had modified, because the official assist paperwork nonetheless advisable that folks manually resize their Microsoft Windows Recovery partition for the updates to put in easily.

Fast ahead to April, KB5034441 and the opposite two updatess have been nonetheless failing to put in.

Microsoft maintained radio silence, asking everybody to comply with lengthy directions that didn’t even work for a lot of configurations.

Finally, in May, Microsoft updatesd its assist doc to substantiate that it wouldn’t publish an computerized repair for the 0x80070643 error, and affected customers wanted to take care of the mess on their very own.

Microsoft releases latest KB5042320, KB5042321, or KB5042322 to switch the yanked updatess

After greater than seven months of confusion and chaos, Microsoft has lastly pulled the set off on three obligatory safety updatess— Microsoft Windows 10 KB5034441, Microsoft Windows 11 KB5034440, and Microsoft Windows Server 2022 KB5034439.

In an updates to the assist doc, which we observed through Microsoft’s RSS feed, the tech large confirmed that it had eliminated the above three updatess.

“Moved this content from updates KB5034441, which has been retired,” Microsoft famous within the updatesd doc. “After installing this updates, the WinRE version installed on the device should greater than or equal to version 10.0.19041.3920​​​​​​​,” the corporate added.

Those who haven’t put in previous updatess like KB5034441 shall be supplied to obtain Microsoft Windows 10 KB5042320, Microsoft Windows 11 KB5042321, or Microsoft Windows Server 2022 KB5042322 (relying on the model of Microsoft Windows you employ) to patch the WinRE vulnerability (CVE-2024-2066).

While Microsoft has yanked KB5034441, KB5034440, and KB5034439, it’s nonetheless obligatory to obtain the latester variations.  That’s as a result of unpatched PCs are susceptible to an exploit documented as “CVE-2024-20666,” which permits an attacker to entry BitLocker-encrypted information.

What a large number, proper? I’ve created a desk that sums up the rollout of this Microsoft Windows safety updates:

The problem has been lastly mounted, and also you’ll not run into the Microsoft Windows updates failure when putting in the latest updatess launched nowthis week.