1. Get Hackintosh up and running with opencore
2. Get another SSD to install windows 11 on.
3. unplug the hackintosh SSD while installing windows 11.
4. when windows 11 is working fine, plug the SSD with MacOS back in, and set that as first boot device.
5. Find both your volumes in opencore picker, and control + enter the MacOS Partition, cause it's highly illegal to have windows 11 as the primary boot.
This is the easiest way, to prevent f**ing up your boot. =)
Fair warning to anyone who wants to add Ubuntu to NVMe hackintosh, even if it's on another drive... Ubuntu boot config does not play well with OC
Re messing up hackintosh in EFI in dual-boot scenarios. I installed Win10 and upgraded to Win11 on a SATA drive with OC / Big Sur on NVMe, and this caused no problems for the NVMe. But adding Ubuntu to the same SATA drive repeatedly clobbers the NVMe EFI folder even though
To be clear:
NVMe: OC+MacOS
SATA: Ubuntu, Windows
I am careful to tell Unity (Ubuntu's installer) that the installation is on the SATA. It puts Ubuntu where I want, updates that drives boot loader, then goes ahead on its own and writes over the NVMe anyway — including when performing yearly incremental dist-upgrades e.g. 21.10.
Ubuntu Unity overwrites:
EFI/BOOT/BOOTx64.efi
and adds an
EFI/Ubuntu folder which sometimes gets seen by the chain loader associated with dual-boot Windows / Ubuntu when booting from the SATA.
When Unity skroggs the NVMe EFI part, it doesn't touch the EFI/OC folder, so you won't lose your hack configuration, but the whole thing is still a PITA.
Beyond having Unity working behind my back, the general capability of boot-loaders from one OS realm to load neighbor OSes turns into a byzantine labyrinth of confusion over what will happen where choosing one thing in the BIOS leads to another whether you intended it or not which means keep a level head when trouble-shooting.
I submitted a bug report at Canonical 6 mos ago and there was a follow-up question from their support which I answered, but when Ubuntu 21.10 came out, my NVMe EFI got stepped on again. So they either are clueless or don't think the behavior of jacking the EFI on a drive unrelated to the install is a problem. (Linus Toralds was right when he saw EFI coming decades ago and raised the red flag: EFI architecture is a nightmare.)
It amuse me to note that Windows has been well behaved for me by comparison, it's installers don't mess with any device except the target and multi-boot is not disturbed by its machinations. And Apple doesn't really use the EFI partition except as a temporary area, while hackers are using it to end-run Apple, so it all feels delightfully bizarre.
I keep a USB stick around with a known-good OC EFI so I can boot and fix the NVMe when this happens. But when also testing MacOS updates, OC updates, and config adjustments for problematic HW, keeping track of which OC vs which Mac while having 3rd party trounce EFI is exhausting.
I suppose this should be posted over in Boot Loaders but I am too pooped keeping track of this forum's insane filing system to worry about it. Maybe someone will find this vital lore over here on page 3404 of 'Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580'