Well, that worked just as I expected!
I'm not sure if it's still relevant but in the past Windows insisted on being on the first drive or partition on a system.
So, with that in mind I booted into the PC BIOS and set the HDD Caddie as the first boot device and the onboard NVMe SSD was moved down to second place.
I clicked on the NVMe entry and set it to disabled and restarted the machine.
Since there were no bootable drives it went straight to the Beelink Windows Recovery USB Media.
First I removed the LAN cable so Windows would set up a local account only!
I let Windows install and set it up with my login details and restarted the machine to the BIOS.
I re-enabled the NVMe SSD entry and rebooted. After the machine got to the Beelink logo I hit F12 and was presented with my two drives to choose from!
Both boot perfectly normally.
I prefer this setup because Linux GRUB knows nothing of Windows and Windows Boot Loader knows nothing of KDE Neon!
I deserve a beer!
https://photos.app.goo.gl/seGwENNPyCWBgDhi6
I'm not sure if it's still relevant but in the past Windows insisted on being on the first drive or partition on a system.
So, with that in mind I booted into the PC BIOS and set the HDD Caddie as the first boot device and the onboard NVMe SSD was moved down to second place.
I clicked on the NVMe entry and set it to disabled and restarted the machine.
Since there were no bootable drives it went straight to the Beelink Windows Recovery USB Media.
First I removed the LAN cable so Windows would set up a local account only!
I let Windows install and set it up with my login details and restarted the machine to the BIOS.
I re-enabled the NVMe SSD entry and rebooted. After the machine got to the Beelink logo I hit F12 and was presented with my two drives to choose from!
Both boot perfectly normally.
I prefer this setup because Linux GRUB knows nothing of Windows and Windows Boot Loader knows nothing of KDE Neon!
I deserve a beer!
https://photos.app.goo.gl/seGwENNPyCWBgDhi6
Comment