Windows update (KB5034441) Error (0x80070643)

Anonymous
2024-01-23T05:38:57+00:00

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.

0 comments No comments

513 answers

Sort by: Most helpful
  1. Anonymous
    2024-02-29T23:18:12+00:00

    **Summary**

    Microsoft has changed how it updates PCs that run the Windows Recovery Environment (WinRE). WinRE will be updated using the monthly cumulative update. This change only applies to PCs that get updates from Windows Update (WU) and Windows Server Update Services (WSUS). This change starts on June 27, 2023, for the Windows 11, version 22H2 cumulative update.  

    Some PCs might not have a recovery partition that is large enough to complete this update. Because of this, the update for WinRE might fail. You will receive the error message, "Windows Recovery Environment servicing failed.” To help you recover from this failure, this article provides instructions to manually resize your recovery partition if you get a system ErrorPhase of 2. This requires your device to have the recovery partition after the OS partition. Use the steps below to verify this.    

    Manually resize your partition by 250 MB

    1. Open a Command Prompt window (cmd) as admin.
    2. To check the WinRE status, run reagentc /info. If the WinRE is installed, there should be a “Windows RE location” with a path to the WinRE directory. An example is, “Windows RE location: [file://%3f/GLOBALROOT/device/harddisk0/partition4/Recovery/WindowsRE]\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE.” Here, the number after “harddisk” and “partition” is the index of the disk and partition WinRE is on.
    3. To disable the WinRE, run reagentc /disable
    4. Shrink the OS partition and prepare the disk for a new recovery partition.
    5. To shrink the OS, run diskpart
    6. Run list disk
    7. To select the OS disk, run sel disk<OS disk index>  This should be the same disk index as WinRE.
    8. To check the partition under the OS disk and find the OS partition, run list part
    9. To select the OS partition, run sel part*<OS partition index>*
    10. Run shrink desired=250 minimum=250
    11. To select the WinRE partition, run sel part*<WinRE partition index>*
    12. To delete the WinRE partition, run delete partition override
    13. Create a new recovery partition.
    14. First, check if the disk partition style is a GUID Partition Table (GPT) or a Master Boot Record (MBR).  To do that, run list disk. Check if there is an asterisk character (\) in the “Gpt” column.  If there is an asterisk character (\), then the drive is GPT. Otherwise, the drive is MBR.
    15. If your disk is GPT, run create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac followed by the command gpt attributes =0x8000000000000001
    16. If your disk is MBR, run create partition primary id=27
    17. To format the partition, run format quick fs=ntfs label=”Windows RE tools”
    18. To confirm that the WinRE partition is created, run list vol
    19. To exit from diskpart, run exit
    20. To re-enable WinRE, run reagentc /enable
    21. To confirm where WinRE is installed, run reagentc /info

    **Note** If creation failed or you do not want to extend the WinRE partition, run reagentc /enable to re-enable WinRE.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-02-29T14:06:00+00:00

    Yes, the "patch" that Microsoft is releasing is called "End Of Life", as in retiring Win10 in Oct 2025. This update\fiasco only updates BitLocker, you can skip this fiasco without consequences.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-02-29T14:02:21+00:00

    It only updates BitLocker. If you don't use BitLocker, skip this "update"\fiasco. Beside, Win10 reaches end of life Oct/2025.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-02-29T14:01:20+00:00

    Correct, because it only affects BitLocker. Who the heck uses that at home?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-02-29T06:40:37+00:00

    hello community , i read and read all your comments, iam not tech enough to mess around the frecommrendation by shringking partition etc, my only qurestion is

    will Microsoft realease a new patch to fix this issue surely they are aware that something is wrong somewhere

    any ideas, any people from Microsoft in this forum can shed a light on it??

    thanks

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments