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-10T15:27:08+00:00

    Yes a recovery partition is automatically created by default without asking you. You need to go out of your way to prevent the Windows installer from creating a recovery partition. This has been the case for all releases of Windows 10. (And also Windows 8 and 7 if I recall correctly).

    However, the default size of the recovery partition has been gradually creeping up over the years. An early release of Windows 10 might have given you a 512MB recovery partition, whereas a later release would have defaulted to 1GB.

    Sometimes in the past, Microsoft has been known to release updates which automatically regenerate the recovery partition, often in cases where the original recovery partition size is now too small to fit the newest requirements. It's not unheard of in some Windows computers to see a succession of multiple old stale recovery partitions at the end of your drive, each one gradually eating away a little bit more of your main system partition. Only the one at the "top of the stack" is actually in use anymore.

    A more graceful solution would be to shrink the main partition by only the amount of extra space that's actually required, then grow the existing recovery partition (rather than create a whole new one), and finally install the new version of recovery in the newly freed up space; however that process would inevitably leave you temporarily in an transitional state without any working recovery at all -- and for risk mitigation purposes, I doubt Microsoft would ever take any action to make that happen automatically and unannounced.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-01-10T15:12:23+00:00

    I am having the same problem.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-01-10T14:56:01+00:00

    Hi Adamอดัม! Your partition "win re" must be at least 1G, I created my winre with 2G and that is OK too. And dont forget some job around ... like (reagentc /disable ... reagentc /enable) /Best Vlad

    Was this answer helpful?

    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Anonymous
    2024-01-10T13:54:52+00:00

    500 devices!? And MS says we should fix it!? Smh if stuff like this happens again I'm gonna start using a mac FFS.

    We have Macs that have issues with updates as well in our environment. I have one currently that refuses to install the latest MacOS update and it has to be wiped and have MacOS reinstalled to fix it. Sadly, MacOS suffers from many of the same issues as Windows. All of our Windows 10 PC's appear to be failing to install this update, Microsoft will have to pull it or fix it with a new update.

    Was this answer helpful?

    0 comments No comments