Update KB5034441 fails to install

I repeat it was not lazy and worked on W11, but as a W10 user I don’t care how careful and wonderful it worked on W11, they just ported lazily from to w10, knowing it was not going to work.

This guy is no a “hater”, and self proclaimed techie Windows “enthusiast”, always pushing people to patch for security, still this is one of the few occasions he rants:

And this is one of his lasts, he comments they could script it to show the error once or not offer the update if you don’t have a WinRE partition, if you don’t use BitLocker, or if you are in Home Ed. But nooooo, they lazily pushed universally for everyone even when most don’t need, making  a lot of people worry and pulling the hairs when they see they should “contact support”, not everyone comes here and for what you see here not even people in the chat or support is helpful, because is an unnecessary problem created by W update people, call it lazy or not but is  screw up.

I said the patch is lazy, not that the engineers are lazy, perhaps on contrary they are over worked and unmotivated people, as shown in some reports from MS; but still there seems to be a poor leadership and management there.

But the argument really doesn't hold as only the same small percentage of Windows 11 will have the Pro edition so it is the same percentage of the tiny population with Windows 11 that will be affected by this security vulnerability as well. EVERYBODY on Windows 11 Home were offered their version of this security patch.

So it comes down to my interpretation of the event. Microsoft decided to do a "phase" launch which created the problem. It is the "SAME" port. There is no different port. If Microsoft decided to do a blind dive without a phase launch, then it wouldn't have this problem.

Microsoft told people in the release notes that you don't have to worry about it if you don't have a winre partition. Only the busybodys on tech forums insist that they have to block the update. Even if you have a winre partition, wait for a permanent fix, you don't have to do all the blocking stuff.

Also end-users can upgrade to the Pro edition at any time, which would create a security hole for them if the patch is not offered to everyone.

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.

I repeat it was not lazy and worked on W11, but as a W10 user I don’t care how careful and wonderful it worked on W11, they just ported lazily from to w10, knowing it was not going to work.

This guy is no a “hater”, and self proclaimed techie Windows “enthusiast”, always pushing people to patch for security, still this is one of the few occasions he rants:

And this is one of his lasts, he comments they could script it to show the error once or not offer the update if you don’t have a WinRE partition, if you don’t use BitLocker, or if you are in Home Ed. But nooooo, they lazily pushed universally for everyone even when most don’t need, making  a lot of people worry and pulling the hairs when they see they should “contact support”, not everyone comes here and for what you see here not even people in the chat or support is helpful, because is an unnecessary problem created by W update people, call it lazy or not but is  screw up.

I said the patch is lazy, not that the engineers are lazy, perhaps on contrary they are over worked and unmotivated people, as shown in some reports from MS; but still there seems to be a poor leadership and management there.

But the argument really doesn't hold as only the same small percentage of Windows 11 will have the Pro edition so it is the same percentage of the tiny population with Windows 11 that will be affected by this security vulnerability as well. EVERYBODY on Windows 11 Home were offered their version of this security patch.

So it comes down to my interpretation of the event. Microsoft decided to do a "phase" launch which created the problem. It is the "SAME" port. There is no different port. If Microsoft decided to do a blind dive without a phase launch, then it wouldn't have this problem.

Microsoft told people in the release notes that you don't have to worry about it if you don't have a winre partition. Only the busybodys on tech forums insist that they have to block the update. Even if you have a winre partition, wait for a permanent fix, you don't have to do all the blocking stuff.

Also end-users can upgrade to the Pro edition at any time, which would create a security hole for them if the patch is not offered to everyone.

What do we do if it won't even download? Everyone seems to be concentrating on the Installation Failure due to partition size, but this update won't even download in Windows Update, so it can't even try to install. All other Windows updates for .NET etc. have downloaded and installed the same day this appeared, so it would not seem to be a connection error.