Security Update for Windows 10, 2024-11, KB5048239 getting error 0x80070643 when installing

Anonymous
2024-11-13T00:16:11+00:00

I have exactly the same problem as this (reported earlier this year), but with the new KB5048239 update. I get the 0x80070643 error when it tries to install. Retried several times, but same issue. I'm pretty sure this is the same problem that I had back in January, too. All security updates have worked fine since then, till now. At that time I was told that this was a general problem with the update and a fix was being made by Microsoft. I did wait and eventually that previous update went away. Now here we are again...

Hello,

The 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441) will not install on my Windows 10 laptop computer.

I get the following message There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80070643) Retry

When I click on Retry it says its Installing-0% for a few minutes then Installed-100% and then I get Download Error (0x80070643) There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80070643) Retry

Windows Update Troubleshooter could not fix this problem.

I'm not sure what to do, please help.

Thank you

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

72 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-12-14T15:57:02+00:00

    Simon -- that is not a lot of detail to be able to help you.

    Can you capture and post a screen-shot after every step?

    Also, please launch "Disk Management", and post a screenshot of that page.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-12-13T17:45:56+00:00

    Thanks to all that provided help.

    Here's my learning of how I finally got 'You're Up to Date'

    Hope this is not unique to me.

    My $WinREAgent directory in C had 3 folders: Backup, Rollback and Scratch

    Backup had boot.sdi, location.txt, ReAgent.xml and a winre.wim file (430,862 kb) I had extracted 6 months ago from a Win10 ISO dtd 5/5/23.

    Rollback was empty.

    Scratch had a file named update.wim (481,514 kb) and a folder named WimTempPath which was empty.

    Windows/system32/Recovery had 2 files

    ReAgent,xml and ReAgent_Merged.xml1

    So, I took the chance that 'update.wim' was really a winre.wim file that needed to be renamed and relocated.

    1. In Windows/system32/Recovery, DELETED both files above.
    2. Copy and pasted in update.wim
    3. Renamed 'update.wim' to 'winre.wim' with Admin privileges
    4. Ran Windows Update which failed.
    5. In a Command Prompt with Admin privileges, ran reagentc /disable command (success)
    6. Ran Windows Update which now succeeded. Takes longer than failed attempts took.
    7. Reboot computer. I saw instruction 'restart' but I first shut down followed by a physical ON button start and next did a restart by command.
    8. In a Command Prompt with Admin privileges, ran reagentc /enable command (success)

    Comment here: I would wait a bit between steps. MS seems to be doing a lot of reconfiguring at some points, creating new folders under $WinREAgent folder and then deleting them (or hiding them).

    1. Ran Windows Update which now succeeded under reagent enabled environment.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-12-12T18:56:31+00:00

    I made them extra large because MS originally said folder too small to get upgrade.

    2 things for me to try but might need guidance.

    I had downloaded a Win10 image in early 2024 and was able to extract a newer winre.wim file but couldn't figure out successful way to load.

    It's here:

    ************************************************

    Another solution I found said to:

    open Powershell in Admin mode.

    type: reagentc /disable

    Open \windows\system32\recovery\ folder

    del *.xml files

    now you run windows update.

    then restart PC.

    open Powershell in Admin mode.

    type: reagentc /enable

    Would this work?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-12-12T16:02:31+00:00

    Volume 3     E   Recovery Im  NTFS   Partition    251 GB  Healthy

    Volume 5          Win RE Tool  NTFS   Partition    730 GB  Healthy

    Wow. Is the size of "E:" really that many Gigabytes?

    Is it a complete "recovery" partition, as a copy of the "C:" drive?

    Also, is that "WinRE" partition really that many Gigabytes, or is it that many Megabytes?

    I enlarged my "WinRE" partition to be 1000 MB (one GB), so that the update could be applied.

    Right-mouse-button-click on the Windows "Start" button, and choose "Disk Management", capture a screen-shot, and please post it here.

    .

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-12-12T14:21:08+00:00

    DISKPART> list volume

    Volume ### Ltr Label Fs Type Size Status Info

    Volume 0 H DVD-ROM 0 B No Media

    Volume 1 Partition 300 GB Healthy Boot

    Volume 2 D HDD Pt2 NTFS Partition 578 GB Healthy

    Volume 3 E Recovery Im NTFS Partition 251 GB Healthy

    Volume 4 SYSTEM FAT32 Partition 359 MB Healthy System

    Volume 5 Win RE Tool NTFS Partition 730 GB Healthy Hidden

    Above from today.

    From my earlier notes:

    Win RE

    boot.sdi 3096 kb 6/2/2012

    ReAgent.xml 1 kb 10/2/2016

    ReCustomization.xml 6 kb 6/25/2012

    RM-WinREPart.FLG 1 kb 6/10/2012

    winre.wim 312,824 kb 10/2/2016

    Was this answer helpful?

    0 comments