@BOTMT,
Because Clover is installed on the M.2 drive in PCIEX4, have you gone into
BIOS Setup --> BOOT section and changed
1st Boot Priority to the Clover disk?
Clover should be able to detect Windows and present you with the option to boot either OS.
Strange things are afoot at the Circle K.
I tried that before by clicking on the drives with the names of the OS drives, and all I got was a black screen with a blinking white cursor.
Then I tried the EFI for each of those two drives, same thing.
Then at your suggestion, I started looking at other drives (I have a lot of them)...
And I found this one, Boot Microsoft EFI Boot from EFI...
Now that one did allow me to boot the Metro menu, which is what I usually see...
I was able to boot into each of them... but not without new issues.
For one, upon clicking restart, I get this...
I get that from either of the two, and I tried a couple of times. I'm running on the default Clover version (4xxx something), that comes with the installation packages suggested when you follow the guides.
And one final strange thing, and I noticed this yesterday too, I can disable every boot selection, reboot, and Metro Windows Bootloader still comes up and I can get in just fine.
I'm booted in now to Windows 10 after making the above screen shot. If I restart now, I do NOT get the BSODs.
Very strange indeed. I'm on BIOS F9j still, for the moment. I will likely soon switch to the custom one you have posted; it's "on the list".
Thanks again
@CaseySJ for your Excellent work, and even more Excellent help! Better service and support than any multi-million dollar tech company!
I just had a thought... It might have something to do with the way I copied the EFI partition from one drive to another. Are there some steps I could follow to re-install Clover directly to the current M.2 SSD, and maybe it would straighten things out?
Oh crap! And I just noticed CFG Lock is Enabled again... not use to messing with that one. I'll go in and disable it now.