Microsoft Did It Again! Beware Of Bugged Update KB5034441

[P4-630]

For me the update simply refused to install.

My dads windows 10 laptop wouldn't take this update either...

Oh well, he can still use it, probably until windows 10 EOL.

 

[ThrashZone]

Tbh. I think there is no "correct location" of the recovery partition since Windows doesn't care if it's in front or behind the "C" partition. I am not 100% sure why mine is at the end. I did a recovery to a new drive, also had a True Image recovery partition which I removed because it was pretty pointless if you have a recovery USB stick. I believe that was also the time when I created the Windows recovery partition after reading about the benefits.


The QA team is now the end user. The smartest way would be to delay updates in the Windows update options. Somehow I just can't resist to get them right away. What's also pretty dumb is that if you search for new updates with a delayed setting it starts to install if it finds anything. Some Microsoft logic right there. But you can cancel it if you want, so there is that.

Hi,
There is a best place only issue is ms has been on stupid so long making them to small and it seems they're stuck on stupid still throwing them at the end of the disk
Then issue an update that can't enlarge it if it's a little to small lol
It's really tough to make this stuff up hehe

Yeah the ms way usually is to just create another recovery at the end of C

You could just use free minitool and enlarge your existing recovery partition to 1gb minitool restarts the machine and moves a little bit of the os over to make room to expand recovery. boom task is done.
I've done it before on several rigs works just fine and you don't have to do anything in dysfunctional diskpart lol

 

[Princess Garnet]

Just got updates this morning and they seemed to go as usual, but I just checked Windows Update manually and that update is indeed listed as failed though. My partition size is 510 MB so I suppose I'll increase it to 1 GB or something and let it try again.

By the way, I did this yesterday (although I increased it 250 MB to a size of 760 MB instead) and I now see the once failed update is listed as successful.

I don't know if it tried to download/install itself and succeeded due to the change in the partition size, or if Microsoft did something to fix it on its end the same day.

 

[AusWolf]

You're wasting your time he's just being a argumentative duckhead lol

Hey, I agreed with you, didn't I?

 

[Bill_Bright]

The problem is that Microsoft is a de facto monopoly, and that means they don't have to try anymore.

Having worked in a large software development company for many years, and having worked with many Microsoft developers for many more, I will say the developers at Microsoft are highly qualified experts who do very much care out their products and try very hard to ensure they put out quality, "bug free" (regardless your definition of "bug" ), software.

The problem is NOT the developers. The problem is the marketing weenies and the execs (AKA: the bean counters) who force the developers to rush out products and updates before they are ready. W8 and the first iteration of Edge are perfect examples. They were pushed out way before they were ready, or in the case of Edge, finished.

 

[INSTG8R]

That was fun playing with Diskpart in CMD. Not done anything that complex in years. While a bother to have too was kinda interesting doing it.

 

[Devastator0]

Looks as though Microsoft has now released a powershell script for doing this

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

I still won't run it until they fix the update itself.

 

[ShrimpBrime]

This thread, it jinxeded me!!

Got home here, fire up the PC. Check out the news, kids school closures for the blizzard and of course Windows update.

I updated on Tuesday like everyone else. Had no issues everything worked fine.

Today, another update? OK, sure I installed it and it seemingly removed Vulkan API. The driver however is unchanged.

I'm using a Quadro K2200, which I have been benching. Ran 3DMark Wild Life Extreme like yesterday or the day before, Today 3DMark says Vulkan API is needed For Wild Life and check the driver. OK, So I did and GPU-Z agrees, it's been removed. Oh boy. I love to DDU and install drivers again for no reason.

Gonna try a restart first. Then a driver wipe and re-install. Wish me luck!!



2 days ago was fine.... lol.



UPDATE (10 minutes of time solved!)

DDU and install did the trick. If that's alI I has to deal with, happy with that.

 

[DaemonForce]

Today, another update? OK, sure I installed it and it seemingly removed Vulkan API. The driver however is unchanged.

I'm using a Quadro K2200, which I have been benching. Ran 3DMark Wild Life Extreme like yesterday or the day before, Today 3DMark says Vulkan API is needed For Wild Life and check the driver. OK, So I did and GPU-Z agrees, it's been removed. Oh boy. I love to DDU and install drivers again for no reason.

Always a super good sign on the tried and trusted mainstream OS when a driveby update in response to fixing a previous one manages to install and nonchalant takes out random core graphical features like Vulkan or possibly settings in Wattman. I have a feeling this arc is gonna go on for the next few days before it gets pulled entirely. What is MS doing?

 

[ThrashZone]

The problem is that Microsoft is a de facto monopoly, and that means they don't have to try anymore.


Ugh, I typed "boot" when I meant to type "system".

Hi,
Actually on MBR disk the system reserved/ recovery partition does have boot files on it so you were correct on that system setup.
Not sure if anyone besides myself and Lex use mbr anymore but I do for at least 3 systems

 

[adilazimdegilx]

It also failed for me but I dont even have RE partition I dont know why it tried to install it anyway...
Postponed updates for 1 month, hopefully they'll fix it.

 

[ThrashZone]

It also failed for me but I dont even have RE partition I dont know why it tried to install it anyway...
Postponed updates for 1 month, hopefully they'll fix it.

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

 

[Assimilator]

Looks as though Microsoft has now released a powershell script for doing this

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

I still won't run it until they fix the update itself.

That PowerShell script does no partition resizing. So can someone please explain to me why this problematic Windows update doesn't just do the exact same thing the script does?

This... this is not your everyday stupidity from Microsoft. This is advanced stupidity.

 

[ThrashZone]

Hi,
There's a lot about this string of updates to pass on

KB5034123 Windows 11 Cumulative Update Build 22621.3007 (22H2) and 22631.3007 (23H2)

UPDATE 1/23: https://www.elevenforum.com/t/kb5034204-windows-11-cumulative-update-preview-build-22621-3085-22h2-and-22631-3085-23h2.21841/ Microsoft Support: January 9, 2024 - KB5034123 (OS Builds 22621.3007 and 22631.3007) IMPORTANT After February 27, 2024, there will no longer be optional...

www.elevenforum.com

Known issues plus lock screen weather opening edge and msn weather

Thought I saw some wifi issues to but didn't see it here.

 

[FoulOnWhite]

On win 11 here, checked yesterday and today and no buggy update so i guess this affects win 10 only.

 

[P4-630]

On win 11 here, checked yesterday and today and no buggy update so i guess this affects win 10 only.

Microsoft Did It Again! Beware Of Bugged Update KB5034441

Maybe they're just trying to kill Windows 10 - sooner than expected. ;)

www.techpowerup.com

 

[ThrashZone]

Hi,
This is funny
MS now creating a new because they can only shrink C and not another partition between C and RE

Windows Created New Recovery Partition after Update - Windows 10 Help Forums

I note many people have had problems with failed Windows updates due to a small size recovery partition this week. I was not affected but note Windows inserted a new larger partition after the update this week. See this disk map from Partition Wizard. Dis

www.tenforums.com

One of a couple reasons why I wanted RE in front of C and larger so MS would stop the insanity of these idiot RE partition issues.
I have my doubts MS will reuse my larger RE partitions though it's just to damn sensible for them I believe

 

[A Computer Guy]

Hi,
This is funny
MS now creating a new because they can only shrink C and not another partition between C and RE

Windows Created New Recovery Partition after Update - Windows 10 Help Forums

I note many people have had problems with failed Windows updates due to a small size recovery partition this week. I was not affected but note Windows inserted a new larger partition after the update this week. See this disk map from Partition Wizard. Dis

www.tenforums.com

One of a couple reasons why I wanted RE in front of C and larger so MS would stop the insanity of these idiot RE partition issues.
I have my doubts MS will reuse my larger RE partitions though it's just to damn sensible for them I believe

I thought on vanilla installs MS always put the recovery partition first? It's like that with all my Win10 PC's but for some reason the size varies perhaps because I updated my SSD's to Samsung Pro's when they were discounted and used Acronis to copy the image of the drives.

 

[ThrashZone]

I thought on vanilla installs MS always put the recovery partition first? It's like that with all my Win10 PC's but for some reason the size varies perhaps because I updated my SSD's to Samsung Pro's when they were discounted and used Acronis to copy the image of the drives.

Hi,
It is in front of C
The issue is they are to small after a while
Otherwise you'd need to increase it's size for future growth ms to stupid fr that though

I Left some space before "a lot actually lol" a clean install so I could make create/ redirect the default one after the install
I hate the damn thing after C or worse at the end of a 1-2-4tb... disk lol
On efi/ gpt disk that is really hard so I did it after the install by redirecting it to the new one I created.

I just installed the new updates and they did reuse the new recovery partition I made with some help from one 11f members help after some lectures of how smart ms is blah... from a few over there lol
After creation it showed 16mb and now shows hair under 750mb

Now just need to disable the pos using reagentc /disable seeing on efi/ gpt Unlike a MBR system it makes it way to hard to boot to my WinPE recovery media so this has got to go I prefer the boot menu not going to bios and changing boot order.

 

[Bill_Bright]

I thought on vanilla installs MS always put the recovery partition first?

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.

 

[FoulOnWhite]

So this one seems to be it on my win11 23H2 system:
View attachment 329105

My Recovery Partition is 611 MB

I just got this update, never even noticed, says installed successfully, which is strange when my recovery partition is only 530mb.

 

[Easy Rhino]

Zorin OS or Linux Mint has you Windows 10 users covered.

 

[ThrashZone]

I just got this update, never even noticed, says installed successfully, which is strange when my recovery partition is only 530mb.
View attachment 329448

How the hell you manage D in front of C lol
Thinking an old dual boot ?

But yeah you broke the norm with that little RE that small and update installing.

 

[FoulOnWhite]

How the hell you manage D in front of C lol
Thinking an old dual boot ?

But yeah you broke the norm with that little RE that small and update installing.

Yeah it was dual boot, used it for media instead. Maybe i should have installed them the other way around putting win 11 section first. My PC boots and runs fine.


Yaay i'm not normal

 

[sam_86314]

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

https://download.microsoft.com/download/f/2/2/f22d5fdb-59cd-4275-8c95-1be17bf70b21/wushowhide.diagcab

I've also attached it in a zip file.

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

Main PC:

No, I'm not resizing the partition just for this update to work.