Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I'm affected by the same problem.. here's what I found:

The 2012 5,1 cMP has a chipset limitation.. they don't properly recognise anything over 2TB so what is needed to get around that is a boot-level patch in the EFI to be recognised. That patch interferes with large-volume support of APFS, so it has been removed.

There is no workaround other than to remove drives that are larger than 2TB from the system, reboot and see if bootcamp will start for you then. I haven't tried that myself yet.. if/when I do and it works I'll let you know.

Right now all you can do is go back to Hi-C or possibly go back to 2TB harddrives on yours system.

Just to close the loop on this removing the 6TB drives doesn't work. Basically the only way to run bootcamp on your cMP 5,1 is to keep HiC on the computer.

To get the newer bootcamp working (which is compatible with the latest Windows 10 updates) I had to start here:

 
  • Like
Reactions: 0134168
Nice. Gonna try later. I gave up with Windows 7 long time ago. Thnx.

Reading the article. Im gonna try in an ESATA III. SSD.
 
Last edited:
There we go
 

Attachments

  • 55F21E76-5F50-4A51-ACBB-0832D9D75056.jpeg
    55F21E76-5F50-4A51-ACBB-0832D9D75056.jpeg
    276.3 KB · Views: 132
  • C242A255-2557-434C-9ED1-B7D333259121.jpeg
    C242A255-2557-434C-9ED1-B7D333259121.jpeg
    47.8 KB · Views: 143
  • Like
Reactions: SystemHasFailed
I've been running Windows for my cMP for many years while it was supported form the Boot Camp Assistant. Then in 2017 things changed to prevent the cMP 4,1 from running Boot Camp. So I found a work around from YouTube that involved flashing the PRAM. During so with its required software provided by the YouTuber helped to get my 4,1 to run Boot Camp again. Since my system was taken from a 4,1 to 5,1 status. So I was able to update Boot Camp Assistant to change my partition I had years prior. Then as of 2018 the cMP 5,1 was also placed on the chopping block as like the prior cMP's before it. Which didn't concern me since I had already created a Boot Camp partition years ago. However after the update to Windows 1903 something gone wrong with the boot up after the upgrade. I ran into blue screen issues and the startup repair that Windows 10 has wasn't able to solve the issue. Which lead to me scraping the partition and using a SSD.

These are capable machines so I don't know why Apple thought it was necessary to prevent them from updating. But since seeing the new cMP introduced this year it's clear what Apple's intent was targeted towards. That said MacOS Majove is the last supported OS for the 5,1 cMP. The next MacOS coming later this year has new hardware requirements. Something not stricken as form the Developers Beta yet. Apple will purposely required the software to check for components to make sure that neither the old Macs nor any Hackintosh builds will be able to install the final release. I believe the T2 chip might me that wrench!

FYI, If you have a PC ONLY Graphics Card (non Apple Graphics card) installed in your cMac Pro you will NOT be able to see the Boot Menu by holding down the Option key at startup. However you can select from with in MacOS from the Start Disk menu. Getting back to MacOS is where things get complicated with a Non Apple Graphics card. Flashing the PRAM becomes the only option. And Apple doesn't plan to fix Boot Camp for the cMP. So people like myself decided to go all in with WindowsOS. Truth be told Windows 10 version 1903 included all of the drivers for my 2009 Mac Pro that has been software flashed to 5,1 status. I didn't have to install a thing. For my installation to a larger SSD I removed all the hard drives and SSDs I had inside my cMP. All except the one I planned to have Windows 10 installed. Prior to the removal I reformatted the hard drive to Fat32 (which is very important). After the install all worked well. Only thing I done was update AMD software that controlled my MSI ATI Radeon RX580. I haven't had any issues and it's been nearly a week.
how did you install Windows on that SSD? by usb or DVD? and how did you burn the Disk, on Mac or Windows?
 
Usb efi installs on the 5,1 are a very bad idea, unless bios is protected by open core, windows will write all
Kinds for stuff to bios, and brick it.
If not running opencore, do not install efi, install legacy mode, all info needed on all this is on this site....
I just used a win 10, dvd, cheep on eBay, and a blank ssd, very simple install, no bootcamp needed.
Windows found every driver I needed on its own, except the updated WiFi/Bluetooth card...that was a pain...
 
  • Like
Reactions: mahdif62
Just gonna chime in here because this was way more of a pain than I thought it would be.

I tried using a USB installer and a different SSD as an installer. Both ended up with errors similar to "Cannot install required files".

I ended up having to dig out my old USB DVD drive, go to the local Staples to buy some DL DVD-Rs and then used WizISO to burn the installer DVD.

Burning the files themselves would not boot and instead just gave me the flashing "?" folder. I'm sure there's a free way of writing a .iso as a bootable DVD but at that point, I was happy to pay the bill to get something working.
 
Just gonna chime in here because this was way more of a pain than I thought it would be.

I tried using a USB installer and a different SSD as an installer. Both ended up with errors similar to "Cannot install required files".

I ended up having to dig out my old USB DVD drive, go to the local Staples to buy some DL DVD-Rs and then used WizISO to burn the installer DVD.

Burning the files themselves would not boot and instead just gave me the flashing "?" folder. I'm sure there's a free way of writing a .iso as a bootable DVD but at that point, I was happy to pay the bill to get something working.
Imposible for me install windows on my Mac Pro 5.1. I tried several methods. Even, an installation booting perfect in my Mac Pro 3,1 dont get to boot.
 
Bootcamp Assistant doesn't support installing Windows 10 on a cMP 5,1 but it works flawlessly when done by option-booting the Windows installer from a DVD or USB drive.

Strongly recommend using the USB installer method as its EFI install boots Windows significantly faster than the BIOS emulation version the DVD installer will get you
Sorry, I know this is an old thread. I do have to clarify the following though as I'd like to install Win10 [classic] via BootCamp on my OpenCore cMP5,1 running Mojave:

  1. Are you saying that if I stick a Win10 DVD installer disc into my cMP5,1, OC will see the Win10 bootloader as an option?
  2. If [1] above is true, then can I install Win10 on an NTFS partioned SSD from the get-go, and then install BCA post-facto for driver support?
  3. How can I ensure I'm installing classic Win10 for BIOS support, and not UEFI when installing via a DVD installer?
My cMP 5,1 is running OC 066 and I don't want to bork the firmware sitting in SPI flash as I just recently reflashed with a never-booted ROM. The last thing I need is UEFI Windows writing to it.

Pinging @h9826790 for additional feedback.
 
Sorry, I know this is an old thread. I do have to clarify the following though as I'd like to install Win10 [classic] via BootCamp on my OpenCore cMP5,1 running Mojave:

  1. Are you saying that if I stick a Win10 DVD installer disc into my cMP5,1, OC will see the Win10 bootloader as an option?
  2. If [1] above is true, then can I install Win10 on an NTFS partioned SSD from the get-go, and then install BCA post-facto for driver support?
  3. How can I ensure I'm installing classic Win10 for BIOS support, and not UEFI when installing via a DVD installer?
My cMP 5,1 is running OC 066 and I don't want to bork the firmware sitting in SPI flash as I just recently reflashed with a never-booted ROM. The last thing I need is UEFI Windows writing to it.

Pinging @h9826790 for additional feedback.
Did you saw that the post is almost a year before the first beta of OC was released? ;)

OpenCore can't be used with Windows CSM/BIOS installs or BootCamp, you have to chain load it with another loader.
 
Did you saw that the post is almost a year before the first beta of OC was released? ;)

OpenCore can't be used with Windows CSM/BIOS installs or BootCamp, you have to chain load it with another loader.
Hi Alexandre. Thanks for clarifying. I'll follow up with @Dayo tomorrow. Now that I think about it, it seems to be more of question on initial boot picker rather than OC since RefindPlus is chain loading OC.

I know OC shouldn't have to do anything, much less write anything to BootROM for Windows 10 to load. I guess this falls upon RefindPlus settings to ensure MS doesn't start writing to the ROM once a boot picker gets loaded?
 
Last edited:
BTW, here's what I see when inserting a Win10 Pro OEM DVD into my cMP 5,1:
35a47456ab355def134683027ac5771b.jpg


Selecting 'Boot Fallback Boot Loader from EFISECTOR' results in the following:
a4225078e79f1dcbd5a8e68b80e4adbc.jpg


Along with:
cbb2356d43ad6624326758bb19bbb930.jpg


Pressing any key just brings me back to RFP boot picker, but this time with a blue screen instead of custom banner:
6aa280f6d417f97d243a9ce9331e7c08.jpg


So @Dayo, I can't install Win 10 via Mojave BOOTCAMP, nor will RFP allow me to boot the a Win10 installer DVD.

Thoughts?
 
BTW, here's what I see when inserting a Win10 Pro OEM DVD into my cMP 5,1:
35a47456ab355def134683027ac5771b.jpg


Selecting 'Boot Fallback Boot Loader from EFISECTOR' results in the following:
a4225078e79f1dcbd5a8e68b80e4adbc.jpg


Along with:
cbb2356d43ad6624326758bb19bbb930.jpg


Pressing any key just brings me back to RFP boot picker, but this time with a blue screen instead of custom banner:
6aa280f6d417f97d243a9ce9331e7c08.jpg


So @Dayo, I can't install Win 10 via Mojave BOOTCAMP, nor will RFP allow me to boot the a Win10 installer DVD.

Thoughts?
I was never able to install Legacy Windows through RP. You will be able to from the Apple boot Picker with the DVD. You may try rEFInd chainloaded from RP. I always succeeded with VirtualBox method.
 
  • Like
Reactions: amstel78
I was never able to install Legacy Windows through RP. You will be able to from the Apple boot Picker with the DVD. You may try rEFInd chainloaded from RP. I always succeeded with VirtualBox method.
Thanks for the tip. Will experiment further.
 
There is a video on youtube:

"HowTo": Bootcamp your (OCed) Mac (without using Bootcamp)

which works for installing Windows without bootcamp.

You have to use the "HeiDoc Download tool", instead of the "MS Media Creation Tool"
 
Last edited:
  • Like
Reactions: amstel78
BTW, here's what I see when inserting a Win10 Pro OEM DVD into my cMP 5,1:
35a47456ab355def134683027ac5771b.jpg


Selecting 'Boot Fallback Boot Loader from EFISECTOR' results in the following:
a4225078e79f1dcbd5a8e68b80e4adbc.jpg


Along with:
cbb2356d43ad6624326758bb19bbb930.jpg


Pressing any key just brings me back to RFP boot picker, but this time with a blue screen instead of custom banner:
6aa280f6d417f97d243a9ce9331e7c08.jpg


So @Dayo, I can't install Win 10 via Mojave BOOTCAMP, nor will RFP allow me to boot the a Win10 installer DVD.

Thoughts?

you can try remove every ssd / hdd but the empty ssd you want to install windows to.

avoid everything with the term efi in it.

fire up the mac, hold the c key and windows installer should boot from dvd.
 
  • Like
Reactions: amstel78
Thanks. Will give that a try after some other issues get sorted out. Seems a whole lot of us on Mojave lost App Store functionality a few days ago. Possibly due to the last security update...
 
Losing Apple Services can be a nvram full problem.

its time to dump your Firmware and check it.

 
Losing Apple Services can be a nvram full problem.

its time to dump your Firmware and check it.

Doubt that's the issue in my case. Just flashed a never-booted MP5,1 BootROM that tsialex made for me last week.

No, the App Store issue is more widespread and affects quite a few other Mojave users other than myself.
 
Ok, so that shouldnt be the issue.

Apple Services malfunction just happened to myself as I had a full 1st stream. After cleaning with a full nvram reset it was cured.

got a working nvram volume as I cleaned it and flashed a clean firmware recently.

guess it was for troubleshooting a bootloader but thats ok as I know the downsites and can do the hardware and firmware repairs.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.