• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Microsoft Did It Again! Beware Of Bugged Update KB5034441

sam_86314 said:
For anyone having this issue, here's a tool that can be used to hide the update.


I've also attached it in a zip file.

Yes, I'm having this issue on all of my Windows 10 computers.

No, I'm not resizing the partition just for this update to work.
Click to expand...
Hi,
Well ms did finally release a poweshell fix
Probably should release it as a update first before the other installs
Or add it to the update but ms is far less than perfect for sure lol
Devastator0 said:
Looks as though Microsoft has now released a powershell script for doing this

www.bleepingcomputer.com

Microsoft shares script to update Windows 10 WinRE with BitLocker fixes

Microsoft has released a PowerShell script to automate updating the Windows Recovery Environment (WinRE) partition in order to fix CVE-2024-20666, a vulnerability that allowed for BitLocker encryption bypass.
www.bleepingcomputer.com www.bleepingcomputer.com

I still won't run it until they fix the update itself.
Click to expand...
 
FoulOnWhite said:
I just got this update, never even noticed, says installed successfully, which is strange when my recovery partition is only 530mb.
View attachment 329448
Click to expand...

Wrong KB# you have there.

ThrashZone said:
Hi,
Well ms did finally release a poweshell fix
Probably should release it as a update first before the other installs
Or add it to the update but ms is far less than perfect for sure lol
Click to expand...

If a PS script can patch the security hole WITHOUT resizing the partition then why the hell the update can't?
 
Regeneration said:
Wrong KB# you have there.



If a PS script can patch the security hole WITHOUT resizing the partition then why the hell the update can't?
Click to expand...
The PS script actually enlarges the partition
Now if ms added it to the update it would be a perfect world hehe
 
Bill_Bright said:
What is a "vanilla" install?

It is probably safe to say if the computer is a factory assembled computer (HP, Dell, Acer, etc.) it is not vanilla.

If the computer (or rather boot disk) is brand new and the user does a fresh install of the OS, then it likely would be the first partition.

But, if the disk previously had Windows 7, for example on it, there may be an older, recovery partition already there that is too small - so the new install will create partition. It would be nice if it just enlarged the first, but not that would be wise for MS to assume that is safe - I don't know what happens to recover partitions when multiple OSs are installed on the same disk, for example.

There might be multiple recovery partitions created if W10 was updated by a major W10 update and the original recovery partition was too small.
Click to expand...
To me vanilla is when you select empty disk and let Microsoft auto create the partitions.

Here is my observation of vanilla.

Pre build 2004, RE before C: and sized 499MB.
21H2, RE after C: and sized 528MB. Confirmed by Assimilator.
Upgrade installs, feature upgrades etc. inherit previous partitions.
 
Last edited:
chrcoluk said:
To me vanilla is when you select empty disk and let Microsoft auto create the partitions.

Here is my observation of vanilla.

Pre build 2004, RE before C: and sized 499MB.
21H2, RE after C: and sized 528MB. (note this is from a custom ISO where I integrated some drivers on to RE, which might be why its 29MB bigger, and not a change on Microsoft's default sizing scheme).
Upgrade installs, feature upgrades etc. inherit previous partitions.
Click to expand...
Mine is also 528MB (well, 529MB), nothing custom.
 
This update was failing for me because the Recovery Environment was missing. This may have been because the original installation had been cloned to a larger drive and during this the Recovery partition had been copied but not its full contents.

So the usual solution - create Windows 10 install on a USB key, copy install.esd to NVME drive, extract the install.wim file for my version from the esd, and use 7Zip to copy ReAgent.xml and WinRE.wim to C:\Windows\System32\Recovery.

Then to enable the WinRE use Reagentc /enable from a command window. At this point the underlying cause of the loss of the RE is evident. ReAgentc moves WinRE.wim to the Recovery partition, it doesn't just copy it. So if anything happens to the Recovery Partition, it's back to square one. Solution, create a folder such as WinREBackup on the install USB key and copy ReAgent.xml and WinRE.wim to it before using Reagentc. Future recovery of WinRE is then just a simple copy job.
 
pressing on said:
This update was failing for me because the Recovery Environment was missing. This may have been because the original installation had been cloned to a larger drive and during this the Recovery partition had been copied but not its full contents.

So the usual solution - create Windows 10 install on a USB key, copy install.esd to NVME drive, extract the install.wim file for my version from the esd, and use 7Zip to copy ReAgent.xml and WinRE.wim to C:\Windows\System32\Recovery.

Then to enable the WinRE use Reagentc /enable from a command window. At this point the underlying cause of the loss of the RE is evident. ReAgentc moves WinRE.wim to the Recovery partition, it doesn't just copy it. So if anything happens to the Recovery Partition, it's back to square one. Solution, create a folder such as WinREBackup on the install USB key and copy ReAgent.xml and WinRE.wim to it before using Reagentc. Future recovery of WinRE is then just a simple copy job.
Click to expand...
Hi,
Yeah I referenced that process a little while back from someone on 11f posted
ThrashZone said:
Hi,
Ran into this yesterday about deleting the partition which I also used to do until I enlarged the original.

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

https://www.neowin.net/news/microsoft-issues-kb5034440-kb5034441-windows-updates-for-bitlocker-secure-boot-flaw/
www.elevenforum.com www.elevenforum.com

View attachment 329413
Click to expand...
 
Regeneration said:
There is no partition adjustment in this script. In BleepingComputer's article, they confirm it too.
Click to expand...
Hi,
Odd but even odder is my recovery partition on two systems got smaller after the update installed
So making the partition larger don't ask me bro the whole ordeal is a MS brain fart :laugh:

They do reference a third party that does offer a script to resize it but yeah unknown to myself hehe
 
Regeneration said:
Windows 11 - KB5034440, KB5033560.
Click to expand...

Well I'm fully updated (windows 11 Pro) and not seeing these you mentioned in my update history....

Screenshot 2024-01-13 150335.png

Screenshot 2024-01-13 150402.png




Security Update Guide - Microsoft Security Response Center

msrc.microsoft.com msrc.microsoft.com

Screenshot 2024-01-13 150645.png
 
P4-630 said:
Well I'm fully updated (windows 11 Pro) and not seeing these you mentioned in my update history....

View attachment 329535
View attachment 329536



Security Update Guide - Microsoft Security Response Center

msrc.microsoft.com msrc.microsoft.com

View attachment 329537
Click to expand...

Same. On 23H2 only three updates were downloaded and installed - the cumulative one, MSRT and .NET update. That’s it. As MS said in its security bulletin, for 11 22H2 and 23H2 the fix for the BitLocker bug is in the CU and seems to require no WinRE messing around.
 
Regeneration said:
Windows 11 - KB5034440, KB5033560.

Windows 10 - KB5034441

Sometimes the error message will not appear in Windows Update just like that.

You'll have to check the full updates history to see it.
Click to expand...
Hi,
Yeah I don't have either one on 11.
I mounted 11 pro 23h2 12-18-2023 and haven't updated since until yesterday
So the two you posted were pulled as far as I can tell.
Not in history or uninstall list either.
 
Can't download and install KB5034441, and of course MS wants me to increase the recovery partition in question which is already at 529mb ?!
Can i change the size using Disk Genius safely and is there a place to find written instructions ?

Or should i just hold tight and wait for this update to be sorted my MS..?
recovery.jpg
 
Ivan Bliminse said:
Can't download and install KB5034441, and of course MS wants me to increase the recovery partition in question which is already at 529mb ?!
Can i change the size using Disk Genius safely and is there a place to find written instructions ?

Or should i just hold tight and wait for this update to be sorted my MS..?
View attachment 329579
Click to expand...
Hi,
Yeah either DG or free minitool will work
As long as you know either will move the os to accommodate the new size
I wouldn't bother if not more than 1gb
Otherwise you can make a new at the end of C with these instructions

CMD format ssd for install

Here's the lappy
www.elevenforum.com www.elevenforum.com

Only item missing is the remove partition letter
I used Z
Code: 
remove letter=Z

By the way the other two will see the recovery as any other partition so just right click it and select move or resize.
Apply.
You will likely be restarted to apply the changes.
 
Followed instructions to the letter, Operation Successful.

It now states - Update will not download and install.. :banghead:
 
Last edited:
Ivan Bliminse said:
Followed instructions to the letter, Operation Successful.

It now states - Update will not download and install.. :banghead:
Click to expand...
Which one post another screen shot.
You might just have to clear updates history.
www.elevenforum.com

Clear Windows Update History in Windows 11

This tutorial will show you how to clear the Windows Update history on your Windows 11 PC. Windows Update keeps Windows 11 updated by automatically downloading and installing the latest updates, drivers, and hotfixes released by Microsoft. Reference...
www.elevenforum.com www.elevenforum.com

Also include the cdm as admin read out with
reagentc /info

The way that actually worked for me
I already had space in front of C
Just created a primary partition with Z letter in free minitool
Then in cmd as admin
Used
Code: 
diskpart
list disk
select disk 0?
list par
select par 0 "should show Z"

CMD output to above commands
Code: 
C:\Users\masqww-lp\Desktop>diskpart

Microsoft DiskPart version 10.0.22621.1

Copyright (C) Microsoft Corporation.
On computer: MASQWW-LP

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          953 GB   551 GB        *
  Disk 1    Online         3726 GB    62 GB        *

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> list par

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Recovery          2912 MB  1024 KB
  Partition 2    System             260 MB  2913 MB
  Partition 3    Reserved            16 MB  3173 MB
  Partition 4    Primary            399 GB  3189 MB

DISKPART> select par 1

Partition 1 is now the selected partition.

DISKPART>

After the above and you selected the Z partition paste each line one at a time
Code: 
clean
set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac

GPT ATTRIBUTES=0x8000000000000001

format FS=NTFS quick label="Recovery Tools"

Then use
exit

Go back and select the recovery partition and use remove letter
remove letter=Z
exit again.

Make sure the letter is gone after restart if not use minitool to remove it
Right click it and select remove letter. apply.

Go back to cmd and use
reagentc /info

And then
reagentc /enable
 
Last edited:
Sorry, should have said - I have win 10, not 11. Will it work the same with win 10..?!
 
Ivan Bliminse said:
Sorry, should have said - I have win 10, not 11. Will it work the same with win 10..?!
Click to expand...
Yeah it doesn't matter which os
To be accurate I do need the screen shots of the existing and outputs to commands though.

I'll probably be on a different computer in a bit so here's everything on one bit
Code: 
diskpart
list disk
select disk 0
list par
select par Z
clean
set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
GPT ATTRIBUTES=0x8000000000000001
format FS=NTFS quick label="Recovery Tools"
remove letter=Z
reagentc /info
reagentc /enable

If successful should have a readout like this
 

Attachments

  • Created new RE recovery tools partition.PNG
    Created new RE recovery tools partition.PNG
    176.3 KB · Views: 85
Ivan Bliminse said:
Can't download and install KB5034441, and of course MS wants me to increase the recovery partition in question which is already at 529mb ?!
Can i change the size using Disk Genius safely and is there a place to find written instructions ?

Or should i just hold tight and wait for this update to be sorted my MS..?
View attachment 329579
Click to expand...

You shouldn't mess around with your partitions just to install some update.

But if you insist, get a 3rd party partitioning software (like Paragon) that is capable to resize C and move the new free space to the begin of the drive (this could a take a while). Microsoft commands will not help because your partition is a bit unusual.
 
Thanks but i've chosen to hide the update..
 
You must log in or register to reply here.
Back
Top