My "Recovery" partition has 563,263,211 bytes showing as "used", and 972,881,920 bytes showing as "free".
This is much more free-space than the "required 250 MB".
Hmm.
This is yet another "fail" for Microsoft's "Quality Assurance" department. :-(
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
My "Recovery" partition has 563,263,211 bytes showing as "used", and 972,881,920 bytes showing as "free".
This is much more free-space than the "required 250 MB".
Hmm.
This is yet another "fail" for Microsoft's "Quality Assurance" department. :-(
Joyce, you do not want to revert to Windows 10.
It will reach the end of its ten-year "Microsoft Product Lifecycle" in mid-October 2025 - relatively soon.
At that time, you will need to reinstall Windows 11, to have a supported operating system.
Instead, just ignore the fact that this update will not install.
This update does not address any "security" issue that will affect you.
Soon, Microsoft will acknowledge the issue, and will issue an update that will install.
How .can I go back to Windows 10
This is for my Windows 10 machine, which has a recovery partition that is gigabytes in size. I have not run this for my Win11 machine.
C:\Windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:
Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 7c9570ac-675a-11ec-86ae-e0cb4ebb2b6e
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
C:\Windows\system32>dir c:\windows\system32\recovery /a
Volume in drive C is Samsung Source Disk
Volume Serial Number is BE34-C6B0
Directory of c:\windows\system32\recovery
2024-11-13 12:56 PM <DIR> .
2024-11-13 12:56 PM <DIR> ..
2024-11-13 12:57 PM 1,077 ReAgent.xml
2019-06-12 10:40 AM 1,118 ReAgent_Merged.xml1
2023-02-15 07:40 AM 777,602,343 Winre.wim
3 File(s) 777,604,538 bytes
2 Dir(s) 54,091,431,936 bytes free
C:\Windows\system32>reagentc /enable
REAGENTC.EXE: Operation Successful.
After lots of powershell commands, Claude 3 says
"Since we've confirmed:
It's looking like:
Joyce, going back to Win10 won't help. This is started on my Windows 10 machine and last night appeared on my Windows 11 computer.
I went through the repartitioning process (I understand such things) according to MS instructions, and it reported that it did not need to be resized. Yet the error still occurs.
I think the problem is that there is no one at MS who understands how the original code works, and there is no one to train new employees. This issue has been going on for months for many of us.
I've also run DISM, sfc /scannow, chkdsk, troubleshooter, rebooting and retrying, booting into safe mode, restarting the Update Services in a variety of ways, virus scans, resetting windows components (e.g. net stop wuauserv etc.)
Nothing works.