Windows 10 Update can't update system reserved partition

This looks like a GPT initialized disk and UEFI firmware.

See Sample: Configure UEFI/GPT-Based Hard Drive Partitions by Using Windows PE and DiskPart for the default and recommended disk schema.

Your setup doesn't seem to have a Microsoft Reserved partition (different from System Reserved) - it has it's own type of MSR. This is a hidden part, so it might only be visible in Diskpart.

To cut down on any confusion, I would physically swap the drives so that
Disk 1 becomes Disk 0 and
Disk 0 becomes Disk 1.

It's just a matter of of pulling the connectors and reconnecting them to the other port.
After you have removed the bogus System REserve partition you created (as suggested by NavyLCDR) and swpped the drives,

Please post a new Disk Management screen shot:

Method One: Use Disk Management in the x-Menu (right click the Windows logo, select Disk Management)

Select View > Bottom > Disk list

Maximize the window and grab the screen shot.

---

Method Two: Use a custom MMC to present Disk Management with pertinent information

If you've already downloaded the custom MMC, go to Step 2 to launch it and then grab the screen shot.

Step 1: Download this zip file (contains dmDskmgr-vd.mmc)

dmDskmgr-vd.zip

Step 2: Double click dmDskmgr-vd.zip to open the compressed folder
Double click dmDskmgr-vd.mmc to launch the custom Disk Management console
You'll get an output similar to this:

Press Alt+PrtScn to grab a snapshot of just the Disk Management window
Open Paint and Ctrl+V to paste it, then save the image

---

Attach the image to a new post.

NavyLCDR said:

If he swaps the drives, he will also have to change the boot order in bios.

nah, a HD boot is a HD boot - it finds the first boot instruction, which should be on the EFI part (I think).

I could be wrong ,,, I don't have a UEFI system.

That's the way I understand bootstrapping - use the first boot code found then boot to the OS per the BCD store

Or change the device boot order (HDD, Optical drive, or Flash drive) and look on that device for the boot code.

Fair enough, let me restate: I don't have a UEFI system ... and I don't have a system with more than one drive at this time

I'm basing this on MBR and active partitions (UEFI systems don't normally have the active flag set - some do, not sure why)
See: Boot Sector

Wiki: Unified Extensible Firmware Interface - Wikipedia, the free encyclopedia

Booting
UEFI booting
.....
Operating system loaders can be automatically detected by a UEFI implementation, which enables easy booting from removable devices such as USB flash drives. This automated detection relies on a standardized file path to the operating system loader, with the path depending on the computer architecture. The format of the file path is defined as <EFI_SYSTEM_PARTITION>/BOOT/BOOT<MACHINE_TYPE_SHORT_NAME>.EFI; for example, the file path to the loader on an x86-64 system is /efi/BOOT/BOOTX64.EFI.

Booting UEFI systems from GPT-partitioned disks is commonly called UEFI-GPT booting. It is also common for a UEFI implementation to include a menu-based user interface to the boot manager, allowing the user to manually select the desired operating system (or system utility) from a list of available boot options.

So, as I said ... I could be wrong, even with the citation.

Rather than continue our discussion, I suggest that the drives be left alone in order to get on with trouble shooting the issue.

The reason I posted was to note that I didn't see a System Reserved partition (referencing the error msg in post# 1) and suggest that it might be an MSR. Then I thought more and realized that Disk Management might not present the MSR. The disk swaps was a best guess that the Thread Starter has the disks in the wrong order.

I enjoy a healthy discussion, but I think I'm only muddying the waters, so I'll bow out. I look in to see where this goes because I'm interested in threads with these types of issues.

Bill
.