Haha no need to apologise! Gonna give that a go :)
Windows 10 22h2 security update [KB5034441] fails to install with code: 0x80070643
* * Mod note on 1/12/24. * *
Please see: https://www.yourwindowsguide.com/2024/01/fix-error-0x80070643-for-windows-10-kb5034441-update.html
The latest update downloads and then fails to install.
- OS Build # 19045.3930.
- Update Troubleshoot tool repair but it does not help.
- MS Windows Update Catalog does not have the update.
- Other updates all went through without any trouble.
This is a brand new update. Is this a known issue? Is there a resolution specific to this update? (Please do not copy and paste standard procedure)
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.
194 answers
Sort by: Oldest
-
Anonymous
2024-01-10T17:25:22+00:00 -
Anonymous
2024-01-10T17:34:21+00:00 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB503444) fails to install! Fix it!
-
Anonymous
2024-01-10T18:38:24+00:00 This is not a trivial exercise. I lost my copy of the WINRE.WIM file which should normally toggle between the C:\windows\system32\recovery folder and the recovery partition, as the /disable and /enable switches are used with REAGENTC. I had to fetch a copy from a cloned system disk I made a few days earlier. That required mounting the hidden partition and doing an xcopy of the missing file to my C drive. Then I had a problem enabling the file (Windows reimage not found) and I had to use the /setreimage switch to get the /enable switch to work. Also to shrink the OS partition in order to free up space to be added to the recovery partition, I had to use DISKMGMT.MSC because the shrinking procedure in the KB5034441 release notes didn't work for me.
-
Anonymous
2024-01-10T18:48:52+00:00 update instal fail
-
Anonymous
2024-01-10T19:35:43+00:00 I have the same problem as everyone else. This is the first time this has happened to me during an update.