- Joined
- Aug 30, 2016
- Messages
- 186
- Motherboard
- Asus MAXIMUS XI HERO
- CPU
- i7-8700K
- Graphics
- RX5700 XT
- Mac
- Classic Mac
- Mobile Phone
My correct recipe for this setup got buried in a long whiny thread (me whining, that is). I thought it was useful enough -- and I've multibooted enough times and run enough stuff on both OS with no problems -- that I'm reposting it here with its own title and calling it Success.
2 internal SSDs. Mojave is on the M.2 NVME SSD on the mobo. The Win10 target is an SSD in a PCIe adapter in slot 3. ASUS MAXIMUS XI HERO. SSDs cannot be disabled in ASUS BIOS. And it's a PITA to remove the one mounted right on the mobo which is where Mojave is installed. So the Mojave SSD (which was installed first) will inevitably get clobbered when Win10 installs.
Therefore:
BEFORE YOU TOUCH WIN10 MEDIA (and get cooties):
On the MacOS side, do this:
www.tonymacx86.com
If I had only done this first, I would have saved myself about three days of hair tearing and cussing. I used the UEFI Shell method.
Oh yes, of course make sure Clover is option #1 on your boot menu also.
Now your Clover is safe from Win10 stomping and you won't get into a scary catch-22 situation like I did. Now you can don your biohazard clothing and get into the Win10 stuff.
Step 0: Use Rufus to make a Win10 USB install stick (see note below)
Step 1: Disable SATA in ASUS BIOS so Win10 doesn't go scribbling boot loaders on your data disks
Step 2: Boot your Rufus stick, using UEFI Boot Menu (F8 key on my mobo)
Step 3: Get Windows Installer start screen
Step 4: Shift-F10 to get command shell
Step 5: Use diskpart to clean target disk, just to be sure
Step 6: Exit to installer
Step 7: Go through activation code blah blah, get to disk menu
Step 8: Choose the disk (should be obvious because it has no partitions any more)
Step 9: (for me this was important) Press New button, don't try to install directly into Unallocated Space
Step 10: Disk gets partitioned with MBR and primary, but don't panic... don't reformat, don't manually add EFI!
Step 11: Now select Primary partition and Install
Step 12: Win10 install screen with progress bar. This is where it goes sideways if you've made an error.
Step 13: Assuming you made no errors, install continues with another boot. Not the stick this time, remove it.
Steo 14: And here the magic begins: at this point I was able to boot Win10 from Clover woo-hoo!
Step 14: Finish WinDoze setup, install driver for your GPU, disable auto updates, remove bloatware, customise, whatever.
Step 15: Restart.
Step 16: Get back into BIOS. Turn SATA back on. Verify Clover is #1 boot option.
Step 17: If this works for you as it just did for me, you should now be able to boot into Win10 or Mojave from Clover. Repeatably.
So out of all the clever tricks from all the clever people who so generously help eejits like me, the one that really changed the game was using the UEFI Shell in Clover to make a hard coded boot entry for Clover, so that Win10 stomping the "Windows Boot Manager" no longer breaks anything. It can stomp all it wants.
About that Rufus boot stick: this seems like a chicken/egg problem and it is: without a Win10 machine you can't make the stick. I run Parallels VM on my Hackie and have for 3 years. It turns out that the through-access to USB devices is good enough to allow Win10 VM to format and write a USB stick, so I just ran Rufus in the VM and made my boot medium. If you didn't have a WinDoze machine (even virtual) then I guess you'd have to write the ISO to a DVD and try booting it from your optical drive (if you had one).
2 internal SSDs. Mojave is on the M.2 NVME SSD on the mobo. The Win10 target is an SSD in a PCIe adapter in slot 3. ASUS MAXIMUS XI HERO. SSDs cannot be disabled in ASUS BIOS. And it's a PITA to remove the one mounted right on the mobo which is where Mojave is installed. So the Mojave SSD (which was installed first) will inevitably get clobbered when Win10 installs.
Therefore:
BEFORE YOU TOUCH WIN10 MEDIA (and get cooties):
On the MacOS side, do this:
[Guide] How to keep Clover working when installing Windows and Linux
A very common issue when multibooting macOS/OS X with Windows and Linux is that after installing the latter the computer will only boot to them. The reason for this is that Clover does not automatically add itself to the UEFI firmware boot menu that is accessible by pressing F12 or another...
www.tonymacx86.com
If I had only done this first, I would have saved myself about three days of hair tearing and cussing. I used the UEFI Shell method.
Oh yes, of course make sure Clover is option #1 on your boot menu also.
Now your Clover is safe from Win10 stomping and you won't get into a scary catch-22 situation like I did. Now you can don your biohazard clothing and get into the Win10 stuff.
Step 0: Use Rufus to make a Win10 USB install stick (see note below)
Step 1: Disable SATA in ASUS BIOS so Win10 doesn't go scribbling boot loaders on your data disks
Step 2: Boot your Rufus stick, using UEFI Boot Menu (F8 key on my mobo)
Step 3: Get Windows Installer start screen
Step 4: Shift-F10 to get command shell
Step 5: Use diskpart to clean target disk, just to be sure
Step 6: Exit to installer
Step 7: Go through activation code blah blah, get to disk menu
Step 8: Choose the disk (should be obvious because it has no partitions any more)
Step 9: (for me this was important) Press New button, don't try to install directly into Unallocated Space
Step 10: Disk gets partitioned with MBR and primary, but don't panic... don't reformat, don't manually add EFI!
Step 11: Now select Primary partition and Install
Step 12: Win10 install screen with progress bar. This is where it goes sideways if you've made an error.
Step 13: Assuming you made no errors, install continues with another boot. Not the stick this time, remove it.
Steo 14: And here the magic begins: at this point I was able to boot Win10 from Clover woo-hoo!
Step 14: Finish WinDoze setup, install driver for your GPU, disable auto updates, remove bloatware, customise, whatever.
Step 15: Restart.
Step 16: Get back into BIOS. Turn SATA back on. Verify Clover is #1 boot option.
Step 17: If this works for you as it just did for me, you should now be able to boot into Win10 or Mojave from Clover. Repeatably.
So out of all the clever tricks from all the clever people who so generously help eejits like me, the one that really changed the game was using the UEFI Shell in Clover to make a hard coded boot entry for Clover, so that Win10 stomping the "Windows Boot Manager" no longer breaks anything. It can stomp all it wants.
About that Rufus boot stick: this seems like a chicken/egg problem and it is: without a Win10 machine you can't make the stick. I run Parallels VM on my Hackie and have for 3 years. It turns out that the through-access to USB devices is good enough to allow Win10 VM to format and write a USB stick, so I just ran Rufus in the VM and made my boot medium. If you didn't have a WinDoze machine (even virtual) then I guess you'd have to write the ISO to a DVD and try booting it from your optical drive (if you had one).
everything okay after 7 restarts now
