(Please note that I am going to upload images here later, but I have gotten really behind on making this guide so I am going to post the text part of the guide now)
This is a guide on how to install Windows 7 on a Mac pro 2013, the how to partition is very detailed. Below you will find a simplified install process that does not go into detail about much. Below that is a long explanation about the entire process on how to install Windows 7 and any errors you may encounter. You are going to need the tools/software below to completer this install.
Tools/Software needed:
1.Uefi Class 3 Modified Windows 7 Iso
2. Standard Windows 8.1 Iso (for tricking the osx bootcamp installer to make a usb drive, and/or for the mac pro 2013 to boot from the usb/dvd as uefi)
https://archive.org/details/win-8.1-english-x-64_202505
(Make sure to create “EI.cfg” in the sources folder of the Widnows 8.1 install disk otherwise the Windows 8.1 installer is not even going to let you install anything without a key. See below for how to make this file if your too lazy to look it up)
3.Bootcamp drivers/support software version 5.1.5640, manual link in case the bootcamp installer cant download them (just drag and drop to the root of the usb drive, or iso if your using a dvd)
https://support.apple.com/en-us/106432
4.Hard to find Amd D300/D500/D700 Windows 7 driver (This driver is having a error code 12 on Windows as of right now, I do not know how to fix this issue, read below for more info)
5.rEFIt, the custom efi boot loader (Yes I know its not longer maintained, but it has the older gray look of the original boot loader from Apple from 2013, and it was what worked for me. rEFInd Plus did not work for me btw)
https://refit.sourceforge.net/
6. Patience
Simplified install process:
1. Install rEFIt, if it does not show up the first time you restart, install it again then restart your pc two times without holding down the power button.
2. Create a Windows 8 Usb installer with bootcamp assistant, then rename the Windows 8 install.wim/esd/swm to install8.old (so it does not get used, don’t delete it incase you need to troubleshoot Windows 7 later). Place the Updated Class 3 install.esd/wim/swm from your Windows 7 iso to the created Windows 8 Usb install disk.
3. Make sure you have the bootcamp drivers installed to the Usb drive or the install is going to fail as you wont have keyboard or mouse support after the first install process. If the bootcanp assistant does not download them for you, you can add them yourself with the “5.1.5640” bootcamp drivers. If you are wanting to add the D700 drivers to the iso image or Usb disk, without having to use Dism or some other program like Ntlie. Just copy the .inf files with the folder(s) inside the location where the drivers are from into “$WinPEDriver$” folder at the root of the Usb/iso, as this add the drivers to the booted image right before Windows loaders from the installer. Its not part of the .wim/.esd./.swm file but it gets added to the install along with the booted preinstall environment. Again this does not fix the Error Code 12 driver issue.
4. After that just install Windows like normal, and don’t overwrite your Osx install partition. Remember that the 2nd step; of the install the Mouse and Keyboard do not work, this is normal. After the 3rd restart, the mouse and keyboard should work along with Usb devices.
Done, just 4 steps. If you are having a hard time install anything, read my detailed install process below.
This is the more detailed guide that I wrote first, it should give you information about any issues you may run into.
Leave a comment below if you want to ask a question for help.
The first thing you're going to need is rEFIit, an EFI boot manager that is custom-made for mostly for hackintoshs. I only found out that this boot manager is what enables Windows 7 to do correctly by accident, as I was using it to find a way to access the EFI shell on the Mac pro 2013, as rEFIt has its own EFI shell built in. Launching a standard Usb drive as a efi shell does not work, oh well.
For some strange reason, I had to install rEFIt once, then restart my computer (It did not show up, even at bootpicker) , then install it a second time for it to function. I am using OSX 10.9, so make sure to restart your computer twice with it installed. And if that doesn't work, just install it a second time and it should install correctly.
I have tried using refined plus, but it was to no avail. I did talk to the person who maintains it here on MacRumers forums (Dayo), and the person gave me some very interesting information about why it was unable to be of any use.
The second thing you were going to need is a specially modified Windows 7 iso and a standard release Windows 8.1 ISO file. The modified Windows 7 ISO file is linked here to archive.org and thanks to The Bob pony on X, I was successfully able to install Windows 7 on this machine. After downloading both the modified Windows 7 Uefi Class 3 iso, and the Windows 8.1 iso files, simply extract the install.esd file from the Widows 7 iso file, and place it inside the Windows 8.1 ISO (if it asks to override that’s ok, if it does not make sure to rename “install.wim” to “install.wim.old” or just delete it).
This can be done before or after using Boot Camp assistant, but doing it after is easier as you don't have to edit the ISO if you do end up editing it I recommend 7 zip if you are using Windows. If you're using Mac, you don't really need to worry as ISO files can be natively mounted. Make sure to delete the install.win/esd/swm that is already inside the Windows 8.1 installation Iso.
If Boot Camp assistant did not download the drivers automatically, you can download the Boot Camp assistant drivers manually, here is a link for the Mac Pro 2013 bootcamp drivers (Please note that these drivers do not have a compatible Windows 7 driver for the AMD 300/D500/D700 GPUs, here is a link for semi working Windows 7 drivers here. Please note that you are not going to get these drivers to work due to an error described later in the, due to error code 12).
After the USB drive is created, simply just restart your computer, or use the boot camp utility to install "Windows 8.1" and not create another USB installer disc. If you get some sort of error that Boot Camp assistant can't see your USB drive. It's fine. Just restart your computer and enter rEFI (There is more then one option for booting from Windows in rEFIt, only pick the one for efi/Uefi booting, not “leagecy” or rEFIt tells you it cant find a way to boot from legacy, same thing applies when you install Windows later). You can also use the native boot picker in order to install Windows 7 here, but it's not going to let you boot Windows 7 after it's installed to the hard drive, without refit.
Once you have booted into the Usb drive, you will notice that everything looks as if you're about to install Windows 8.1. If you had successfully replaced the install.wim/esd/swm go ahead with the installation as normal, as the installer will show you it is going to install Windows 7, not Windows 8.1. Look for the partition you created or Boot Camp assistant created and only format that partition. You could delete it but it's better to just use format instead.
Note that the Usb installer is not going to install any os unless you have a Windows 8.1 key. To bypass this create EI.cfg in the sources folder of your Usb install disk or iso file.
Here is how to create said file:
All EI.cfg is a .txt file with 4 lines of text in it (Just copy and paste these 4 lines of code with the empty line as well in notepad, save it as Ei.txt, then in Windows explorer rename it to “Ei.efg”. If you’re doing this on my just use text edit and follow the same steps):
[EditionID]
[Channel]
Retail
[VL]
0
(Something very interesting I found out, that some people might run into if you attempt to use disc utility to create the partition yourself and select the Windows NT/Fat 32 file system for the partition. When you get to the installation screen you are going to find out that the Windows installer will tell you that it can't be installed on a MBR hard disk, apparently the way the GPT/MBR hybrid disks are created on Macs is by simply creating a second partition as Windows Nt or fat 32. If this error occurs, you will need to go back to disc utility and format that partition to Exfat or HFS plus or Hfsj. Once Windows 7 is done installing, your computer is going to restart into another Windows installation screen, this time it should have a Windows 7 theme and your USB devices should not work, such as your mouse and keyboard, this is normal. Give it about 10 to 20 minutes and it should restart again as the process that is taking place is that window is installing all of the updated Windows updates and drivers. (You can tell if the computer is frozen if the three dots here are not cycling) (Also if your using a Oled screen or a Crt Monitor, make sure to turn down the brightness and contrast so you do not get burn in)
Once the installer restarts your computer a second time automatically, it will go back into Windows 7 install screen and about a minute or two; it should be done installing completely. You should be at the Window 7 set up screen. (Mouse and keyboard should be working at this step, please not that right after you put your name and pc name into the Install box the pc freezes for about 5 seconds, I don’t know why, but that happened to me so don’t freak out if it freezes for less than 30 seconds)
And voilà! Windows 7 is installed, but unfortunately there is one big catch with this installation.
Apparently there is some sort of issue with the Firepro D700 (I am using D700’s, I just assume this error would occur on D300’s, and D500’s as well)
There are Drivers for the Firepro D300/D500/D700 Gpus from this modified Iso file. These drivers have been labeled as “ATI/AMD Radeon HD 7970/Radeon R9 280X (TAHUTU XT/XTL)” for a different machine for some reason, I assume this is because the hardwired ids match for this other GPU. It could be that this driver was made for the Firepro D300/D500/D700 cards but I am not sure, so lets just use the official Drivers instead, that wont fix the error code 12, but it shows that the cards are the correct D-Series gpus you should have installed in your Mac pro 2013. So, the problem with this error code 12 is that the gpu responsible for all of the rendering to the HDMI port has its parents Pci device using the resources it needs. There is no normal way to see what resources it is requesting, but going into safe mode and looking there dhows you what resources it tryes to use. I also used HWinfo, and it shows me a bunch of stuff related to Pci lanes. (Impotent notice! I installed Windows 8.1 to see what resources the Gpus use there, and apparently they both have Irq’s being used by both of the drivers, in Windows 7, they both do not request any Irq’s. This could be the problem, but I am going off of the basis that these irq’s are not the issue, and this memory address being used by the parent Pci Chipset driver is. As the other Amd Gpu that does not sending Display info/Graphics to the Hdmi port is not showing any problems. I should note that the Pc does not even bother to try and render anything with this 2nd gpu. As even trying to Set a screensaver that is not the “blank” option, gives an error that a Direct3D gpu is required, suggesting that this Gpu is not used normally and only works when the other gpu works too, only for using crossfire I would assume.)
Apparently, this Pci Bus/Chipset driver is using the exact same memory address and I/O port that this Gpu is trying to use. The working Gpu does not have any ports being used or requested in device manger or Msinfo32. So the most likely culprit is this memory address is being used. This Pci Bus/Chipset driver causes the machine to no longer have work graphics as what the Chipset driver here is the communication for the PCI lane directly to the graphics card, same thing for the Pci bus driver. You can prove this as the other graphics card that does not push any graphics to the HDMI port uses a different PCI chip set driver if that driver gets disabled you will notice that the other graphics card now disappears from the device manager list. If you are unfortunate enough to disable the PCI chip set driver, or the Pci one, that is allowing the graphics card to push graphics through the HDMI port by accident, you can use Windows narrator to find your way around in the dark to re-enable it. Simply just press the Start key and then enter the device manager and Windows should talk back to you about what is selected. Using these exact same drivers on Windows 8.1 turns out to be completely successful. It is apparent that the issue here is not necessarily the drivers but rather Windows 7 itself. As the way all the memory allocation works in Windows 8.1 is that it is able to allocate memory for devices with conflict, or that the Chipset driver/Pci bus devieces are not using the memory ranges for said deviece. I should also note that device manager does not show any type of conflict whatsoever with any other devices even with the route PCI chip set driver, nor the Pci bus deviece. I have found out what the memory addresses that are needing to be used by going into safe mode and looking at the resources tab in device manager. I currently have found no way whatsoever to get this graphics card to work or even edit this memory address if you take a look here at the root PCI device Chip driver resources tab, apparently Windows had a feature to where you can manually select memory allocation. I'm not sure if this is a driver specific feature or if Windows has it disabled entirely. I currently have found a way to uncheck this box here although I may not be able to change the graphics card memory allocation as the parent PCI device here does work. I should be able to change its memory allocation in some way. I have found out by using treexy that there exists two different drivers for Windows 7 for the Firepro D300/D500/D700 Gpus. Unfortunately the website requires a monthly subscription in order to download files. I went ahead and bought a subscription to treexy, and no, the older drivers did not work, nor the other 10 drivers I tried using from Driver Fusion. I still got the same error code 12 issuse. Remember that Treexy does not own these driver files, and that AMD does, so linking them is perfectly legal. The only way I was able to even find out there was Windows 7 drivers for this GPU was to this website treexy, but then I went ahead and found the files on softpedia by cross-referencing the driver versions.
If anyone has any experience with this error code 12, or with creating graphics drivers, I could really use your help in finding a way to get these drivers to work directly on Windows 7. I also especially would like to try and contact someone who designed the Mac Pro 2013 or the Firepro D300/D500/D700 Gpus in the machine. I'm not sure if there is anyone here on the Mac Rumors forums that have worked on this machine, but if you did a summary or explanation about why Windows 7 was dropped from the machine would be very helpful.
So for the moment, Windows 7 does work on the Mac Pro 2013 and it is possible to install it natively. All that is missing right now is the graphics drivers due to this error code 12 . If anyone has any idea on what I should do to get these drivers to work, please let me know and I'll be more than happy to update this guide.
This is a guide on how to install Windows 7 on a Mac pro 2013, the how to partition is very detailed. Below you will find a simplified install process that does not go into detail about much. Below that is a long explanation about the entire process on how to install Windows 7 and any errors you may encounter. You are going to need the tools/software below to completer this install.
Tools/Software needed:
1.Uefi Class 3 Modified Windows 7 Iso
Windows 7 for UEFI Class 3 X 64 En US : TheBobPony : Free Download, Borrow, and Streaming : Internet Archive
This is a iso of Windows 7 updated for Uefi class 3 Machines. This iso allows newer pcs/laptops to install Wnndows 7 without Csm support. This iso was...
archive.org
2. Standard Windows 8.1 Iso (for tricking the osx bootcamp installer to make a usb drive, and/or for the mac pro 2013 to boot from the usb/dvd as uefi)
https://archive.org/details/win-8.1-english-x-64_202505
(Make sure to create “EI.cfg” in the sources folder of the Widnows 8.1 install disk otherwise the Windows 8.1 installer is not even going to let you install anything without a key. See below for how to make this file if your too lazy to look it up)
3.Bootcamp drivers/support software version 5.1.5640, manual link in case the bootcamp installer cant download them (just drag and drop to the root of the usb drive, or iso if your using a dvd)
https://support.apple.com/en-us/106432
4.Hard to find Amd D300/D500/D700 Windows 7 driver (This driver is having a error code 12 on Windows as of right now, I do not know how to fix this issue, read below for more info)
5.rEFIt, the custom efi boot loader (Yes I know its not longer maintained, but it has the older gray look of the original boot loader from Apple from 2013, and it was what worked for me. rEFInd Plus did not work for me btw)
https://refit.sourceforge.net/
6. Patience
Simplified install process:
1. Install rEFIt, if it does not show up the first time you restart, install it again then restart your pc two times without holding down the power button.
2. Create a Windows 8 Usb installer with bootcamp assistant, then rename the Windows 8 install.wim/esd/swm to install8.old (so it does not get used, don’t delete it incase you need to troubleshoot Windows 7 later). Place the Updated Class 3 install.esd/wim/swm from your Windows 7 iso to the created Windows 8 Usb install disk.
3. Make sure you have the bootcamp drivers installed to the Usb drive or the install is going to fail as you wont have keyboard or mouse support after the first install process. If the bootcanp assistant does not download them for you, you can add them yourself with the “5.1.5640” bootcamp drivers. If you are wanting to add the D700 drivers to the iso image or Usb disk, without having to use Dism or some other program like Ntlie. Just copy the .inf files with the folder(s) inside the location where the drivers are from into “$WinPEDriver$” folder at the root of the Usb/iso, as this add the drivers to the booted image right before Windows loaders from the installer. Its not part of the .wim/.esd./.swm file but it gets added to the install along with the booted preinstall environment. Again this does not fix the Error Code 12 driver issue.
4. After that just install Windows like normal, and don’t overwrite your Osx install partition. Remember that the 2nd step; of the install the Mouse and Keyboard do not work, this is normal. After the 3rd restart, the mouse and keyboard should work along with Usb devices.
Done, just 4 steps. If you are having a hard time install anything, read my detailed install process below.
This is the more detailed guide that I wrote first, it should give you information about any issues you may run into.
Leave a comment below if you want to ask a question for help.
The first thing you're going to need is rEFIit, an EFI boot manager that is custom-made for mostly for hackintoshs. I only found out that this boot manager is what enables Windows 7 to do correctly by accident, as I was using it to find a way to access the EFI shell on the Mac pro 2013, as rEFIt has its own EFI shell built in. Launching a standard Usb drive as a efi shell does not work, oh well.
For some strange reason, I had to install rEFIt once, then restart my computer (It did not show up, even at bootpicker) , then install it a second time for it to function. I am using OSX 10.9, so make sure to restart your computer twice with it installed. And if that doesn't work, just install it a second time and it should install correctly.
I have tried using refined plus, but it was to no avail. I did talk to the person who maintains it here on MacRumers forums (Dayo), and the person gave me some very interesting information about why it was unable to be of any use.
The second thing you were going to need is a specially modified Windows 7 iso and a standard release Windows 8.1 ISO file. The modified Windows 7 ISO file is linked here to archive.org and thanks to The Bob pony on X, I was successfully able to install Windows 7 on this machine. After downloading both the modified Windows 7 Uefi Class 3 iso, and the Windows 8.1 iso files, simply extract the install.esd file from the Widows 7 iso file, and place it inside the Windows 8.1 ISO (if it asks to override that’s ok, if it does not make sure to rename “install.wim” to “install.wim.old” or just delete it).
This can be done before or after using Boot Camp assistant, but doing it after is easier as you don't have to edit the ISO if you do end up editing it I recommend 7 zip if you are using Windows. If you're using Mac, you don't really need to worry as ISO files can be natively mounted. Make sure to delete the install.win/esd/swm that is already inside the Windows 8.1 installation Iso.
If Boot Camp assistant did not download the drivers automatically, you can download the Boot Camp assistant drivers manually, here is a link for the Mac Pro 2013 bootcamp drivers (Please note that these drivers do not have a compatible Windows 7 driver for the AMD 300/D500/D700 GPUs, here is a link for semi working Windows 7 drivers here. Please note that you are not going to get these drivers to work due to an error described later in the, due to error code 12).
After the USB drive is created, simply just restart your computer, or use the boot camp utility to install "Windows 8.1" and not create another USB installer disc. If you get some sort of error that Boot Camp assistant can't see your USB drive. It's fine. Just restart your computer and enter rEFI (There is more then one option for booting from Windows in rEFIt, only pick the one for efi/Uefi booting, not “leagecy” or rEFIt tells you it cant find a way to boot from legacy, same thing applies when you install Windows later). You can also use the native boot picker in order to install Windows 7 here, but it's not going to let you boot Windows 7 after it's installed to the hard drive, without refit.
Once you have booted into the Usb drive, you will notice that everything looks as if you're about to install Windows 8.1. If you had successfully replaced the install.wim/esd/swm go ahead with the installation as normal, as the installer will show you it is going to install Windows 7, not Windows 8.1. Look for the partition you created or Boot Camp assistant created and only format that partition. You could delete it but it's better to just use format instead.
Note that the Usb installer is not going to install any os unless you have a Windows 8.1 key. To bypass this create EI.cfg in the sources folder of your Usb install disk or iso file.
Here is how to create said file:
All EI.cfg is a .txt file with 4 lines of text in it (Just copy and paste these 4 lines of code with the empty line as well in notepad, save it as Ei.txt, then in Windows explorer rename it to “Ei.efg”. If you’re doing this on my just use text edit and follow the same steps):
[EditionID]
[Channel]
Retail
[VL]
0
(Something very interesting I found out, that some people might run into if you attempt to use disc utility to create the partition yourself and select the Windows NT/Fat 32 file system for the partition. When you get to the installation screen you are going to find out that the Windows installer will tell you that it can't be installed on a MBR hard disk, apparently the way the GPT/MBR hybrid disks are created on Macs is by simply creating a second partition as Windows Nt or fat 32. If this error occurs, you will need to go back to disc utility and format that partition to Exfat or HFS plus or Hfsj. Once Windows 7 is done installing, your computer is going to restart into another Windows installation screen, this time it should have a Windows 7 theme and your USB devices should not work, such as your mouse and keyboard, this is normal. Give it about 10 to 20 minutes and it should restart again as the process that is taking place is that window is installing all of the updated Windows updates and drivers. (You can tell if the computer is frozen if the three dots here are not cycling) (Also if your using a Oled screen or a Crt Monitor, make sure to turn down the brightness and contrast so you do not get burn in)
Once the installer restarts your computer a second time automatically, it will go back into Windows 7 install screen and about a minute or two; it should be done installing completely. You should be at the Window 7 set up screen. (Mouse and keyboard should be working at this step, please not that right after you put your name and pc name into the Install box the pc freezes for about 5 seconds, I don’t know why, but that happened to me so don’t freak out if it freezes for less than 30 seconds)
And voilà! Windows 7 is installed, but unfortunately there is one big catch with this installation.
Apparently there is some sort of issue with the Firepro D700 (I am using D700’s, I just assume this error would occur on D300’s, and D500’s as well)
There are Drivers for the Firepro D300/D500/D700 Gpus from this modified Iso file. These drivers have been labeled as “ATI/AMD Radeon HD 7970/Radeon R9 280X (TAHUTU XT/XTL)” for a different machine for some reason, I assume this is because the hardwired ids match for this other GPU. It could be that this driver was made for the Firepro D300/D500/D700 cards but I am not sure, so lets just use the official Drivers instead, that wont fix the error code 12, but it shows that the cards are the correct D-Series gpus you should have installed in your Mac pro 2013. So, the problem with this error code 12 is that the gpu responsible for all of the rendering to the HDMI port has its parents Pci device using the resources it needs. There is no normal way to see what resources it is requesting, but going into safe mode and looking there dhows you what resources it tryes to use. I also used HWinfo, and it shows me a bunch of stuff related to Pci lanes. (Impotent notice! I installed Windows 8.1 to see what resources the Gpus use there, and apparently they both have Irq’s being used by both of the drivers, in Windows 7, they both do not request any Irq’s. This could be the problem, but I am going off of the basis that these irq’s are not the issue, and this memory address being used by the parent Pci Chipset driver is. As the other Amd Gpu that does not sending Display info/Graphics to the Hdmi port is not showing any problems. I should note that the Pc does not even bother to try and render anything with this 2nd gpu. As even trying to Set a screensaver that is not the “blank” option, gives an error that a Direct3D gpu is required, suggesting that this Gpu is not used normally and only works when the other gpu works too, only for using crossfire I would assume.)
Apparently, this Pci Bus/Chipset driver is using the exact same memory address and I/O port that this Gpu is trying to use. The working Gpu does not have any ports being used or requested in device manger or Msinfo32. So the most likely culprit is this memory address is being used. This Pci Bus/Chipset driver causes the machine to no longer have work graphics as what the Chipset driver here is the communication for the PCI lane directly to the graphics card, same thing for the Pci bus driver. You can prove this as the other graphics card that does not push any graphics to the HDMI port uses a different PCI chip set driver if that driver gets disabled you will notice that the other graphics card now disappears from the device manager list. If you are unfortunate enough to disable the PCI chip set driver, or the Pci one, that is allowing the graphics card to push graphics through the HDMI port by accident, you can use Windows narrator to find your way around in the dark to re-enable it. Simply just press the Start key and then enter the device manager and Windows should talk back to you about what is selected. Using these exact same drivers on Windows 8.1 turns out to be completely successful. It is apparent that the issue here is not necessarily the drivers but rather Windows 7 itself. As the way all the memory allocation works in Windows 8.1 is that it is able to allocate memory for devices with conflict, or that the Chipset driver/Pci bus devieces are not using the memory ranges for said deviece. I should also note that device manager does not show any type of conflict whatsoever with any other devices even with the route PCI chip set driver, nor the Pci bus deviece. I have found out what the memory addresses that are needing to be used by going into safe mode and looking at the resources tab in device manager. I currently have found no way whatsoever to get this graphics card to work or even edit this memory address if you take a look here at the root PCI device Chip driver resources tab, apparently Windows had a feature to where you can manually select memory allocation. I'm not sure if this is a driver specific feature or if Windows has it disabled entirely. I currently have found a way to uncheck this box here although I may not be able to change the graphics card memory allocation as the parent PCI device here does work. I should be able to change its memory allocation in some way. I have found out by using treexy that there exists two different drivers for Windows 7 for the Firepro D300/D500/D700 Gpus. Unfortunately the website requires a monthly subscription in order to download files. I went ahead and bought a subscription to treexy, and no, the older drivers did not work, nor the other 10 drivers I tried using from Driver Fusion. I still got the same error code 12 issuse. Remember that Treexy does not own these driver files, and that AMD does, so linking them is perfectly legal. The only way I was able to even find out there was Windows 7 drivers for this GPU was to this website treexy, but then I went ahead and found the files on softpedia by cross-referencing the driver versions.
If anyone has any experience with this error code 12, or with creating graphics drivers, I could really use your help in finding a way to get these drivers to work directly on Windows 7. I also especially would like to try and contact someone who designed the Mac Pro 2013 or the Firepro D300/D500/D700 Gpus in the machine. I'm not sure if there is anyone here on the Mac Rumors forums that have worked on this machine, but if you did a summary or explanation about why Windows 7 was dropped from the machine would be very helpful.
So for the moment, Windows 7 does work on the Mac Pro 2013 and it is possible to install it natively. All that is missing right now is the graphics drivers due to this error code 12 . If anyone has any idea on what I should do to get these drivers to work, please let me know and I'll be more than happy to update this guide.
Last edited:
