Microsoft Confirms it will NOT Fix KB5034441 Error 0x80070643 on Windows 10

Microsoft has officially confirmed, "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."

reagentc /info

Keep an eye out for fresh content uploaded regularly.

#windows11 #windows10 #windowsupdate #windows11updates #googlechrome #bravebrowser #microsoftedge #mozillafirefox #vivaldibrowser #powertoys #howtowindows #speedupwindows #googleapps #windows12 #chromerefresh2023 #edgeprojectphoenix #wallpapers #windowsconcepts #linux #brentech #wheretechismadesimple

[DraxxDarlok]

There you go, MS quality Control making absolutely sure that no quality accidentally escapes out of their labs.

[edison]

I wonder if they are going to intentionally screw up Windows 10 to get people to downgrade to Windows 11?

[KevinBenecke]

Microsucks won't fix it because they know the average user can't fix it manually and is hoping they will buy a new computer with the latest Windows 11 spyware and data collection.

[Cahos_Rahne_Veloza]

Thanks for the heads up.

I wish I could send Microsoft a dislike, or a huge middle finger, for giving us the middle finger themselves.

[billyguthrie]

Like i said yesterday the fact that these people can't fix an issue they caused yet they think much like google that they should be allowed to dictate industry standards is insulting the public.

[EmperorChiCheung]

It’s not “a little bit cheeky” but indeed outrageously disrespectful. I’ve been a fan of Microsoft for more than thirty years, and this event is one of the few times that the company really disappointed me. At the very least, they should pull back the update for systems having problems with it. I have two Windows 10 Pro machines and succeeded in installing the update on the one without any restore partition setup while failing on the other with a fairly large restore partition. Truly unreasonable and annoying.

[peterdobson]

Yup...I hid the update and ignored it. However, that makes a statement about Microsoft's commitment to their customers. It is not a good look.

[k.chriscaldwell]

If it ain’t broke, don’t update it. If you want it broke, permit Micro$oft to update it.

[TommyViper]

This is why I wish Linux could adapt even more to the home market that isn't exactly tech savvy, because it would force Microsoft to start listening to its users and actually caring what they have to say.

[AndyM...]

They should pull the update immediately, like they should have done back then !!!

[icdeadpipol]

this bug is a throwback to the quote "640k ought to be enough for anybody", where Microsoft grossly under-estimated the amount of disk space needed for the recovery partition.

[devaramed]

why do I have to use diskpart to just fix he mistake that i've not made

[ronnyb]

then they should remove this annoying update from their servers, the more they fiddle on their OS, the more crappy it gets
also their spying copilot AI should be removed from people who will never use the thing, i call all that crap, BLOATWARE
i just need a clean operating system to run my programs, thats ALL

[stco]

Thanks for the news. I was expecting this to disappear on one PC I have, but I now know it will be here forever. Very sloppy and poor behaviour from Microsoft.

[danmorgan]

They won't push out an automatic fix, as it would require 'shrinking' of the user's Data/OS partition, to make space for the increased size required by the recovery partition. Making arbitrary, automatic changes to the data partition 'could' in theory go wrong. Not only that, on systems with dual-boot partitions, which one would the automation choose to shrink? The potential for data corruption / loss, and the likelihood of users then wanting to sue Microsoft for said lost data, is the reason they aren't pushing out a fix for this.


It's not a difficult fix to get around this, if you are competent enough to use a command window, you can do the steps quickly. My system had the error, I shrunk my data partition by the required amount, using free partition manager software, then increased the size of the recovery partition to satisfy the update requirements. It took all of 5 minutes. Microsoft's nomenclature for the NTFS file system admittedly didn't make it 'easy', but it was doable, following the PowerShell instructions I've seen in numerous locations on the Internet.

[alixcozmo]

I'll be hopping ships soon to linux, am so glad I won't have to deal with stuff like this for much longer :)

[uzer_zero]

My "Healthy (Recover Partition)" is shown as 523 MB in size, with a 525 MB "Unallocated" section next to it that the WIndows 10 installer just decided not to use for some reason. The update still failed. So M$' statement about the required size is either needlessly vague or flat out wrong. And I don't think those two are mutually exclusive.

[garfield]

Insane. Well I guess I'm keeping this update hidden forever, honestly it's baffling to me why they rolled it out in the first place if they didn't have a contingency plan for it being an issue. Incredibly stupid blunder.

[MarcCastellsBallesta]

Thanks! Many of the computers at work are being a pain in the ass. Tomorrow I will see if it's this update.

[mikescholz]

My recovery environment is selecting linux from GRUB at boot.