Cannot install January patches in a healthy W10 22H2

Thanks

a. Does reagentc /info show it's enabled? Yes, I've never caught it abnormal. Yesterday I did a new Macrium Reflect WinRE Rescue Media successfully, and it works.

I've just now run the Reset Windows Update batch and it worked fine (if at all, when stopping the cryptographic service, it warned that some True Vector service, associated to Zonelarm, would be stopped too, so I shut down ZoneAlarm and gave OK), although KB5034441 failed as well (after rebooting and waiting a bit).

b. Idk how to hide an update from the command prompt or Advanced Startup, but I've used wushowhide.diagcab from a normal startup and it has done its job successfully. WU is saying that everything's updated and offering an optional preview (although I had to push the Retry button of the latter 0x80070643 failure to normalize this).

If you ever want to try again, do these commands first.

command prompt as admin:

bcdboot /bcdclean

chkdsk C: /f (y) yes and restart the computer

sfc /scannow

Dism /Online /Cleanup-Image /RestoreHealth

Extract the winre.wim file with 7zip from the latest Windows iso download. You give a letter to the recovery partition to extract it into that partition, delete the old one before.

This is a Pro so I could disable previews, but I don't want to lose resources. I've searched for WUmgr and I've found it and another similar one. I don't discard them but I'm not picky with the updates, the problem is that every some years one is picky with me or with users in this case. I had Vista for about 12 years and there was one (in 12 years) that would throw an "armored" 0x80070643 too.

If it's just a question of putting one file in the right place, they could also put the file in the Catalog and give directions to do it, maybe a batch (I'm kidding just a bit, if money depended on this...). If I've caught this well, ReAgentc / disable + replace winre.wim in C:\Windows\System32\Recovery + ReAgentc /enable puts the file in the right place.

Like many others, I have a problem installing update KB5034441 on Windows10 22H2. Thought I'd take a look at the size of my recovery partition but didn't see any partition labeled as such. Here's what Disk Management is showing. Is the recovery partition the unlabeled 527MB partition or is it hidden?

@Mike100
Just rightklick on (C.) and select "shrink Volume" then type 1024 MB.
Click on the black bar and create a new Volume. Assign letter "R"
After that you move the Recovery Folder from the 527 MB Partition to R
When everything is finished run diskpart and set the attribute to the new partition.
diskpart
sel disk 1
sel par 5
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
exit

After waiting or Microsoft to issue a fix they have apparently done so as after a reboot this AM I am now able to see photos again.
What I do not know is why the KB5034441 is still in my que waiting to be installed, wouldn't Microsoft pull this update at least from those that had the failure to install message?

Pentagon said:

@Mike100
Just rightklick on (C.) and select "shrink Volume" then type 1024 MB.
Click on the black bar and create a new Volume. Assign letter "R"
After that you move the Recovery Folder from the 527 MB Partition to R
When everything is finished run diskpart and set the attribute to the new partition.
diskpart
sel disk 1
sel par 5
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
exit

I found how to use commands & got this showing the 527MB partition is a hidden recovery partition.

It appears it can be assigned a drive letter. However looking at several examples they never showed the recovery partition with a drive letter, but always showed a Label in Disk Management.

When in Disk Management I can right click on the 537MB partition but all the options that appear are grayed out. IOW clicking on properties does nothing. I presume this is because the partition is hidden. How do I un-hide it?