I have been working to verify
ariftwister's claims that EaseUS was the cause of the problem, and was able to do so. I installed the Easeus partition manager and made a change to a partition. The two recovery partitions changed to a Type designation of
OEM. After the change I saw a popup message from Easeus about updating the system information, which is more than likely when the problem occurred.
But the problem was a little more involved than just changing a partition ID to the Recovery GUID. On my system, the IDs were already set to the Recovery GUIDs and were not changed when the error occurred.
What it appears happened, was the Easeus utility removed the volume information from the two recovery partitions, as Diskpart noted in the quoted material. Since replacing the Partition ID with the same number was of no help, I ended up changing them to the Primary partition GUID, ebd0a0a2-b9e5-4433-87c0-68b6b72699c7. After a Reboot, the partitions showed up as Type Primary in Diskpart.
I then changed the partitions back to the Recovery GUIDs and the system was back to normal and the
reagentc /info command completed.
Luckily you can copy and paste into, out of, and within a Command Prompt window, those GUID numbers can be a pain to type. :shock:
The attachments might help explain.
DISKPART> det par
Partition 6
Type : de94bba4-06d1-4d40-a1a6-bfd50179d6ac
Hidden : Yes
Required: Yes
Attrib : 0X8000000000000001
Offset in Bytes: 234952327168
There is no volume associated with this partition.
DISKPART> lis par
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 OEM 300 MB 1024 KB
Partition 2 System 99 MB 301 MB
Partition 3 Reserved 128 MB 400 MB
Partition 4 Primary 149 GB 528 MB
Partition 5 Primary 68 GB 150 GB
Partition 6 OEM 15 GB 218 GB
DISKPART> exit
Leaving DiskPart...
C:\Windows\system32>reagentc /info
REAGENTC.EXE: Operation failed: 3
REAGENTC.EXE: An error has occurred.
