Windows 10 22h2 security update [KB5034441] fails to install with code: 0x80070643

Anonymous
2024-01-09T19:42:37+00:00

* * Mod note on 1/12/24. * *

Please see: https://www.yourwindowsguide.com/2024/01/fix-error-0x80070643-for-windows-10-kb5034441-update.html 


The latest update downloads and then fails to install.

  • OS Build # 19045.3930.
  • Update Troubleshoot tool repair but it does not help.
  • MS Windows Update Catalog does not have the update.
  • Other updates all went through without any trouble.

This is a brand new update. Is this a known issue? Is there a resolution specific to this update? (Please do not copy and paste standard procedure)

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.

0 comments No comments

194 answers

Sort by: Most helpful
  1. Anonymous
    2024-01-12T00:06:01+00:00

    I found this today:

    https://www.bleepingcomputer.com/news/microsoft/microsoft-shares-script-to-update-windows-10-winre-with-bitlocker-fixes/amp/

    Not quite a reworking of the fix and I honestly don't believe Microsoft can/will fix the update. By design, the recovery partition was intended to fluctuate in size.

    But as someone else posted before, earlier versions of Windows 10 park the recovery partition at the "top" of the drive while later versions park it at the "end" which makes resizing easier (if still largely manual).

    Unfortunately, I don't know if the above "solution" will address these older systems (like the ones I have). I'm reluctant to mess with the current partition order as something is likely to go wrong and the computers won't boot anymore.

    I also don't know if this would address situations where there are *multiple* recovery partitions, as I have in one case.

    Caveat emptor...

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-01-11T23:47:53+00:00

    Oh boy did you hit that nail on the head! XP came out and worked great, Vista didn't works at all until they released the first service pack a year later. Then 7 was released, what a wonderful breath of fresh air! It didn't just work, it was great!
    Haha, to get back in the groove they released 8, surely as non-functional as Vista, worse the stupid full screen start menu., 8.1 was no big relief from 8, I suppose it worked but I never used it.

    Oh, almost forgot.....
    To Force 8 on us they broke win 7's update function. Suddenly you couldn't do a clean 7 install and have it update!

    "What do you want that for? Install 8!"

    Then 10 was released, Better than 7, and it worked great!

    Can't let us get used to something that we like, watch out, here's 11.....they had to hide most system functions and f+*k with the start menu again. WTFF !
    I suspect that everytime there's a new windows department manager they want to lay their "wonderful change" on the world, so when the compliments come in they can say "That was my idea" I think they should have to face a committee of real users before changing the UI

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-01-11T23:03:48+00:00

    My WDC SSD is a PCIe NVMe 4.0 drive that is almost brand new. I have used Reflect for years but don't see an option to resize a partition during a restore.

    I'm just going to wait until MS fixes the update.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-01-11T23:03:13+00:00

    yeah, all that didn't work... but it made me feel like I was making it happen... like I might have a chance... until the final push of the button... by-your-leave thanks for the dance

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-01-11T22:36:14+00:00

    Thanks so much for sharing this info. Based on what I've read the entire security update is focused on patching a security flaw in Bitlocker. Since I don't use Bitlocker, I don't think its worth the trouble (and the risk) of increasing the WRE partition size. So, I'm just going to ignore the update error (not the first time) and wait for Microsoft to push out an update that actually works on all machines. Especially since they are the ones that created the issue with the partition size.

    Was this answer helpful?

    0 comments No comments