Microsoft issues KB5034440, KB5034441 Windows updates for BitLocker Secure Boot flaw

Wolfzz · Jan 10, 2024

Microsoft issues KB5034440, KB5034441 Windows updates for BitLocker Secure Boot flaw

Microsoft has addressed a security vulnerability that can lead to BitLocker Secure Boot bypass on both Windows 10 and 11. Alongside that, the company has also detailed how to resize the WinRE space.

www.neowin.net

BamaInArk · Jan 10, 2024

And apparently KB5034441 is having issues for many on Win10.

Bree · Jan 10, 2024

Yes, I was one of those with errors installing KB5034441 in Win10.

KB5034441 updates the recovery environment. It will fail if...

the recovery partition is too small to be updated (see the MS resizing instructions)
The recovery environment is missing (recovery partition has been deleted without first disabling the recovery environment)
The recovery environment files are corrupted.

For the last two the fix is to repair the recovery environment by extracting new copies of ReAgent.xml and WinRE.wim from the install.esd or install.wim in the sources folder of the install media and placing them in "C:\Windows\System32\Recovery".

Ghot · Jan 10, 2024

More info...

Fix 0x80070643 - Error Install Failure when trying to install Windows Update - gHacks Tech News

Find out how to fix the error message 0x80070643 - Error Install Failure when trying to install the latest Windows Update.

www.ghacks.net

These directions seem a bit clearer than MS's directions.
They're the same directions, just laid out a bit better.

barreleye · Jan 10, 2024

I got it for my Windows 10 systems, but is this problem fixed in Windows 11 23H2? The confusing neowin article starts by talking about the Patch Tuesday update KB5034123, which was successfully installed on my system, but it doesn't actually say it addresses the problem. It goes on to talk about KB5034440, but the Microsoft document says it's for Windows 11, version 21H2. Indeed, that update has not been installed on my system, and when I follow the instructions to view the Service Pack Build for WinRE, it appears low, and I don't see where to get the "UBR" for the update to compare it to anyway, so this isn't even helpful:

Add an update to Windows RE

Add an update package to Windows RE.

learn.microsoft.com

Code:

T>Dism /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk3\partition4\Recovery\WindowsRE\winre.wim /index:1

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Details for image : \\?\GLOBALROOT\device\harddisk3\partition4\Recovery\WindowsRE\winre.wim

Index : 1
Name : Microsoft Windows Recovery Environment (amd64)
Description : Microsoft Windows Recover Environment (amd64)
Size : 2,699,067,084 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.22621
ServicePack Build : 382
ServicePack Level : 0
Edition : WindowsPE
Installation : WindowsPE
ProductType : WinNT
ProductSuite :
System Root : WINDOWS
Directories : 4526
Files : 19190
Created : 5/6/2022 - 11:53:32 PM
Modified : 9/22/2022 - 9:47:02 PM
Languages :
        en-US (Default)
The operation completed successfully.

So, is this fixed in Windows 11 23H2, and if so, what fixed it and where is it documented, and how can you tell?

starchase · Jan 11, 2024

Just to clarify some confusion about stepping through the 14 part cure referenced in the "simplified" instruction link, can not one just run Mini Tool and increase the size of the Recovery Partition that way?

BamaInArk · Jan 11, 2024

starchase said:
Just to clarify some confusion about stepping through the 14 part cure referenced in the "simplified" instruction link, can not one just run Mini Tool and increase the size of the Recovery Partition that way?

That one(mini-tool) is easy enough to use.

starchase · Jan 11, 2024

starchase said:
Just to clarify some confusion about stepping through the 14 part cure referenced in the "simplified" instruction link, can not one just run Mini Tool and increase the size of the Recovery Partition that way?

Well, I did use mini-tool to increase the size of the recovery partition from around 350 MB to 800 MB; there were some files in that partition since the free space was nowhere near the partition size. (I had been using version 9 and when I restarted the PC to effect the changes made, Partition Magic did restart but stopped before making any changes! I tried twice and failed the same. So I downloaded the latest version and it completed without a hitch! That was strange!

But Windows still failed to download. Turns out resizing removed whatever was originally in the Recovery partition. But running

Code: