New
#31
*** Note: I didn't realized it now says Windows Boot Manager, now I'm even more confused)
1st of all, thank you very much, guys!
Current Disk Management (Man, it looks awful at the moment)
And the weirdness in my BIOS
Disk Boot Priority: (I always had whatever OS I wanted to look for first selected according to the drive)
I disabled everything except my main drive (disk 0 with the restored partition in GPT with Win 10)
And here's the funny part....
P1: Is my Disk 1 (secondary drive, the one with only data), it wasn't connected when I clean installed Windows 10, and it was already there....
With P0: (Disk 0) selected with only that disk connected, the clean install booted up correctly.... But not when I restored the image....
So, there's definitely something wrong there...
Selecting that P1 - Windows Boot Manager, did the trick...
Feeling silly is an understatement...
The question remains, why was the Windows Boot Manager linked to a drive that wasn't even connected?
Could it be just a coding error on the BIOS?