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-10T01:31:58+00:00

    I just started running into this, and there's this blurb in the description of the update:

    IMPORTANT

    Some computers might not have a recovery partition that is large enough to complete this update. Because of this, the update for WinRE might fail. In this case, you will receive the following error message:

    • Windows Recovery Environment servicing failed.
      (CBS_E_INSUFFICIENT_DISK_SPACE)

    To help you recover from this failure, please follow Instructions to manually resize your partition to install the WinRE update.

    Known issue Because of an issue in the error code handling routine, you might receive the following error message instead of the expected error message when there is insufficient disk space:

    • 0x80070643 - ERROR_INSTALL_FAILURE

    Source: https://support.microsoft.com/en-us/topic/kb5034441-windows-recovery-environment-update-for-windows-10-version-21h2-and-22h2-january-9-2024-62c04204-aaa5-4fee-a02a-2fdea17075a8

    I tried the process of resizing the recovery partition and ran into an interesting error when I tried to re-enable it. Windows reported it can't enable it while Bitlocker is enabled.

    So I'm wondering if this patch to fix a Bitlocker-related vulnerability requires Bitlocker to be disabled and the device decrypted before it will work.

    Thoughts?

    Was this answer helpful?

    200+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-01-10T02:11:34+00:00

    Followed the above steps except for in-place upgrade (since my PC does not have hardware to run windows 11). Problem persists.

    Was this answer helpful?

    100+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-01-10T05:33:29+00:00

    Although I know this is going to work, there is no way I will be doing that to all the computers I support or advise inexperienced users to do that. That would involves hours of work remotely accessing these boxes.

    Could anything go wrong???? (we all know that answer)!

    1. This shouldn't have happened in the first place (plenty of comments re that).
    2. MS should aroung a proper fix quickly & apologise for the stuff-up.

    Was this answer helpful?

    100+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-01-10T05:58:54+00:00

    Most excellent quality control, Microsoft.

    I did not buy Windows for the privilege of being your unpaid Beta tester. :-(

    Was this answer helpful?

    100+ people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-01-10T10:39:40+00:00

    For a tech company whose annual worldwide revenue hit 211.92 billion USD according to Statista and the company's own annual report for the 2023 fiscal year, I find it baffling that this security update made it past quality assurance before live deployment. Not only does this issue just stick out and build unnecessary logs in eventvwr.msc every time it fails, it resolves a critical vulnerability for people who use BitLocker on their machines, and they cannot even install it.

    Here is the support article for the broken KB5034441 update:

    "KB5034441: Windows Recovery Environment update for Windows 10, version 21H2 and 22H2: January 9, 2024"

    If you read through this article and follow the instructions page link it provides, you will find that the solution is to resize the recovery partition on your machine. And that involves shrinking your boot C:\ volume, deleting your recovery partition, and reinstating a new one with more byte space. Like your everyday, casual Windows user is going to understand what all of that means and is going to risk breaking their operating system running a list of shell commands they do not understand.

    As someone with very little experience with disk management and PowerShell, I was hesitant following the partition resize instructions out of concern I might break or accidentally remove a partition my system needs to run correctly. But I took the time to research what the commands outlined in the instructions did, and how disk management worked, so that I can comfortably resolve the issue knowing what was happening.

    Not every Windows user is going to do that. So you end up forcing thousands who use your OS to encounter this issue and wait for some fix that might come Soon™, for an update you rushed out knowing it had some problem with a solution your software engineers are paid to fix. It is not the community's job to fix problems you are aware of. That is frustrating.

    Was this answer helpful?

    100+ people found this answer helpful.
    0 comments No comments