Also: If you have a Titan Ridge card (which you’d remove for the installation), don’t forget to disable the corresponding SSDT in your OC config.Yes thanks thats what i figured and thats why i didn’t want to remove my OC drive.
I’ll try it again with everything non essential disconnectedthanks 🙏
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
not to forget to make a bootrom backup before messing with UEFI Windows!
If you get Windows certificates you can flash back your backup. If you have none you need a bootrom service.
If you get Windows certificates you can flash back your backup. If you have none you need a bootrom service.
Hm no luck unfortunately. I tried your method 5 times with different .iso and also some other methods creating a bootable USB using rufus ect. but none seem to work. I took out everything except the SATA-SSD that has OC on it, my Radeon VII and the PCIe Card that houses my Nvme SSD where i want to install Windows to.
Could this be the issue? Is it not possible to install Windows on an nvme drive with the cMP?
As far as I know, UEFI Windows can be installed on an NVMe drive in the cMP, but it might be worth testing an installation to a SATA drive to rule out the possibility of a hardware incompatibility (for example, with PCIe adapters).
Another possibility is that something in your config is problematic for the installation (device properties, renames, etc.), so you might want to test an installation with the basic config in post #1 (make sure to have a natively bootable macOS installation to restore your original config after the test).
So i managed to get an install running off an SATA SSD installed in Bay2 and OC SATA SSD in Bay 1. So its likely something in MartinLo’s config is preventing an NvME install to boot. I don’t really wanna mess around with it too much since everything else is just working so perfectly and i really only occasionally use Windows for gaming. So i will use the nvme as a data drive for my win install on sata ssd i guess. Shouldn’t make much of a performance difference anyways…
Thanks a lot for your help as always!
I thought I would post this comment from my YouTube channel. This guy seemed to have been able to install Mac OS and Windows on a single NVMe. Interesting... My Windows 11 is on a ssd in sata bay 2, OC is on sata bay 1, my Mac OS is on NVMe pcie slot 3.
Here is his post:
Comment on "WINDOWS 11 MAC PRO 5,1 INSTALL with RUFUS"
Skip741 x • 3 weeks ago
Glad to see u got this done! I talked with u a while back when I was trying to do a
monterey/ Uefi windows 11 dual boot from a Single nvme...The big concern was of course, bootrom corruption... issue solved: I also used martin lo's efi but as a double protection, you want to do the rufus creation of win 11 and not only remove TPM but also remove secureboot in rufus options, in
one swoop, this removes the damn secureboot aspect of windows and thus no risk of it trying to write to the mac bootrom... does it work? yes! Ive confirmed it by dumping the rom and checking for microsofts secureboot certificates...none to be found brother...Been using it for about month and a have zero issues.. Previously, I had tried a martin lo efi With secureboot functional in windows and it Was Not protecting the bootrom properly....rufus did the magic..mine is 2 partions on one nvme done in GUID format ...monterey apfs on 1 and the windows on the other formated in ntfs...EACH partition has its Own efi partition and folder...i did Not want to merge the 2 efis into one... I used macrium to image an operational uefi windows system complete with efi onto the ntfs partition...I did not use bootcamp.. keep martin lo's efi on a usb and it is Always the 1st boot device...all booting happens Thru the usb and never without it... like u said, win 11 is killer fast and boots win 11 in 3 or 4 secs for me... i use an r×570 in a 6 core 5,1.. bootscreen shows and I just pick win or mac and off I go... thought I;d share this with u and anyone else who wondered if it could be done.
so after installing all the nvme drives and my Titan Ridge again the Windows System won’t boot again even off the SATA SSD. I have no idea but it seems to have something to do with the Sonnet 4x4 PCIe Card i’m using.
I have spent hours today assembling and disassembling my Mac today and i won’t start again…
Will try this now:…
Does your Opencore efi folder contain the 'Microsoft" folder? Windows 11 is so snappy for me running off sata bay 2 not sure the NVMe route is worth it if you are just using it for occasional gamig which is what I use it for. This is my video on installing Windows 11 using rufus I already had windows 1o installed and put 11 on a new SSD
yeah i saw this too today. i had an issue during the installation thou.
will try again...
i want to install it on the SATA SSD in Bay 2 and it worked without my nvme pcie card installed but after i reassembled everything it freezed booting just as before when i tried installing on an nvme. i need that nvme pcie card obviously since it has my main OS and Data drives in it...
also my OC folder doesn`t contain any Microsoft stuff just Apple and OC as it should be i think at least looking at cdf´s tutorial in post1. On my Windows SATA SSD i have an EFI partition containing an EFI folder and inside is the Microsoft folder i think you are referring to.
try moving the microsoft folder to the opencore efi folder and remove it from the windows drive efi. If it's not in the opencore folder opencore won't see the windows drive from what I understand. My Window drives EFI does not contain a EFI folder at all. I asked about this earier today. see this thread. https://forums.macrumors.com/thread...-1.2356603/page-3?post=31899035#post-31899035
Attachments
Last edited:
Actually, OC will find it regardless of which EFI partition contains the Microsoft folder. The idea for placing it in a different EFI partition is to prevent Windows from replacing the OC BOOT folder with its own version during updates.
Note: If you've let Windows install the EFI files automatically, then you might want to make sure that your BOOT folder contains the OC BOOTx64.efi file and not the Windows one!
Last edited:
Thats what i thought. I also tried having the Windows EFI files on other drives as well as together with the OC stuff. Didn’t affect anything and i’d rather keep my OC EFI clean for easy Updates…
I have another theory now. I seem to remember having had issues with installing windows peviously and i noticed this strange “Updates” partition on my macOS Monterey Nvme drive. As i said my VMM flag is disabled and the only update available is for ventura which i don't want to do anyway. Can i just get rid of this partition somehow?
As said i seem to be able to boot windows if the nvme pcie controller is not installed but i also don’t have any issues booting macOS from it so i doubt it is an OC issue with my PCIe card in general
So it seems it might be a faulty “snapshot” i can see it in diskutility and its 0KB i can’t delete it and when i try to activate it finder crashes.
Any idea on how to fix this?
Maybe enable vmm for this to finish or something?
Mh even stranger in diskutility i can see the two apfs volumes for system and data of my monterey installation but the system partitionnis greyed out and it sais snapshot active?!
The presence of that volume is normal, and the possibility of the snapshot being faulty is another issue (which shouldn't affect Windows).
Ok but im sure something is weird with my macOS and i seem to remember having had this issue before and believe me it affected booting into windows.
When i open diskutility and look for my macOS Monterey it shows a greyed out macOS partition and a macOS - Data one. When i click on the greyed out one i see a message saying something snapshot aktive. When i rightclick the grayed out volume and say activate it. I can see a snapshot on the volume but i can’t delete it nor can i show it in the finder. Actually when i try to do anything with it finder starts freaking out and i will eventually be logged out of my account and back to my login screen. When i log back in the statusbar flickers and I’m thrown out again.
There is something f*d up for sure.
When i boot the recovery and perform a disk repair it checks that very snapshot but somehow finishes the check without doing anything about the snapshot
so i ended up deleting the whole macOS install and did a fresh install of Win11 on a SATA SSD (which worked before i reassembled my MacPro and put in the Nvme PCIe Card and the Titan Ridge). As cdf suspected that wasn't what was causing Win11 not to boot after following the steps in post#1.
I'm sorta burnt out now and sick of wasting my time.
No, he just wrote it: "The idea for placing it in a different EFI partition is to prevent Windows from replacing the OC BOOT folder with its own version during updates"
You wont need the “boot” folder of the microsoft EFI at all just the “microsoft” folder ideally on the EFI partition of your windows drive. OC will recognize it and show it in the bootpicker
In terms of functionality for Windows, it makes no difference, but using a different EFI partition for Windows is a good idea to mitigate BootROM damage.
When using the same EFI partition, the OC folder EFI/BOOT is likely to get replaced by the Windows one, and this is a very bad thing. Now, it might not be immediately obvious that this has happened, because with LauncherOption=Full, OC redirects its blessing to EFI/OC/OpenCore.efi. But contrary to EFI/BOOT/BOOTx64.efi, this path is not a standard one, so after so after an NVRAM reset (a real one outside of OC), if the OC version of BOOTx64.efi has been replaced by the Windows version, then it is possible for Windows to boot outside of OC, damaging the Mac Pro’s BootROM! You can check whether the BOOTx64.efi file is the right one by searching the file for the string “OpenCore”.
In addition to using a different EFI partition for Windows, another safety measure is to keep only the Microsoft folder (so that the only EFI/BOOT folder on any EFI partition is the OC one). Of course, the solution isn’t bulletproof, because Windows can still recreate the BOOT folder (though it shouldn’t overwrite the OC one if it uses a different EFI partition). Therefore, after any Windows update, it is also a good idea to go look for this folder on the Windows EFI partition and to delete it.
I hope this clarifies things a bit!
Right. I suppose that’s because they all use the OC EFI partition (maybe disk1s1 in your case)—look for a Microsoft or Grub folder there (grubless Linux is possible, but that’s another story!). Everything can still work in this case; you just have to keep on eye on that BOOT folder (as mentioned above).