Contribute
Register

Guide: MultiBooting UEFI

I have no idea why but from reading the below thread removed the 3 USB drives I had in my system and inserted just the windows 10 USB and it worked now. So weird! I LOVE windows sometimes...

https://www.tonymacx86.com/threads/unable-to-install-windows-10.180258/
It is because there is a hierarchy of USB ports and one of your other USB drives was in a port with a higher priority than the Windows USB drive - and the installer always looks at the highest priority USB port instead of the one the drive is actually in. This is no problem if the higher priority ports are empty - the installer just looks at the next one - but if there is a drive there, then naturally it does not have the Windows boot files on it and the Windows installer cannot reboot the computer after unpacking files because if a drive without the boot file is present in the port it does not look at the next port if it does not find the boot file - it just throws up the error message.
 
UPDATE: found a fix, see at the end

I've tried this guide and installed all 3 systems (Sierra, Win10, Ubuntu 16) on my 4TB HDD, however I can't boot to Sierra natively. I can only boot off HDD when I boot to USB Clover bootloader from the Unibeast installation USB. However, when I select the bootloader created by Multibeast called 'Mac OS X' from my UEFI boot menu, instead after like 1 second it goes directly to my second boot priority, which is Ubuntu (which loads fine). When I boot from Unibeast USB Clover, I can also boot Windows 10 just fine and also can boot to HDD Sierra just fine. Yet, I can't boot to Sierra natively, the HDD Clover doesn't seem to work :(
Any idea what could be causing this?
I've checked that the HDD EFI partition has Clover folder on it and seems to have same files like the USB EFI partition.
I've also tried different driver options when installing MultiBeast (though not sure how this would help is Clover doesn't even start at boot).
Otherwise I don't understand how to troubleshoot this and what happens to Clover when it's started off HDD vs USB.
Thanks for any suggestions

P.S.
The only difference from the guide was that I burned Win10 .iso to a DVD instead of a flash drive since I used my 2 drives for OSX and Ubuntu installations.

Boot devices visible in UEFI Boot menu selection
Mac OS X
ubuntu
UEFI: Sandisk <- this is Unibeast OS X installation USB
(Windows is missing since the respective file was renamed per this guide)

UPDATE: Turns out that the 'Mac OS X' entry in the boot menu was pointing to the partition where Sierra was installed instead of to the \EFI\Clover\Cloverx64.efi, that's why it wasn't booting anything.
  1. I booted from USB Clover (longer story: this was El Capitan USB Clover since I decided to install that instead of Sierra, thinking maybe it would fix the issue: and I saw two Clover Options icons, realizing that my HDD Clover was ok and could be fixed)
  2. Clicked on green icon with Clover Options (second one, which I assumed was from the HDD Clover, but maybe the original would also work)
  3. Chose the option to populate boot menu with Clover items
  4. Now, choosing any of those new menu items would boot to HDD Clover, where I could choose boot to macOS Sierra without any USB present!
Tip: you can cleanup all those extra options inside Clover via Clover Configurator (go to GUI and unselect Legacy, but select Linux) and pre-Clover (in BIOS or boot selector) via Windows EasyUEFI utility or via Clover command shell https://www.tonymacx86.com/threads/...boot-entries-prevent-further-problems.175274/
 
Last edited:
It is because there is a hierarchy of USB ports and one of your other USB drives was in a port with a higher priority than the Windows USB drive - and the installer always looks at the highest priority USB port instead of the one the drive is actually in. This is no problem if the higher priority ports are empty - the installer just looks at the next one - but if there is a drive there, then naturally it does not have the Windows boot files on it and the Windows installer cannot reboot the computer after unpacking files because if a drive without the boot file is present in the port it does not look at the next port if it does not find the boot file - it just throws up the error message.

Oh interesting - thanks!
 
Ok now I have another problem :(

I installed windows 10 fine, renamed the bootloader file, installed macOS fine and ran multibeast.

Clover pops up on boot which is great and I can boot into macOS!

However when I select 'Boot EFI from Windows EFI' (or whatever the exact wording is) then the little windows loading circle thing starts spinning but then my monitor suddenly goes into standby and it gets no further.

... any ideas what is going on?!

[To clarify I had both windows 10 and El Capitan working fine on my system before (although I used a USB key to boot into OSX previously) so they both definitely should work]
 
Ok now I have another problem :(

I installed windows 10 fine, renamed the bootloader file, installed macOS fine and ran multibeast.

Clover pops up on boot which is great and I can boot into macOS!

However when I select 'Boot EFI from Windows EFI' (or whatever the exact wording is) then the little windows loading circle thing starts spinning but then my monitor suddenly goes into standby and it gets no further.

... any ideas what is going on?!

[To clarify I had both windows 10 and El Capitan working fine on my system before (although I used a USB key to boot into OSX previously) so they both definitely should work]
OS X and Win10 on same or separate drives?
 
Same drive - only one plugged in - did exactly as guide said.

Weird thing is it appears to be booting into windows (get the circles) then seems to die.
 
Sorry if this was already asked. Can you install Ubuntu on a 2nd drive without ever installing windows? Would you just skip the windows step or is that a prerequisite?
 
Sorry if this was already asked. Can you install Ubuntu on a 2nd drive without ever installing windows? Would you just skip the windows step or is that a prerequisite?
Yes. See the other pinned guide in this forum for booting UEFI on separate drives.
 
When I want to install win 10, I delete the partition and then create partition,it warns windows cannot be installed on this disk. The selected disk is of type GPT partition style. what to do now?
 
When I want to install win 10, I delete the partition and then create partition,it warns windows cannot be installed on this disk. The selected disk is of type GPT partition style. what to do now?
Win10 installer USB, if properly made, has both Legacy and UEFI installerson it and it will show uip in your boot devices as USB Win10 installer and UEFI USB Win10 installer.
You boot with function hotkey that allows you to select a boot device and select the UEFI USB Win10 installer.
 
Back
Top