10 Pro (22H2) Can't Install 3 Pending Updates...

Windows Version: Win 10 Pro V. 22H2 Build 19045.3570

I've had 3 pending updates since last month that fail every time I try to install them:

Update 1 01/24 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)
ERROR: Download Error: 0x80070643

Update 2 - 01/24 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5034122)
ERROR: - 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

Update 3 01/24 01/24 Cumulative Update Preview for Windows 10 Version 22H2 x64 based Systems (KB5034203)
ERROR: Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x8007000d)

---

I've seen multiple posts about these updates on the MS forums saying the only fix is to resize the recovery partition... but that seems dangerous and unnecessary lol. Am I to just pause Windows updates until Microsoft puts out a fix?

Apparently KB5034122 & KB5034441 both suffer from the recovery partition bug. I was just hoping for a workaround other than hiding the update or having to manually resize the recovery partition and risk breaking my Windows partition.

I don't have preview updates enabled, but KB5034203 showed up as an optional update. When I attempted to install it, it spat out that error.

Ah well. Figured I'd ask.

Thank you for the reply.

@hlve
There is no Recovery Partition Bug! Only in your mind!
Try to install WIN10 on a 10 GB Partition and see what happens. But don't come back with a BUG-Statement!
The 3 updates that can't be installed on your PC are completely independent!
And tomorrow you have 4 udates that refuse to get installed! I bet!

hlve said:

Apparently KB5034122 & KB5034441 both suffer from the recovery partition bug. I was just hoping for a workaround other than hiding the update or having to manually resize the recovery partition and risk breaking my Windows partition.

I don't have preview updates enabled, but KB5034203 showed up as an optional update. When I attempted to install it, it spat out that error.

Ah well. Figured I'd ask.

Thank you for the reply.

I could install KB5034122 (I haven't attempted KB5034203) downloading the installer from the Catalog, although I did a Windows drive restore from an imaging tool backup after my first batch of attempts. I did the following:

0) I had WU paused. Recovery partition is possibly too small for KB5034441. I do a Windows drive backup with Macrium Reflect (*).

1) Unpause it. WU tries to install KB5034441 first and fails with 0x80070643. KB5034275 (.NET update) and KB5034122 fail afterwards (I cannot recall in which order between the two) with 0x80070002.

2) I extend the recovery partition 1500MB towards the left with diskpart, following MS directions (MS suggests 250 MB, but many have succeeded with more than 250 MB, that is a minimum). I do more failed attempts, including one with KB5034441 hidden in which WU fails with the other two. Maybe this latter attempt is worth for you. (**)

3) Restore the backup in 0). The Windows drive is now as if 1) and 2) had not happened at all (I only have Windows in this drive, if I had data partitions in it, I would have restored the Windows partitions only).

4) I extend the recovery partition 1500MB towards the left with MiniTool Partition Wizard elevated this time.

5) With WU still paused, I run the installers of KB5033909, KB5033918 (these two are the Catalog's equivalent to KB5034275) and KB5034203 rebooting after each (3 times total). All succeeded. This is the main point of this post, but I cannot know what would have happened if I had managed to hide KB5034441 before unpausing WU, and WU had operated itself with KB5034275 and KB5034203 only, from a clean state.

6) I unpause WU and it installs KB890830 (monthly anti-malware check) and KB5034582 (.NET preview, I guess this was installed because I did not have a "KB5034275" entry in the list, although I had its Catalog components) successfully, but it fails with KB5034441. I hide it.

(*) If you don't have an adequate backup to "go backwards in time", the Catalog's installers might succeed or not, Idk, but they don't have contraindications afaik (if at all they are not logged the same in the list of installed updates).
(**) As I had the "clean" resource of restoring my backup, I did not try the Catalog's installers in this phase.