Microsoft Did It Again! Beware Of Bugged Update KB5034441

[A Computer Guy]

You are not alone. For every dorkwad who is willing to muck around with some partition utility, there are tens of thousands of consumers who have zero interest in this. Hell, most consumers aren't even inclined to upgrade their operating systems.

And how many corporate IT staffers want to diddle with this B.S.? Best practices would require a full backup of the system before the repartitioning exercise just in case something goes awry. Multiple that by hundreds (even thousands) of systems. Hell, they might be working on this when the February Patch Tuesday rolls around.

Ahahahahahahaha!!!!


Well clearly his continuing presence is not enough.

So Microsoft should fire everyone but Raymond and he can work alongside the AI. Still a better chance at decent Windows releases.

But no. Whoever is in charge of Windows software engineering will probably get a promotion next month...

And remember that even if Microsoft eventually fixes this particular update (which they will), they have squandered trust.

TRUST IS EARNED.

Not just the trust of consumers. Nor the trust of corporate IT staffers. Partners, third party software developers, technology journalists, even some of their own employees.

Wait what? We are trusting Microsoft?

Just checked my Windows 10. Pending! Guess now is a good time to backup before trying this.

 

[AusWolf]

If your recovery partition is less then 750MB (which it is for most PCs) it will always fail to download / install with code 0x80070643. It will just nag for eternity.

When you search around for that error code, Microsoft's solution is to tell people (even common people) to resize OS partitions.

Sure, but I mean, is it a problem if it doesn't install? What's in the update anyway?

 

[ThrashZone]

Sure, but I mean, is it a problem if it doesn't install? What's in the update anyway?

Repeating the install and write error over and over seeing it's security update.

Waiting for ms to finally recall it.

 

[AusWolf]

Repeating the install and write error over and over seeing it's security update.

That's a bit too vague to urge me to resize my OS partitions right away.

Waiting for ms to finally recall it.

That seems to be the proper course of action, in my opinion.

 

[ThrashZone]

That's a bit too vague to urge me to resize my OS partitions right away.


That seems to be the proper course of action, in my opinion.

Hi,
Yep
Making sure the updates service is disabled will help.

Bitlocker code patch is in the update by the way.

 

[Assimilator]

Not just the trust of consumers. Nor the trust of corporate IT staffers. Partners, third party software developers, technology journalists, even some of their own employees.

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

Not sure it's really a boot partition
The 100-260mb efi is which is not effected by recovery partition.

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

 

[ThrashZone]

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

Hi,
Yeah well in a way it is boot
WinRE does have startup repair tools hehe
But so does a windows installation media.

 

[AusWolf]

Bitlocker code patch is in the update by the way.

Thanks. I don't use BitLocker, so I think I'll be fine until MS fixes this update to install properly without my messing around.

 

[Regeneration]

That does not make it "buggy". It may be poor planning or misguided policy but those are different from bugs.

If an update gives error messages on vanilla, fresh Windows installation just out of the box then it is BUGGED.

 

[ThrashZone]

If an update gives error messages on vanilla, fresh Windows installation just out of the box then it is BUGGED.

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

 

[skizzo]

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

 

[MarsM4N]

Had the same issue. Apparently it only affects Win10 users, and for some even increasing the recovery partition to 2GB doesn't fix the issue. Well, I've tried the update today again, still failed with the "Error 0x80070643" . My recovery partition is at the end of the disk with tons of unallocated space in front of it, so I felt comfortable to just resize the recovery partition. Just a few clicks with MiniTool® Partition Wizard Free and the job was done. Did a restart, then kicked off the update & it went through without any problem.

It shouldn't be a big security risk and Microsoft obviously has to gonna fix the update since the issue is pretty wide spread. So the best recommendation would be to just wait for Microsoft to fix the issue. But if you're adventurous & got a backup of your data, go for it. If you're not experienced do not mess around, messing with partitions can break your whole system.

 

[ThrashZone]

Hi,
Think the winRE partition I created with 11f help is good to go
I enabled it and it shows the correct location Recovery partition in front of C and not at the end of C
But we shall see after installing the silly ass update later hehe

I also swapped m.2's
It was really bugging me os m.2 showed as disk 2 instead of 1 or 0.

 

[cvaldes]

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

Well, they used to put in a better effort even when they were more of that de facto monopoly you talk about.

They gave up caring when they fumbled away the mobile ball and basically lost relevance to Joe Consumer's daily life. Today Joe Consumer's most important computing device is their smartphone and Microsoft just sits on the sidelines watching their mindshare evaporate.

ChatGPT is their latest (desperate?) attempt to stay in the public consciousness.

Remember that it's not just Windows Mobile (the operating system) that failed. It has been pretty much every single consumer facing technology & service (HoTMaiL, Zune, Live, whatever) over the past twenty years except for Xbox.

Microsoft doesn't try anymore because they know they are irrelevant in consumer facing technologies. They are making bank as a cloud service so pretty much all of their focus is there in Azure, etc. Azure's customers aren't consumers, Azure's customers are corporations, enterprises, and government organizations.

Servicing Windows and Office is really just legacy extended support to Microsoft in 2024. They don't want their best engineering talent working on Windows Security Updates.

 

[RJARRRPCGP]

Had the same issue. Apparently it only affects Win10 users, and for some even increasing the recovery partition to 2GB doesn't fix the issue. Well, I've tried the update today again, still failed with the "Error 0x80070643" .

0x80070643 is a common Windows Update error code on 10, but only seen that with Defender updates, followed by a Defender update that's successful afterwards. It usually happens on 10 with Defender updates, when another update is being applied.


Now, with the WinRE issue, I already suffered that issue in 2023, where updating WinRE suddenly failed out-of-the-blue. I just disabled WinRE months ago, IIRC.
This is with 11 22H2 installed on September 20, 2022. In my case, I only knew, because of a new error in the event log.

 

[chrcoluk]

Mine is 500meg and at start of disk, what idiot designed this update?

In my opinion if the update cant automatically figure things out it shouldnt be left in a failed state, but instead mark itself as installed and perhaps just provide a warning for the end user on next boot, especially the case if bitlocker isnt even being used.

Luckily I routinely leave 10% unpartitioned on my SSDs so it looks like I can probably make a new larger RE after the OS easily.

My question is for those with a bigger recovery partition, why is it bigger if the default is 500?

 

[Devastator0]

Yeah, I'm an experienced Windows/PC user and am comfortable with partition resizing but I'm no way going to manually mess around with this just to allow an update to install. As others have mentioned, I'm hanging in there until Microsoft inevitably recalls the update.

 

[R0H1T]

Do yourself a favor and make it 1-2gb's and be done.

Or just throw the PC in the bin, no more MS' spyware

Yeah, I'm an experienced Windows/PC user and am comfortable with partition resizing but I'm no way going to manually mess around with this just to allow an update to install.

I doubt anyone would wanna risk data loss, just for a single update!

 

[chrcoluk]

Yeah I had a rethink, instead I think I am going to just hide the update which should prevent being nagged unless they reissue it, I have a 10 day delay on quality updates, so hoping its pulled by then.

 

[Chomiq]

Being an unpaid member of msft QA team never felt so good ?

There's barely any QA team left because MS believed that insider can replace it.

 

[mb194dc]

Yeah I had a rethink, instead I think I am going to just hide the update which should prevent being nagged unless they reissue it, I have a 10 day delay on quality updates, so hoping its pulled by then.

Ya think, I almost never install updates on day one for this reason...

Won't be doing this one, don't use bitlocker, it needs to be pulled.

 

[Waldorf]

@Bill_Bright
depends how you define "buggy".
to me as a user, it means it doesnt work as expected...

and what would you call this then :
real bug

@R0H1T
i doubt their collection is as problematic vs what google/meta (and the like) get from ppl using their "free" social media stuff.

 

[MarsM4N]

I enabled it and it shows the correct location Recovery partition in front of C and not at the end of C

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.

There's barely any QA team left because MS believed that insider can replace it.

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.

 

[AA1138]

This step helped me install the update
KB5034441!!!
2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)

 

[Chomiq]

For me the update simply refused to install.