VBox UEFI-booting to wrong EFI file

[Steve6375]

I have a VM set to Windows 10 64-bit.
The VM (Vbox 5) has a vmdk disk with a FAT32 partition
The FAT32 partition contains a \System\Library\CoreServices\boot.efi file and a \EFI\BOOT\BOOTX64.EFI file (both contain grub2).

VBox when set to EFI, always boots to the \System\Library\CoreServices\boot.efi file.

On a real PC (not MAC), it boots to the \EFI\BOOT\BOOTX64.EFI file. I would have expected it to only boot this file if the OS was set to OS X?

If I rename the \System folder, the VBox boots correctly to the \EFI\BOOT\BOOTX64.EFI file.

Is this a bug?

[socratis]

You do not have an OSX Host, you have a Windows Host, and you're trying to boot a Hackintosh!

OSX guests are only supported on Apple hardware (which you do not have). See: Important notice regarding Mac OS X as Guest and ch. 3.1.1 Mac OS X Guests of the User Manual.

Mac OS X is commercial, licensed software and contains both license and technical restrictions that limit its use to certain hardware and usage scenarios. You must understand and comply with these restrictions.

In particular, Apple prohibits the installation of most versions of Mac OS X on non-Apple hardware.

These license restrictions are also enforced on a technical level. Mac OS X verifies that it is running on Apple hardware. Most DVDs that accompany Apple hardware check for the exact model. These restrictions are not circumvented by Oracle VM VirtualBox and continue to apply.

In the really rare case (0.001%) that this is actually an Apple computer, in which you have installed Windows, and you're trying to boot a legitimate OSX guest and not a Hackintosh, send me a PM and I'll remedy the situation. Be prepared to provide evidence in such a case.

Also, consider changing your favorite internet search engine. There should be plenty of results about this issue on these forums (all of them locked, hoping that someone will get the hint), but the search engine you're using now, does not seem to return any results for some reason.

Moving to "OSX Guests" from "Windows Hosts".


PS. Good thing that I just made the warning about OSX guests a "Global" post, that would save me some locking/moving... riiiiiight...