Windows update (KB5034441) Error (0x80070643)

Same here, unfortunately. I've read that the best course is to pause updates until a solution comes out.

By experimentation, I found a resolution for the formatting error for the newly created recovery partition myself. If I booted from the MBR disk containing the recovery partition then the quick format would fail with "the parameter is incorrect". However, if I booted Windows from another disk (I have dual boot disks for resilience) then the formatting of the recovery partition worked fine. After formatting the partition I did need to set id=27 again to mark it as a recovery partition.

Having successfully increased the size of the recovery partition from 460Mb to 710Mb I optimistically retried the installation of KB5034441. To my dismay it failed in exactly the same way as previously.

What is clear to me is that Microsoft's suggested workaround for the KB5034441 problem is not a guaranteed solution. Of course, it is highly undesirable for end users to have to resort to such manual partitioning in the first place. Still waiting for a proper fix for this issue.

Micro$oft is playing a dangerous game. How many of the gazillion Windows computer users are willing and able to successfully use their crackbrained workaround? Personally, I have no interest in goofing around with my partitions to solve a problem that shouldn't need fixing. My computers do just fine without this goofball update.

M$ needs to get rid of this update unless and until it works properly. They want absolute control of our computers. Now they want control of our time and effort too?

I have no idea. I restored my entire hard drive (including the restore and boot partition) from two days before I had this issue. I disabled automatic updates. Everything is working fine for now. I put my automatic update on pause. In theory they said they are working on this. I don't know. Originally I had this error and they said to keep trying every couple of days. I am not doing to do that now. The pause is set to expire on 2/9/2024 so I hope they fix it before then. I am still hoping the updates do not break my computer again.

I am replying to this post because I see no way to post my own original ... i.e., my own original grief and ANGER at MS for this. I worked in IT since early 1970s (mainframes thru mins thru micros, etc.). I am retired and just want the darn things to work. I stuck with MS even though Apple users argued how easy their systems were and that they "just worked." I am retired and "just want my desktop Windows 10 and laptop Win 10 to work!" My PCs are old and will not load Win 11, but so what! Win 10 and my hardware work for my uses (no gaming, video editing, etc.)). Is this actually the beginning of MS efforts to FORCE us to move to Win 11 ... and for the benefit of the manufacturers to get us to update our systems since Win 11 will not run on our "antique" systems. If so, the hell with MS and PCs. I'll look at Apple systems ... or Lynix ... or Chromebooks or something! My wife got a new iPad and we have Apple phones ... they just work. Not an Apple advertisement at all. I like using Windows and MS apps, but this has left me frustrated over many attempts and ANGRY. I realize developer teams move on to the next and greatest, leaving the grunt work to maintenance teams ... but this is ridiculous.