So - out of curiosity - *why isn't Microsoft fixing this?*I assume most users cannot successfully navigate through this process.
Windows update (KB5034441) Error (0x80070643)
When I tried to install the windows update "2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" I received the error code (0x80070643).
I have already tried, restarting my computer, waiting a bit before retrying, running a memory diagnostic check, checking all my drivers for updates, installing optional updates, and running a malware scan.
When I tried to run the windows update troubleshooter it said "diagnosing problems" but never fixed them and I was still unable to install the update after running the trouble shooter.
Any help would be appreciated.
Windows for home | Windows 10 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
513 answers
Sort by: Most helpful
-
Anonymous
2024-07-08T12:26:44+00:00 -
Anonymous
2024-04-12T18:10:29+00:00 hi all
Does any one know wheb Microsoft will release a fix patch for this update
I am noy tech dsavy enough to play with partition and i think it up to Microsoft do release its own fix
anyone from mMicrosoft on this forum?
Please can Microsoft hed some light on that one?
-
Anonymous
2024-02-20T23:56:04+00:00 Microsoft has too many updates it's absolutely absurd - I do legal writing and have numerous files open and then there is a limit on how many you can pause - I hate MS with all my heart and soul - someone suggested going to Apple that their system doesn't have these problems As long as they have
a word processing program that converts to .pdf but I have enormous amounts of data in what is probably a MS file system so I'm ****. They ought to just ransom the thing when they want you to buy 11 12 or whatever they ought to just charge you the price to keep what you have so much for the genius Liberals in their make work pseudo capitalist retail economy hillbilly **** yeah I'm greatly pleased
-
Anonymous
2024-02-11T22:14:07+00:00 Previously I posted a rather upset (angry) reply that MS could allow such to happen, with references to development teams vs maintenance teams. I forgot to mention the teams that are probably more important than both of those ... the testing teams, I have been involved in setting up test suites for new software development (years ago). I have also been a manager of QA. If MS says (as the HAVE stated) that they intend to continue support of Win 10 with updates for a couple years at least, they should darn well be testing these updates BEFORE releasing them to the general audience ... not just alpha and beta testers. MS should have a lab of various of these older systems (PCs) on which to try these "patches" before ramming them out to the general user community. Come on, MS, get your act together if you were not just blowing smoke about supporting our "vintage" systems! BTW, someone mentioned that MS did not read this list. I only found it by searching on the error message. I would hope that SOMEHOW MS people take notice of how frustrated its customers are ... and that they recognize that we do have options other than them
-
Anonymous
2024-02-05T17:48:07+00:00 The problem is that the suggested Microsoft workaround (involving a manual extension of the recovery partition using diskpart) may or may not work.
I have a PC with dual Window 10 boot SSD's - I can boot Windows 10 from either SSD. One SSD has a recovery partition of 840Mb and KB5034441 installed OK, without the need for me to do a manual extension of the recovery partition. On the other SSD the recovery partition was only 460Mb and KB5034441 failed with the dreaded 0x80070643 error. I extended the recovery partition by 250Mb to 710Mb, using the Microsoft instructions. 0x80070643 still occurred. I tried extending the recovery partition again, this time to 960Mb. Same 0x80070643 error.
I don't think that the recovery partition size is the only reason for KB5034441 installation failure - there must be some other potential cause, which is not addressed by the suggested Microsoft workaround.