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-07-07T13:07:19+00:00

    What Instructions?

    Thank you stranger quick 10 minutes of following instructions and finally was able to update, THANKS.

    Was this answer helpful?

    0 comments No comments
  2. Neil D 34,280 Reputation points Volunteer Moderator
    2024-07-07T14:26:27+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 DiskPart A 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?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-07-08T00:06:15+00:00

    Some good advice for a person who is familiar with using all the commands and programs you mentioned. If not, it is likely they may not resolve the issues stopping completion of this Update. Most common is the Recovery Partition (with files) is just gone. The user has done some kind of SSD or HDD replacement and did not copy the partition. These users are in trouble.

    Some Advice: You should start reading this Post from about Page 40 to 47. This will give you some idea of what is needed to solve this problem. I would recommend you follow Jeff W5 comments and solution. This will be the simplest solution. If you would like to try the harder way, start reading at about Page 19, as there are some other solutions that do not involve a complete Win 10 OS replacement (saving your files and installed programs). This is NOT easy, don't try if you are not experienced. My recommendations can be found around page 38 and 39 and they worked for six Win10 PCs that did not have Recovery Files or a working Recovery Partition. This involved borrowing the Recovery Files from a working PC and placing them where the reagentc program can find them along with doing all the other necessary Partition resizing - you might want to substitute 1024 for 300 kb.

    Assuming first, you are NOT using BitLocker. If you have a PC that can be upgraded to Win 11 easily, do it. If you don't have the CPU or TPM and know how to jump to Win 11 then do it. If you want to stay on Win 10 and just fix this, take the actions on Page 40-47.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-07-08T01:21:24+00:00

    If your disk is MBR, :

    run create partition primary id=27

    run set id=27

    That should be

    create partition primary

    format quick fs=ntfs label=”WindowsRE”

    set id=27

    The original KB5028997 failed to create an MBR recovery partition. A step has been added to fix this, but it still does not make perfect sense there, and none in this rendition.

    Was this answer helpful?

    0 comments No comments
  5. Neil D 34,280 Reputation points Volunteer Moderator
    2024-07-08T08:37:39+00:00

    I was just replying to Brian798 who asked What instruction.

    It isn't my method or routine.

    Was this answer helpful?

    0 comments No comments