Update KB5034441 fails to install

LoL, I can't believe you still haven't solved this problem...

I've also extended the size of the EFI partition to 1 GB manually, and even that hasn't resolved the issue... (every other update works though)

Are you killing off Windows 10 on purpose, or what?!

C'mon, it's literally have been two exact months since then!!!

Since the beginning you keep referring about W11, that is irrelevant.

I don’t care if they did a wonderful and dedicated work in this patch as the Manhattan or Apollo project on W11, as a W10 user if they ported it lazily from there (because the partition systems is very different), knowing it will not work,  is a screw up:

1. Assuming is true what you say W update can detect when you upgrade to PRO that you don’t have and need the patch and install it.
2. Upgrading to PRO doesn’t mean you’ll use BitLocker, actually I have PRO, but I don’t have a WinRE partition nor I use BitLocker, is double irrelevant for me. Is not that a hacker in a banana country is going to take on your device online, it requires physical access to your PC. So I only can imagine some corps, big or tiny, using BitLocker, and distrust of their own employs accessing their devices may be worry for this. Totally irrelevant for Average Joe.
3. Ok let’s give you right for a second, the patch is super important to have it in everyone, then with a more reason a major screw up if it doesn’t works if 1) average users has to do experiments their drives partition until it works 2) or as it is happening now, most people ended up hiding this "super important" update

So in anyway, as you want to see it, it’s a mayor screw up, stop defending their incompetence and bad decisions, is not the first one, they just did it this month again.

Again, if you don't have winre partition and microsoft is telling you that if you don't have winre partition, you can ignore the messages --- why are you arguing about it. It doesn't affect you.

I am not excusing them of anything. I am just saying that they patched this thing over Christmas and after the fiasco in January patch Tuesday, they were having a bunch of zero days vulnerabilities to patch. This "error" message doesn't hurt anyone except people with OCD who can't stand to see the error message or people with cascading update failures (not KB5001716 failures that hiccup was fixed today).

I rather they fixed the zero days vulnerabilities first then this irrelevant error message. It is the lowest of low priorities. If you have a HOME edition and you see the error message, just ignore it. It will eventually get fixed.

It’s not only about me, i told 100 times almost no uses BitLocker on W10, (on W11 may be more common and more logic to push it on everyone); but most people don't know it and some are wrongly scared if not installed, thinking they may have a vulnerability and tomorrow some hacker online may take over your system.

Not everyone even read these forums, you may have read here some tried MS “wise easy fix” ended bricking their systems, losing partitions and valuable data.

And if you try to ignore it tries to install again and again background causing conflicts and taking resources of your system, especially if your PC is old, as may be common in some W10 users.

The best solution so far is using the tool to ignore it, but we must not be using tools to hide patches an updates because these people screwed up.

Just a couple of notes to everyone on thread. Going to start with the error message we got from KB5034441. I was still getting the definitive updates and of course the error from KB5034441. Though worried maybe something else would fail to show. I finally after 2-3 weeks time hid it. Then of course just recently we had the error on KB5001716. Which I spent the whole first day trying to fix it using DISM and sfc scannow among others. None of them worked (forget the troubleshooter that fails to notice it is even bad), Though there is a difference between the two. The first one never updated nor fixed. The one just some days ago had already updated in Oct and also on March 5th. Then tried to update again. Then just hid it and it fixed it and left the ones that had already updated alone. No more errors for now. So for MS still having a black eye for KB5034441 and not really knowing if it has been fixed behind the scenes or a not needed update. The fixes for the KB5034441 as called out by MS and those on YT work for some and not others. Not me because I am not about to cause more problems by partitioning something that MS needs to repair, or resend a good copy for all. For those who wish to fix this last one just hide it. It also states it is fixed by the program. You are only removing the error upload.

One difference is that for KB5034441 if you still get the error it means it is not installed, as you said hiding it doesn’t solve it, but you should worry only if you use BitLocker and you are afraid someone with physical access to your Pc may hack it, if not don’t worry this update is irrelevant. So hiding it is the best solution for most people.

Here the thing is the WinRE partition, it doesn’t have the right size to be installed, and messing with your partitions is not a good idea unless you perfectly know what are you doing.

Fo KB5001716 is different and other unrelated thing,  it doesn’t detect you already have it installed, so it tries to reinstall but since you have it, it gives an error. For some the solution is to search it, then uninstall the update, it will install successfully. But that solution doesn’t work for everybody, for some the thing tries to reinstall again later.

It is a problem because it tries to reinstall all time taking resources on your PC, but apart from that KB5001716 (at difference of KB5034441) it is already installed so you are hiding an update you already have.

Again KB5001716 other unnecessary update from W update engineers, it is said the only thing it does, (if your PC fulfill the requises) is push one of those sneaky intrusive full screen pop ups, to force people to install W11 with a tiny almost hidden option to say "no", and that’s it.

They are working hard on that instead of fixing KB5034441 and now they have 2 flopped updates

Just a couple of notes to everyone on thread. Going to start with the error message we got from KB5034441. I was still getting the definitive updates and of course the error from KB5034441. Though worried maybe something else would fail to show. I finally after 2-3 weeks time hid it. Then of course just recently we had the error on KB5001716. Which I spent the whole first day trying to fix it using DISM and sfc scannow among others. None of them worked (forget the troubleshooter that fails to notice it is even bad), Though there is a difference between the two. The first one never updated nor fixed. The one just some days ago had already updated in Oct and also on March 5th. Then tried to update again. Then just hid it and it fixed it and left the ones that had already updated alone. No more errors for now. So for MS still having a black eye for KB5034441 and not really knowing if it has been fixed behind the scenes or a not needed update. The fixes for the KB5034441 as called out by MS and those on YT work for some and not others. Not me because I am not about to cause more problems by partitioning something that MS needs to repair, or resend a good copy for all. For those who wish to fix this last one just hide it. It also states it is fixed by the program. You are only removing the error upload.