• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Microsoft Did It Again! Beware Of Bugged Update KB5034441

Trudat, however, if those lessons are not heeded, then what good are they ?
More importantly what good is somebody who heeds no lessons? With that note I'm going to heed prior lessons about going off topic and will end here. I just didn't want you to think I was ignoring your question. :toast:
 
Despite no WinRE update failure in February and March on the daily-driver in the sig, I went ahead and shrunk the OS partition, deleted the WinRE partition and made a new WinRE partition.

For the OS partition, I just went ahead and did this in DiskPart:

shrink desired=1024 minimum=1024

----------------------------------------------

The shrink command is in megabytes.
 
Looking at my installations

Seems 530MB is too small, but 546MB is big enough.

These were the sizes the Windows 10 installations made, depending on if it was a recent build or old.
 
I'm not fixing it on any of my machines manually. If Microsoft can't be asked to figure out something, then neither should I.
Exactly, had the same problem on couple win 10 machines here but ignored it for months already...
However, was planning at some point to upgrade them to 11, when I did that the problem went away of course. Just upgraded from within 10 & not a fresh install of 11. All's working well now. :)
 
It is now May 3, 2024, and one of my machines with Windows 10 is showing a failed download of the "update" this thread is about.

So, nearly FOUR (4) months after the OP started this thread, this "issue" is still not solved. Really, Microsoft? Oh, wait, it's Microsoft we are dealing with.

I am not going to "meddle" with resizing and enlarging partitions. If THEY release an update for something in THEIR crap OS, and that fails, then THEY can keep their "update" (just like they can keep their crap OS too, after 2025).

I am SICK and TIRED of the ENDLESS "issues" I am facing with Windows 10 (Windows 11 is even worse). At work, I am no longer the "local power user" (LPU) because I was, am FED UP with this Windows 10/11 crap.

I have been using Linux since 2007, from Ubuntu to Mint/LMDE to Fedora, OpenSUSE... whatever, MX Linux, Bunsenlabs, and Linux is in all ways (except, perhaps, gaming?) FAR superior than Windows. I have gotten to "hate" Microsoft Windows (10/11/ 12?). It is the MOST unreliable thing I have EVER worked with in my entire life.

Linus Torvalds should get a statue on every continent, including Antarctica, for having given us GNU/Linux. (Alright, alright, you can have a small statue too, Richard.)
 
I've read somewhere that microsoft released a statement that they won't fix this bug.

KB5034441 known issue , status changed to Resolved

Resolution: Automatic resolution of this issue won't be available in a future Windows update. Manual steps are necessary to complete the installation of this update on devices which are experiencing this error.

So it is up to the user to do a manual fix If they want. Personally I would just disable and delete the winRE partition because I am not affected (BitLocker encryption bypass issue).


How was I under the impression that MS was starting to care for their users again ? :confused:
 
Last edited:
I also saw a news bit somewhere the other day that said that M$ has no intention of fixing this issue, so just have to do it myself...go figure !
 
Kinda typical MS, like introducing 2 KB updates with the same names where you had to have one before the other which also lead to problems.

This should be fairly simple for MS, create a update that does this, then requires a reboot before you can install this update, and make a requirement that this update looks for the previous update and size of the partition.

Should be a done but I guess since outsourcing MS don't bother anymore just like Apple with osx updates that doesn't check for required disc space is actually free :roll:
 
I also saw a news bit somewhere the other day that said that M$ has no intention of fixing this issue, so just have to do it myself...go figure !
Luckily it's not too difficult to fix manually (at least for the pc savvy). I can see some going bonkers over the idea of some newly unused space near the start of their drive after the partition is relocated to the end like a gnat buzzing around just waiting to fly up someone's nose for no apparent reason. If one has an SSD I suppose one could spin that as overprovisioning or some some free space for SLC cache now. :laugh:
 
If one updates Windows 10 to 11 the partition gets extended, so it certainly can be done automatically.
 
If one updates Windows 10 to 11 the partition gets extended, so it certainly can be done automatically.

If that's true, then why doesn't ms make an update to auto extend that partition.....
 
Microsoft has acknowledged that it has given up trying to fix borked KB5034441:


More commentary here:


Lame. But that's Windows in 2024...

Happy weekend everyone!

:):p:D
 
Last edited:
If Microsoft can't be bothered to fix it, then I won't, either. I guess it's not important anyway.
 
If Microsoft can't be bothered to fix it, then I won't, either. I guess it's not important anyway.
That's right! Who needs a pesky recovery volume anyhow?!? They're just a waste of valuable disk space!

:clap::peace::lovetpu:
 
I just reinstalled Windows 10 as recent versions format the right partition size. (546MB rather than 530MB)
 
Last edited:
I just reinstalled Windows 10 as recent versions format the right parition size. (546MB rather than 530MB)
As stated in an earlier linked article:


the actual size of the recovery partition isn't the issue. Microsoft stated that the recovery partition needs 250MB of free space for a successful update. It's how much is available in the existing recovery partition, not the size of the whole partition.

And as Mayank Parmar stated in his recent post (read the Windows Latest article reference in post #187), KB5034441 failed on his computer that doesn't even have a recovery partition.
 
Back
Top