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: Oldest
  1. Anonymous
    2024-06-23T16:57:20+00:00

    Yes, in my opinion, they (Microsoft) are NOT going to offer some Automatic Update or one-touch easy fix. This one you are going to have to fix it yourself, or just ignore the update as it really has no effect on operation for 98% of PC's.

    If you read the pages of this post, you will find there are several Essential Steps needed to correct the issue. Two of those are Resizing your Recovery Partition and manually pointing (directing) Microsoft Windows 10 to the correct Recovery area (on your Boot Drive C: inside the Windows Program first, or moved to a sized Recovery Partition. Sometimes you need to find (get) the essential files that are part of the Recovery. Without these files the Update will NEVER complete.

    Some of the directions located from Page 38 to 44 also give a solution that is a complete replacement of Windows 10 Operating System by downloading the proper Windows 10 OS on a Thumb Drive and installing Windows 10 again (saving your programs and data without loss). This is the method I would recommend, especially if you are not familiar with Recovery Partitions, reagentc, and Command Com working. Making Windows find the needed Recovery Files is tricky.

    Read the pages from this post, you might need some help in completing the steps needed, but some are easy.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-06-23T18:58:57+00:00

    This one you are going to have to fix it yourself, or just ignore the update as it really has no effect on operation for 98% of PC's.

    Unless, of course, they are trying to upgrade to Windows 11.

    One should not need to take on the role of an IT professional to resolve this.

    Disappointing.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-06-27T05:53:48+00:00

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-06-27T11:28:06+00:00

    Fixing the KB5034441 Update Error

    I wish to share my experience of fixing this error from all the resources I found

    As you can see we have an error updating KB5034441. I have Found a solution and glad to explain.

    We have a health Recovery partition , it's just not big enough.


    Opened A Command Prompt with Administrative Privileges.

    type cmd in the search bar and right click Command Prompt and select Run as Administrator.

    This next command is the most important for without it one must go through much added procedures to get a successful ReAgentC/Enable run.

    * Run ReAgentC  /Disable   This is done to move the REimage to system directory for later use

    Run    DiskPartA program for performing tasks on the hardrive

    Run   list disk   Please take note of the type of disk you have .ie. An asterisk under * GPT

    Run   Sel Disk 0         The Main Disk or the one with the Windows OS on it C:\ most likely       

    Run     Sel Part 3         The Primary Partition. we're going to shrink this to add to part 4

    Run   shrink desired=300 minimum=300   this will give us plenty after we make a new partition

    now Select the Recovery partition

    Run     sel par 4   This is the Recovery Partition we’re going to delete then create new

    Run  detail par   Let’s get details about the Recovery partition for comparison later if needed.  

    you should see an asterisk next to the recovery partition as it is the one selected.

    Run   delete Part Override

    now, we're going to create our new larger partition.

    For GPT Disks :

    Run   create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac

    **** Run   gpt attributes =0x8000000000000001

    Run   format quick fs=ntfs label=”WindowsRE”

    If your disk is MBR, :

    run create partition primary id=27

    run  set id=27

    Run   List par Let's see how big the partition has become

    Your Recovery partition size may very. it should be > 800

    run Exit to exit out of Diskpart. and return to the Command Prompt.

    Run     ReAgentC  /Enable to enable the Recovery partition

    this is when the REimage is now going to be place back on the recovery partition

    If enabling was successful, and it should be, exit out and close all windows and check for updates and it should work as it did for me.

    If you receive an error that the REimage was not found then please comment and I have solution for that as well. I will post.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-06-27T12:21:26+00:00

    I've posted this earlier but you do not have to mess with resizing partitions to fix this error. Just follow the tutorial below.

    How to Do a Repair Install of Windows 10 with an In-place Upgrade

    The above worked for me last month - no more pesky update error message, after many months. Check the box for Download updates, drivers and optional features (recommended) box when it gets to that point. Otherwise, follow the tutorial step-by-step.

    Was this answer helpful?

    0 comments No comments