This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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
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.
> This command can only be executed from an elevated command prompt.
Correct.
Right-mouse-button click on the "CMD.EXE" file, and choose "run as Administrator", and try again.
The presence of "C:\users\natal" instead of "C:\Windows..."
indicates that you skipped that necessary step.
C:\Users\natal>
C:\Users\natal>reagentc /disable
This command can only be executed from an elevated command prompt.
REAGENTC.EXE: Operation failed: 5
REAGENTC.EXE: An error has occurred.
C:\Users\natal>
C:\Users\natal>dir c:\windows\system32\recovery /a
Volume in drive C has no label.
Volume Serial Number is 92A0-AE84
Directory of c:\windows\system32\recovery
08/30/2021 04:45 PM .
08/30/2021 04:45 PM ..
08/30/2021 02:48 PM 1,104 ReAgent.xml
1 File(s) 1,104 bytes
2 Dir(s) 155,368,226,816 bytes free
>> every time Windows is doing a update, it slows the computer down to a crawl,
I think that it is time to replace your "antique" of a "spinning" disk-drive by current storage technologies: either a SSD (solid state disk) with a SATA interface, or a NVMe memory-stick, if your motherboard supports NVMe.
Also, how old is your current disk-drive? How reliable will it be in a few years? If you purchased a computer with Windows 7 pre-installed, your disk-drive will be at least TEN years old. If you purchased a computer with Windows 10 pre-installed, your disk-drive will be up to TEN years old.
Like ten-year-old automobile tires, replace them before they "blow", usually at the worst-possible time.
The big advantages of upgrading to SSD are MUCH FASTER boot-up times, and MUCH QUICKER runs of Windows Update.
Once you go SSD, you'll never go back! :-)
Like others have mentioned, this update keeps reloading continually, even though it shows it has already sucessfully installed. Of course every time Windows is doing a update, it slows the computer down to a crawl, so this is a massive fail that doesn't seem fixable.
>> the host boot drive (C:/F:) is a drive drive raid array I believe Raid 1 (mirrored)
The first part of the exercise of copying "F:" to another disk-drive is to verify that there are no bad sectors that cannot be copied.
The second part of the exercise is to update your hyper-visor to create a new VM, pointing at the contents of the COPY of the "F:" disk-drive.
The third part is to (virtually) boot from the newly-created VM.
I hope this helps.