Cannot install January patches in a healthy W10 22H2

Some facts:
In post #28
you wrote: "I did use MiniTool and the Recovery Partition of 527MB has only 80MB unused space."
In the next step you ask:
"Why increase the partition size if there is already enough free space?"
Question: Enough space? Is 80 < 250 ? (Is 80 smaller or bigger than 250)

In post #30
Your question: "Should the 99MB System partition also be moved after C?"
I never came across such a question.

"How risky is moving the Recovery partition?" How can it be risky, when it is just not possible and nobody told you that?

@dalchina

I read this about using reagentc to move the Recovery partition but not sure why you want to disable & then enable WinRE.
Enable or Disable Windows Recovery Environment in Windows 10

In posting #7 of the above link, it mentions the example in posting #6 does not show the Recovery partition with a "Healthy (Recovery Partition) under it". It suggests doing a repair install of Windows 10. Mine does not show that either. Also in posting #6, DiskPart shows "Hidden : No".

Mine shows "Hidden : Yes". Any chance “Healthy (Recovery Partition)” would appear if the partition was not hidden?

I was looking at MiniTool & the example showed it can be used to move the Recovery partition & it did not mention anything else that had to be done. Almost sounds too easy. Am I missing something?

Thanks again

Mike100 said:

I read this about using reagentc to move the Recovery partition but not sure why you want to disable & then enable WinRE.
Enable or Disable Windows Recovery Environment in Windows 10

In posting #7 of the above link, it mentions the example in posting #6 does not show the Recovery partition with a "Healthy (Recovery Partition) under it". It suggests doing a repair install of Windows 10. Mine does not show that either. Also in posting #6, DiskPart shows "Hidden : No".

Mine shows "Hidden : Yes". Any chance “Healthy (Recovery Partition)” would appear if the partition was not hidden?

I was looking at MiniTool & the example showed it can be used to move the Recovery partition & it did not mention anything else that had to be done. Almost sounds too easy. Am I missing something?

Thanks again

W/o knowing a lot, specially at first, I simply judged wise to unplug the crusher while servicing it. But in the middle I've also learnt that disabling WinRE does also move 1 of its 3 main files (Winre.wim) or 2 (plus ReAgent.xml) from the recovery partition to C:\Windows\System32\Recovery (the 3rd file is boot.sdi , that I've never seen in the said C: subfolder, maybe it's created automatically off Idk). For instance, this means that deleting the recovery partition (for instance intending to recreate it afterwards) w/o having disabled WinRE, means LOSING that file (btw the MS directions to enlarge the recovery partition do exactly this, they don't extend the recovery partition, they "delete partition override" it and create a new one afterwards, of course with WinRE disabled).

A possibly outdated version of Winre.wim (Idk if enough for WinRE working as it should in all cases and possible uses, nor if updatable in all cases) can be recovered from the installing media. As for ReAgent.xml, the installing media has a usable generic version that's updated inmediately upon enabling WinRE. I haven't seen boot.sdi in the installing media, at least in the same location as the other two files, but I've never seen a recovery partition w/o one.

Any chance "Healthy (Recovery Partition)" would appear if the partition was not hidden? Windows Disk Management (diskmgmt.msc) doesn't have "global view". "Healthy", in the tool's language just means that the partition has a recognized file system, and "(Recovery Partition)" just means that it has the necessary ID (0x27 in MBR disks and de94bba4-06d1-4d40-a16a-bfd50179d6ac in GPT ones, in the latter case "gpt attributes" must be set to 0x8000000000000001 as well, but Idk if diskmgmt.msc checks that).

For instance, this thread's post #2 shows a disk (where WinRE works well and KB5034441 installed well after resizing the indicated partition) with 2 partitions showed as "Healthy (Recovery Partition)", although only the indicated one actually acts as it (I suppose it's "mechanically impossible" more than one, except if, in a just imaginary erroneous situation that Idk if it's possible, one is doing half the WinRE "services" and the other the other half).

I've seen it mentioned a few times that the update has been pulled from the Microsoft Update Catalog. That's probably why it won't update.
https://catalog.update.microsoft.com...spx?q=KB503441

Also saw a couple comments that since KB503441 was not updating that this prevented other updates. I hid KB503441 and almost immediately got one of those daily security updates.

Mike100 said:

I've seen it mentioned a few times that the update has been pulled from the Microsoft Update Catalog. That's probably why it won't update.

It has never been offered in the Update Catalog!
So it's a bad excuse not to do the necessary steps.

Mr. Cerebrus,
you don't have to monitor every update. Just read the official MS statement.
Do you know how to find that?

I've seen this & similar instructions on how to move the Recovery partition.
Moving Windows Recovery Partition Correctly - theDXT

But I've also seen this.
How to Move Windows 10 Recovery Partition without Data Loss?
How to Move Windows 10 Recovery Partition without Data Loss?

Does that mean AOMEI is taking all the necessary steps to preserve the Recovery partition data?

@Mike100
Every week you come with a new question. And with each question you prove that you don't understand your particular partition problem. The solution to your problem is given in post #18.
But obviously you refuse or do you still believe that you can manage it in a different way? Mission Impossible!