Ok, 5 physical drives.
Need some identification as to what is what.
And, at the end of the clone process, the first thing you needed to do was...power off, disconnect any and all other dries, and allow the system to try to boot from only the NEW drive.
This is not optional.
Yes... did that, a while ago. It does. I did this with Disk-3. (At one point it was by itself.)
I was happy-go-lucky. But knew the 'reserved' partitions looked kinda-wonky. Then I moved to Disk-4 a M-2 drive. I suppose I shouldn't have done that yet before cleaning up.
Ignore Disk1, Disk2 (they are just data-disks),... and Really Ignore Disk 3... As I said, I Disk3 is just a copy now. Disk 4 is the active partition.
However, I did not expect that 'windows-update' would not work. Given the 'Wonky' Reserve partition. I also thought could be easy to correct.
P.S. I wish I disconnected Drive 3... so as not to confuse the question. I'm sure it has nothing to do with the issue, for the original question. Because both 3 and 4 suffer the same issue. How to restore a missing 'system-reserved' partition? Or what the system thinks is not a system-restore part.
You can see from the image which drives are marked 'System & Boot'. The EFI on Disk4 and the 'Copy of C' on 4."
Edit: I realize I didn't even have the question correct at the top. I changed it to 'system-reserved' partition. Not 'Recovery'.
Edit: Ok... The SYSTEM-RESERVED partition is lay-over from the MBR days, which maybe it used to be. This is a GPT disk, which should not have one. It is booting UEFI. With the EFI partition. I'm going to reexamine the 'Update' error again.
Yes, the partitions may be find. I actually deleted 'Disk-4'-'L-Copy' above, the 450mb, it was the former 'system-reserved' and then extended the EFI partition to 300MB. That also caused no-change. Still that 'update' does not finish.
The real-problem may be that this particular 'Windows-Update' just blows-out. Maybe, the error itself giving a false-reading. And its little to-do with the recent changes to the computer configuration. Its something else.
Error is 0x800F0922 Update is: 2020-12 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4592449).
This particular one seems to be troublesome