- Joined
- Mar 10, 2013
- Messages
- 55
- Motherboard
- Gigabyte Z390 Aorus Pro Wifi
- CPU
- i9-9900K
- Graphics
- RX 580
- Mac
- Mobile Phone
Hi Guys,
I've got a working Hackintosh with OpenCore 0.8.3 able to boot Monterey (12.6) from my Samsung 500GB NVMe. My hack also has a SanDisk 240GB SSD, a 4-TB internal HDD, and an 8-TB internal HDD. I use the last two just for data and can unplug them if need be for this install. What I'd like to have is Windows 11 on the 240GB SSD and be able to choose either that or macOS on the NVMe from OC.
I've got a bootable Win 11 USB I made using the ISO downloaded from MS and following a guide to format the USB FAT32 and split install.wim using wimlib. The USB boots fine and launches the Windows 11 installer. I can Shift-F10 to go play with diskpart and fix things as needed, and when I check the list of disks using diskpart I see that I've got the 240GB SSD as Disk 0.
My general process has been this
1. Erase the 240GB SSD using Disk Utility to make it a GUID partition mapped Mac OS Extended (Journaled) drive. This is giving me a 200MB EFI partition on disk0s1, and the rest as a Data partition on disk0s2
2. Boot the Windows USB and start the installer picking a custom install
3. Select and delete the macOS Data partition on the 240GB SSD (leaving the EFI partition alone). This gives me a 240GB SSD with a 200MB EFI and the rest as unused space.
4. Select the unused space and proceed with the Windows 11 install on that.
Invariably one of two things happens, both ending in the dreaded "Windows could not prepare the computer to boot into the next phase" error.
1. If I've prepped the EFI partition on the SSD by copying the efi folder from the Win11 USB to it, then my BIOS will let me select that disk as the first boot option and I'll get all the way past "Finishing up" where I'll then hit the error above.
2. If I try it with an empty EFI partition then I can't select the SSD as the first boot option in the BIOS, so I can either leave it on the NVMe or point it to the Win11 USB - both will cause me to hit the error above even sooner, basically right after telling Windows to install on the unused space.
I've tried playing with diskpart to delete and repartition the 240GB SSD for a 300MB FAT32 EFI partition and the rest as an NTFS partition which I later delete for free space in the Windows installer. This has not changed the outcome.
My BIOS does not allow me to disable the NVMe drive, but that drive is invariably coming up after the SSD no matter how I connect SATA cables to things, and as things currently stand my target for the Windows install is disk 0 (as reported by both Disk Utility in macOS and by diskpart in Windows).
What can I do to get past this problem?
I've got a working Hackintosh with OpenCore 0.8.3 able to boot Monterey (12.6) from my Samsung 500GB NVMe. My hack also has a SanDisk 240GB SSD, a 4-TB internal HDD, and an 8-TB internal HDD. I use the last two just for data and can unplug them if need be for this install. What I'd like to have is Windows 11 on the 240GB SSD and be able to choose either that or macOS on the NVMe from OC.
I've got a bootable Win 11 USB I made using the ISO downloaded from MS and following a guide to format the USB FAT32 and split install.wim using wimlib. The USB boots fine and launches the Windows 11 installer. I can Shift-F10 to go play with diskpart and fix things as needed, and when I check the list of disks using diskpart I see that I've got the 240GB SSD as Disk 0.
My general process has been this
1. Erase the 240GB SSD using Disk Utility to make it a GUID partition mapped Mac OS Extended (Journaled) drive. This is giving me a 200MB EFI partition on disk0s1, and the rest as a Data partition on disk0s2
2. Boot the Windows USB and start the installer picking a custom install
3. Select and delete the macOS Data partition on the 240GB SSD (leaving the EFI partition alone). This gives me a 240GB SSD with a 200MB EFI and the rest as unused space.
4. Select the unused space and proceed with the Windows 11 install on that.
Invariably one of two things happens, both ending in the dreaded "Windows could not prepare the computer to boot into the next phase" error.
1. If I've prepped the EFI partition on the SSD by copying the efi folder from the Win11 USB to it, then my BIOS will let me select that disk as the first boot option and I'll get all the way past "Finishing up" where I'll then hit the error above.
2. If I try it with an empty EFI partition then I can't select the SSD as the first boot option in the BIOS, so I can either leave it on the NVMe or point it to the Win11 USB - both will cause me to hit the error above even sooner, basically right after telling Windows to install on the unused space.
I've tried playing with diskpart to delete and repartition the 240GB SSD for a 300MB FAT32 EFI partition and the rest as an NTFS partition which I later delete for free space in the Windows installer. This has not changed the outcome.
My BIOS does not allow me to disable the NVMe drive, but that drive is invariably coming up after the SSD no matter how I connect SATA cables to things, and as things currently stand my target for the Windows install is disk 0 (as reported by both Disk Utility in macOS and by diskpart in Windows).
What can I do to get past this problem?