Some people whose bootroms were corrupted (some of which could no longer boot) also had multiple MS signing certificates in their NVRAM from Win10 EFI installs. An absolute causal relationship between the two was never established (not to my knowledge anyway) but considering the cMP cannot utilize SecureBoot, MS should not be installing those certs in the first place. Installing in Legacy mode prevents that situation entirely.
But there are other reasons too. For one, Apple never sanctioned UEFI Windows installs on the CMP, whereas they do for later Macs which use UEFI-compliant firmware. They always intended for Windows to be installed in Legacy mode on this hardware. One example of this is that you cannot use the built-in Startup Disk preference to set an EFI Win10 install as bootable. If you do, the cMP will either throw an error or worse it will act as if it's setting it and then once you reboot you'll get stuck in the CSM boot, whereby you can't get to Windows nor macOS without a PRAM reset or option booting (which is not possible for most of us as of Mojave).
It seems to be the consensus here that TRIM indeed is in effect with Win10 installed in Legacy mode, and furthermore that any speed benefits of the SATA controller being in AHCI mode are minor at best. If you're interested, there was even a method posted here a while back of how to get AHCI mode working in a legacy install, although I believe it had some side effects like breaking sleep mode.
For most users who want to be able to easily switch back and forth between Win10 and Mojave using Apple's provided tools, it's easier and safer to just use Legacy mode. You of course are free to use UEFI mode on your own system if you've determined the potential speed advantage is worth the hassle and potential risks.
Thanks for the explanation. Every since Windows 8/8.1 (which I very rarely used as I disliked it) I have installed using EFI mode, and I have noted that Startup Disk in System Preferences do not work, but I have been used to that since I installed Windows that way. Also I know that the Boot Camp Control Panel in Windows will not work correctly when Boot to OS X is selected from the System Tray. I supposed I have just grown accustomed to these issues and have always used the Option button to select an alternate OS, and held down Ctrl to make it stick if I want to make it the default OS, and never had any issues. If I need to change the OS that the machine is booted into remotely (from OS X to Windows) I ssh into the machine and bless the Windows bootx64.efi file and restart, and it always will boot into Windows. Perhaps I am just used to the bugs, but I haven't encountered the corrupt firmware issue, however my machine has not upgraded its BootROM to anything beyond the one that supported APFS, and not the one that allows booting to NVMe SSDs. I also have a boot screen with a flashed GTX 980Ti, and am "stuck" at 10.13.6, and will be there for a while it we do not see a new web driver. I can't see the upgrade to 10.14 is worth purchasing a new video card and losing BTTM, etc. personally. I would be interested in those on a Mac Pro 5,1 running Mojave if they feel the upgrade is worth it.
Thanks!
BTW, I don't see any incentive to upgrade the beloved "cheese grater" that I bought in 2013 - Yes it was expensive when new, but it has been a rock solid workstation that I use more as a OS X/UNIX Workstation and it is such a stable platform that can run months on end without a reboot needed. I have the dual 3.06 Xeons, and upgraded to 128GB of RAM a long time ago. I guess the area I am lacking is the throughput on the disks, as I am using internal disks and external USB disks. A 10GbE card with a SAN connected would resolve much of the storage issues, and would provide good fault-tolerance and decent speed. I think I recall reading of an iSCSI initiator for OS X, but I have not used or tested it, but that would be something of interest. I am an vSphere/Exchange/Windows Server administrator, and people find it odd I prefer a Macintosh as a workstation, but the reliability of OS X and window management, and VMware Fusion Professional all work great together, and I have just grown to love OS X as a desktop OS. We can partly thank Windows 8/8.1 for that!
As a side note, I guess I am used to "unsupported" territory, and we all are there if we are running Windows 10 on the Mac Pro, since Apple never said it would run Windows 10. Mac Pro users tend to be power users and of course know better, so although EFI is/has been unsupported the life of the Mac Pro, the advantages it offered I felt outweighed the boot selection option from the respective installed OSs. If I am not mistaken, it was the first machine that Apple produced that would install any version of Windows in EFI mode, starting with Windows 8. I tried many times to install Windows 7 Enterprise x64 in EFI, but it did not detect the video card properly, and I never continued attempting. If the drivers were slipstreamed or an unattended file were included on the install media, it may successfully install and come up to the desktop, but I have not attempted this.
Last edited: