A bit of preamble.
For a number of weeks I have been trying to convert an MBR based NVME SSD to GPT (on the basis I will need to turn off CSM on my motherboard to turn on AMD SAM once released by Asrock).
During the course of my tweaking, I may have deleted a system reserved partition and caused some general mayhap. The end result is I needed to reinstall W10 yesterday, which unfortunately appears to have gone wrong.
When looking at Disk Manager my (NVME boot) C: drive is shown as "Healthy (Boot, page File, Active, Crash Dump, Primary Partition)" and the backup drive (SATA3 SSD) as "Healthy (System, active, primary partition)". The end result is that I now cannot boot without having both drives plugged in (not an issue) but I still cannot convert the boot drive to GPT as the "system" is on the other hard drive.
My gut feeling is that I need to install W10 again with all other drives apart from the NVME SSD installed, but I would be grateful if anyone could talk me through another fix. I have tried bootrec.exe and a repair of W10 using a recovery drive.
Thank you
Alec
For a number of weeks I have been trying to convert an MBR based NVME SSD to GPT (on the basis I will need to turn off CSM on my motherboard to turn on AMD SAM once released by Asrock).
During the course of my tweaking, I may have deleted a system reserved partition and caused some general mayhap. The end result is I needed to reinstall W10 yesterday, which unfortunately appears to have gone wrong.
When looking at Disk Manager my (NVME boot) C: drive is shown as "Healthy (Boot, page File, Active, Crash Dump, Primary Partition)" and the backup drive (SATA3 SSD) as "Healthy (System, active, primary partition)". The end result is that I now cannot boot without having both drives plugged in (not an issue) but I still cannot convert the boot drive to GPT as the "system" is on the other hard drive.
My gut feeling is that I need to install W10 again with all other drives apart from the NVME SSD installed, but I would be grateful if anyone could talk me through another fix. I have tried bootrec.exe and a repair of W10 using a recovery drive.
Thank you
Alec