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-04-14T17:23:23+00:00

    This solution with temporary relocation of WinRE to system partition does not work for me. It also does not locate recovery partition automatically after I removed and re-created it - I get the RE image was not found. I don't find winre.wim in %windir%\system32\recovery, it is in C:$ReAgent\Scratch under the name update.wim. I need to manually copy it to the recovery partition location recovery\windowsre and then do reagentc /setreimage path to there so that I could successfully enable RE environment.

    But it does not help with this 0x80070643 error. Every time I attempt the update it moves winre.wim from %windir%\system32\recovery to C:$ReAgent\Scratch\update.wim.

    My system is HP laptop survived upgrade from Windows 8.1. Initial recovery partition on it was located at the very beginning on the disk. I was unable to expand it as diskpart can shrink only to left so I just removed it and created a new recovery partition sized 996MB after the main boot partition.

    Any suggestions are appreciated.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-04-14T14:35:40+00:00

    I have wondered why it is beneficial to have this recovery on a different partition but on the same drive as your Windows Operating System drive. Chances are if you have a disk problem it will take out the whole drive, so it is of no benefit as you will not be able to use it.

    I followed the same direction (path) you did, once I was able to get the update to complete. It is easy to move the recovery from your Windows OS partition over to your newly created Recovery Partition (larger sized) using reagentc disable and reagentc enable. It does the recover moving automatically without the use of using setreimage. I could not get the path part of setreimage to work.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-04-11T13:36:07+00:00

    This has to work.

    ...and it ultimately did, thank you!

    I needed to do a couple of other things to get there, so just going to fill in a few blanks in case it helps.

    No 3rd party software just working with Windows 10:

    1. Run Command Prompt as Administrator
    2. Disable Windows RE.

    type/paste:   reagentc /disable

    1. Optional: If you need a bit of a guide and further reassurance before jumping to the next command, you can use Disk Management to verify what/where your Recovery Partition is and leave it up. Search "Disk Management" (create and format hard disk partitions found in the control panel)

    *You can't delete the partition by using Disk Management. So...

    1. Return to Command Prompt (as Admin) type: DISKPART
    2. Type: list disk
    3. Using Disk Management as a guide, compare it to the list in your command prompt and confirm your Disk number (most likely Disk 0)
    4. Type: select disk 0 (or pertaining disk with the partition on it)
    5. Type: list part
    6. Identify the Recovery partition number (most likely Partition 4)
    7. Type; select part 4 (or pertaining recovery partition)
    8. Type: delete part override

    Now it's deleted and you need to re-enable Windows RE.

    1. Open a fresh Command Prompt (Admin) or return to default command line and type: reagentc /enable
    2. Try the update, worked for me.

    Thank you Volume Z

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-04-07T15:08:34+00:00

    To recap -

    1. I'm working with the assumption that the issue is that the RE partition is too small - according to MS.
    2. I'm able to do the diskpart/cmd but I wanted to see if people who are uncomfortable with doing them (i.e., they don't have a full system to bare metal backup process in place) could do something easier.
    3. I used a partition tool (and several free ones are listed in this thread) that can shrink the main C partition so you can expand the WIN_RE partition. I increased mine using this method.
    4. When it still had errors, and after increasing it again with no effect, I opened a "Run as Administrator" Command Prompt and entered reagentc.exe/enable - rebooted and it worked.

    IMHO the issue is MS either isn't interested in giving the general users a command prompt file that auto-resizes the C and WIN_RE partitions.

    NOR are they interested in giving everyone the straightforward process that worked for me which would mean they would have to recommend a partition management tool.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-04-06T19:33:26+00:00

    Might want to try a CLEAN Win 10 install with a thumb drive created ESD made from Windows Recovery. You will loose all your programs and data so back up your Personal Info first. Good luck. Windows will erase your hard drive, format it, and re-partition it also. Might want to make sure you do not have any SSD optimization going on like Overprovisioning or Momentum Cache. I try to leave at least 20 GB of the OS Drive Unallocated. This allows for increasing partition size if needed. FYI: This update is really not worth the effort. It has no effect on performance, and does nothing for a non-bitlocked drive. Might want to just ignore it or bypass it like so many others have done. Perhaps one day Microsoft will fix it, but given the complexity and reduced interest in Win 10 it is not likely.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments