As Far As I Know
Where can one find those drivers?
Go here "
https://github.com/minihub/bootcamp-intel-macs" then select the "Mac pro 6,1" at the very bottom of the list.
After your download then extract the files, go to “BootCamp-041-98143\BootCamp-041-98143\BootCamp\Drivers\AMD\AMDGraphics\Packages\Drivers\Display\WT6A_INF” folder and select the “C7186304.inf” “C7186304.cat” files, and the “B186909” folder. Do not select the other Driver files, as they are for “Windows Blue” witch is the prototype name for windows 8 (not windows 8.1).
The “C7186304” driver is made for Windows Vista, but it should not be a problem as Vista is older then Windows 7.
There is two drivers for Windows 8, most likely one of them was a Windows 7 driver, but got accidently named or configured for “Windows blue” (Again windows 8). The Msi file requires the “Catalyst” software to be installed, and that’s not possible on parallels for some reason, even if you did you have to have the gpus installed (As in connected to the os) for the Catalyst software to do anything. The bootcamp support software DOES install the drivers automatically, but only after you enter a computer name, password, and windows update option. Making it quite unhelpful (it also requires .net 4.5 to be installed, most likely something windows 8/8.1 already have installed)
So this means that the only way to install these drivers is BEFORE Windows gets installed, as in the .wim/.esd file. For some reason the .esd file (even when converted to .wim) that bobtheboney has supplied won’t accept ANY drivers to it. I just get a “Error 30” when trying to put drivers on it, even when im booted into windows 10 with its version of dism. That means we are going to have to manually replace the Efi files to get this to work. (Im not sure if I can upload the edited .boot64 and other efi files to mac rumors forums so you are going to have to extract them from the .wim (not the .esd, they are not in there) from the .iso that bobthepony supplies.).
To makes this more simple here is what to do step by step.
Step 1:
Create a standard Efi Windows 7 iso with Rufes (Make sure it’s a virgin/untouched iso, as in no drivers added to the .wim/.esd YET).
Step 2:
Unzip the Bootcamp drivers to the Usb disk to its root driver, where the “BootCamp” “$WinPEDriver$” and “AutoUnattend.xml” are at the root of the drive. ($WinPEDriver$ tells the Usb installer to load the drivers in this file along with Windows, AutoUnattend.xml is what starts the driver installer AFTER you enter your name and etc after Windows finalizes the install on the harddrive)
Step 3:
Use Dism to install the “C7186304” Drivers into boot.wim and install.wim (remember a .esd file is a compressed .wim file), MAKE SURE the “B186909” Folder is in the same folder as the other two files or it Dism WONT install the drivers. I did have success installing these drivers into a Windows 8 boot.wim file, but not the .esd that was supplied like I mentioned earlier ( I did not try a Windows 7 boot.wim nor have I tired see if the method I describe above installing the drivers into a virgin/untouched copy of Windows 7 yet (As I have been busy.).). (Windows 8 already is able to be seen by the Mac pro 2013, so im not sure if these drivers made a difference, but Dism said the drivers copied over without issues.).
Step 4. After the Usb Install is done, you are going to need to copy over that extracted bootx64.efi, bootmgr.efi and bootmgfw.efi to their respective locations inside the Efi partition ( You will need to boot back into Mac osx and mount the efi partition yourself (Ill edit this guide on the commands on how to do that later, I don’t have much time as of right now) The reason why is because you need that Uefi Class 3 Support in order to see anything, without those 3 files you are not going to be able to do anything as the machine will just crash/bootloop or freeze. (Something inserting I did notice that proves Windows 7 is running without graphics, after I had done all what I am about to write, I had let the Mac pro 2013 set for about 3 minuets I noticed the “scroll lock” and “num lock” keys were responding. Meaning that Windows 7 was running, just without graphics. (You could finish the install process with parallels, just wait for the error message of it trying to “upgrade” you bootcamp install and it will give you control of the bootcamp os in osx. This way we could install la script to run when the pc starts up to write what time it is to a file on the desktop, proving my theory about Windows 7 running correct)
Now, for what I had done to get that far. I installed the installation that bobthepony created (without the bootcamp utility, just launch the usb drive as a efi shell by holding down option when starting your mac, some keyboard like mine have the option and command keys mislabeled, so use one or the other if it does not pop up for you), but took the install.esd file and dumped it into a Windows 8 install Usb to see if the efi install world work (At this point I had already used a standard Windows 7 install.wim file to install Windows 7 while trying to get Uefi Seven to work (It did not due to no Intel hd graphics being on this Server grade Cpu, as mention by “pittance72” (A potential work around for Uefi Seven to work is to change the memory location in the uefiseven.efi file, as when you install a driver it has a memory address, but the only way I could think to obtain the address is to install Windows 8.1 first and try to get the address location there, but not a grantee as it might be different then the Windows 7 Driver, worth a shot although. See if there is a difference with Windows 8/8.1/10/11 for potential addresses.).
WARING! Don’t touch the “apple” boot entry as that is going to destroy your bootable install of osx, a bootable install disk can be used instead or a recovery partition if you don’t want to install mac osx for some reason, mostly to do with Veracrypt.
After swapping out those efi files, Windows 7 should work without issue. Not needing Uefi Seven or Vga shim installed. If it does work or not, please let me know or others know what happened and what step we can take to recreate the issues or success.
I would add more to this install guide, but its been over an hour and I need to rest. I would had some files and pictures for more clarity, but ill try and do that later this week, as I am tired. Good luck with install Windows 7, let us know if you do find a way to install it!