Question Windows update failed

[emitfudd]

KB5034441: Windows Recovery Environment update for Windows 10, version 21H2 and 22H2: January 9, 2024​

This update will not install. All other available updates installed normally. Tried restarting PC and it still failed. Since this update was just issued yesterday should I be concerned or just wait until Microsoft issues a fix.

I just saw another post about this. However it seems there are more than one issue here. The linked article says:

This update addresses a security vulnerability that could allow attackers to bypass BitLocker encryption by using Windows Recovery Environment (WinRE). For more information, see CVE-2024-20666.

IMPORTANT Some computers might not have a recovery partition that is large enough to complete this update. Because of this, the update for WinRE might fail. In this case, you will receive the following error message: Windows Recovery Environment servicing failed. (CBS_E_INSUFFICIENT_DISK_SPACE) I have no such message. The consensus seems to be to wait for Microsoft to issue a fix.

 

[Darkbreeze]

The consensus would be right. I mean, what else can you do? Aside from doing a clean install, running through all the updates again and hoping you don't end up with the same failure, there is literally nothing else you can do and no other options. At least, not at this point.

It's always possible that if MS doesn't immediately fix the problem with a patch, assuming its widespread and not just on your machine, that a work around or other repair might be created but I wouldn't hold my breath on that. So long as all other updates are working correctly and the rest of Windows is functioning normally, I'd not worry and just wait.

 

[WaterOS]

assuming its widespread and not just on your machine

Yeah, it's widespread. In the Microsoft official community, there are a lot of complains. Also, I have the same problem. My first thread in this forum was about the problem.

 

[USAFRet]

The ...4441 update worked fine on my Win 10 Pro system.
It DID fail initially, but after a reboot and try again, it worked.

 

[MajorPager]

but after a reboot and try again, it worked.

I wish my luck was that good, but alas, it is not.

For the past few days almost all my systems I have with Windows 10 have gotten this error, except for a 32-bit version I installed 4 days ago. I mostly found out that it was another one of Microsoft's screw-ups through their community forum today, and it's pretty bad. I thought at first that it was my computer only, but I was so very wrong.

 

[Darkbreeze]

https://www.tomshardware.com/softwa...s-leading-to-errors-and-has-a-complicated-fix

 

[emitfudd]

I don't use Bitlocker. Ignoring this issue for now.

 

[Darkbreeze]

Are you sure about that, because a lot of devices use it by default, especially if Secure boot is enabled, and it doesn't necessarily require YOU to opt in.

 

[emitfudd]

Are you sure about that, because a lot of devices use it by default, especially if Secure boot is enabled, and it doesn't necessarily require YOU to opt in.

I just checked. It is off for both drives.

 

[Darkbreeze]

Well, narrower and narrower. Back to wait I guess. Pretty sure the encryption problem isn't the ONLY one related to that update, and if it IS, then your problem is something else not even related to Windows update.