Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Dayo

macrumors 68020
Original poster
Dec 21, 2018
2,318
1,307
PART 1 of 3

This is a guide to installing Windows 10 on Classic Mac Pros without the Boot Camp Assistant.
This is one of many ways to implement such a "Bare Metal" setup but is a straightforward method.

This guide is for installing Legacy Windows, as opposed to UEFI Windows, but can also be used for installing UEFI Windows with one change in the process (which will be pointed out).

UEFI Windows is now the orthodox installation setup but unlike Legacy Windows, usage, and even simply just starting the installer, comes with risks of damaging Classic Mac Pros. Users must note and mitigate these risks should they decide upon UEFI Windows. Please search the forum or create a separate thread for this if you prefer UEFI Windows.

An installed Windows 10 instance can apparently be upgraded to Version 11.
A link to a tool that apparently does this is provided at the end of the guide.
It may however be best to remain on Windows 10 until absolutely required.
If so, you may want to take a look at Windows 10 IoT Enterprise LTSC 2021.
This release of Windows 10 will receive security updates for 10 years (2031).

NOTE
This guide requires installing Legacy Windows on a separate disk to avoid the HybridMBR hack that the Boot Camp Assistant relies on. To install Legacy Windows and Mac OS on the same disk however, the HybridMBR hack must be applied instead. Follow these alternative instructions to manually apply the hack and to install Legacy Windows when done.

The idea is to start the installation on a VM, ensure the target disk is properly formatted, then finalise directly on a Mac.
  • Ensure a Pre-Boot Configuration Screen is Available
    • IMPORTANT: Required to install and handle the Multi-Boot arrangement.
      • If running a GPU that supports this, you can access the Pre-Boot Configuration Screen by pressing the OPTION key on restarting your Mac.
      • If you do not have such in place, try using MyBootMgr to set RefindPlus up for an equivalent screen.
  • Download and Install VirtualBox
    • IMPORTANT: VirtualBox does not ordinarily work on cMP as from v7.x.
      • You will therefore need VirtualBox v6.1.
      • Choose the "macOS / Intel hosts" variant.
    • Do not open VirtualBox from "Applications" after installing, or shut it down before continuing if you do.
  • Download the Windows 10 "ISO" File
    • This will represent a "CD/DVD" to be inserted into the Virtual Machine to start the installation.
      • USE THIS LINK for the General Availability Channel (GAC).
        • This provides ISO files for standard versions of Windows 10.
        • Access from Mac OS or Linux as required download options are not shown on Windows.
      • USE THIS LINK for the Long Term Support Channel (LTSC) if you have the required access credentials or USE THIS LINK to obtain an unlocked LTSC ISO file from the third party "Microsoft Activation Scripts (MAS)" site.
        • An unlocked x64 "MAS" ISO file is likely best for a cMP over the official one.
        • You will need the MAS scripts from the massgrave.dev site to activate later.
Launch Disk Utiity and choose Show All Devices under View in the top left corner of the window. Then, select a disk (whole disk, not just a volume on a disk) attached to one of the four native SATA Bays in your MacPro and format it by clicking Erase. NB: This will be wiped clean so ensure you move any important data out first. Also, note that the native SATA Bays are required to run Legacy Windows on Classic MacPro. UEFI Windows can be run from any available port/slot.

IMG_00.png

After Erase is clicked, you will get a drop down dialogue box as below:
IMG_01.png

Choose the same options as shown above, then click on Erase to format the disk.
Run Terminal once done, enter diskutil list, and note the Disk ID for "WIN_DISK" (See "3" below):
IMG_03.png


Return to Disk Utiity and unmount WIN_DISK:
IMG_04a.png



Run the following command in Terminal:
sudo VBoxManage internalcommands createrawvmdk -filename "${HOME}/Desktop/Win10.vmdk" -rawdisk /dev/disk??.
  • Make sure /dev/disk?? matches the Disk ID noted earlier.
  • Reconfirm the Disk ID if you have rebooted since you last checked as it can change between boots.
This creates a virtual hard disk for the Windows VM on your desktop (Win10.vmdk) that points to WIN_DISK, being created in Raw Disk Mode.

Unmount WIN_DISK from Disk Utiity again after, as it would have been mounted by the previous command:
IMG_04a.png

Your physical disk is now prepared and ready to be connected to a Windows VM.
Type and enter sudo virtualbox into Terminal to launch VirtualBox.
Remember not to launch directly from Applications but to use Terminal.
PS: Cannot recollect why this is required, but recollect I found it so.

Select New within VirtualBox:
IMG_07.png

Swtich to Expert Mode on the drop down box as the Virtual Machine needs finetuning:
IMG_08.png

In Expert Mode, adjust settings as shown:
  1. WIN10
  2. /Users/YOUR_USER_NAME/Virtualbox VMs
  3. Windows 10
  4. Leave at default setting. Will tweak later
  5. Select "use existing file".
  6. Click folder icon to select the file
IMG_09.png

You will get a dialogue as shown where you should click Add:
IMG_10.png

Navigate to your desktop and select the Win10.vmdk file created earlier.
Highlight this when returned to the dialogue box and click Choose.
IMG_11.png

Press Create to create a Windows VM linked to WIN_DISK on return to the Expert Mode dialogue.
IMG_12.png

CONTINUED BELOW...
 
Last edited:
PART 2 of 3

You will now configure the virtual machine and start it up to initiate the installation.

On creation of the virtual machine, select the instance and go to the Settings tab.
There, under Storage, you will note the Virtual SATA Port for a hard disk is connected to the VMK file but the port for the Virtual Optical Drive shows that the drive is empty.

To install Windows, a virtual installation CD/DVD must be loaded into the virtual optical drive of the virtual machine.
So, click on Storage:
IMG_13.png

To load the virtual CD/DVD:
  1. Select Storage
  2. Select the optical drive bay
  3. Click on the icon to load the virtual optical drive
IMG_14.png

Select Choose a disk file, navigate to your Windows 10 ISO file and select this:
IMG_15.png

This will insert the ISO file into the virtual optical bay:
IMG_16.png


Click on System
  1. Tweak the RAM allocation.
    • About 50% of available RAM is good as the virtual machine is to be deleted once done
  2. IMPORTANT: To install in Legacy Mode, ensure Enable EFI is NOT CHECKED
    • Legacy Mode is recommended for Classic Mac Pros.
    • Obviously check this if you want UEFI Windows.
      • Not tested myself but should work
  3. Click OK
IMG_18.png
Return to Disk Utility and unmount WIN_DISK again as it would have been mounted during the creation process.
It must be unmounted to boot the VM:

IMG_19a.png

Start the virtual machine to run the installation program from the virtual CD/DVD:
IMG_20.png

The VM will start the Windows installer:
IMG_21.png


Complete the initial config and proceed:
IMG_22.png

CONTINUED BELOW...
 
Last edited:
  • Like
Reactions: Juka_420
PART 3 of 3

You will now complete the first installation stage, including formating WIN_DISK for Windows.
You will stop the installation after the first stage and continue directly on your Mac.
The Virtual Windows Machine can then be deleted afterwards.

Start the installation and indicate that you do not have a Product Key (unless you do) and move to the next screen.
A product key can be added later:
IMG_24.png

Select the desired version of Windows.
The next two images show the LTSC and GAC outputs respectively:
IMG_26.png

IMG_25.png
Notes on versions:
  • The "N" variants are significantly de-bloated releases for the EU
  • The "IoT" LTSC option is available when activating Windows later

Accept the license when shown, then select the Custom option on the following screen (IMPORTANT)
IMG_27.png

You will then get a screen indicating Windows cannot be installed on WIN_DISK.
At this point, format the disk:
IMG_28.png

Proceed once formatted:
IMG_30.png

Keep an eye on the installation for when it gets to the Getting Finished step:
IMG_31.png

When it completes this installation step, the installer will issue a reboot on the Virtual Machine.
The reboot signal is issued after a 10-second countdown, which is shown by the Virtual Machine.
Prepare to shut the VM down by navigating to the menu item shown below (right click to display).
Only press Power Off when the countdown is running and do not let it get to the end.

IMG_32.png
Shut your Mac down after the VM Power Off and reboot into the "Windows" instance shown by your Pre-Boot Configuration screen to complete the installation by following the prompts displayed. You can access the screen by pressing the "OPTION" key on boot, if your GPU supports this, or use a third party tool such as RefindPlus, which can be set up using MyBootMgr

Those that use bluetooth connected peripherals, and such, may need to install drivers.
I have not needed extra drivers myself, perhaps because I keep things hardwired and have modest needs.

NB: When on the LTS channel and following the on-screen prompts to complete the installation, you will come to a page requiring signing into a Microsoft Enterprise account to proceed. Note that you can select an option on the page to use a domain instead. This allows proceeding with a username and password you define.

A useful post-installation step is to right click "C\:" drive in Windows, select "Properties" and add a label. The disk will then be displayed with this label in RefindPlus when it is set to load an NTFS filesystem driver (as done when an intent to use Windows is indicated when running MyBootMgr). Otherwise, a generic name such as "NTFS Volume" will be used.

NB: The LTS Channel ISO file installs the "regular" Enterprise version, which is supported with security updates for five years. To get the "IoT" version, supported with security updates for 10 years, "activate" the installed Windows version and enable the "IoT" option.





It is possible to get drivers from this site:

Alternatively, the Brigadier tool apparently works for getting and installing drivers when set to "iMacPro1,1".
Code:
brigadier -m iMacPro1,1

Another option, purely to get drivers, is to use the Boot Camp Assistant:
Distilled from the alternative "HybridMBR" based guide linked in Post 1​

Step 1: Download the Bootcamp Windows Support Software (in Mac OS)​

This download will contain the Windows drivers you will need to run Windows on your Mac. Allow the computer to do this for you via the Boot Camp Assistant application:

  1. Open Boot Camp Assistant from Applications -> Utilities
  2. Click continue at the introduction, you may see 2 or 3 options, unclick these options, we will not use them:
    bootcamp_support_download0.png
  3. Instead, from the Action menu, select Download Windows Support Software
    bootcamp_support_download1.png
  4. Select your Desktop or Downloads folder as the destination for the download
  5. Press Quit once you are done. The download is 1.35GB, drag it to a USB drive, best formatted as ExFAT, to use later when booted into Windows

Step 2: Install 'Bootcamp Windows Support Software' (in Windows)​

These drivers are installed as part of the Bootcamp Windows Support Software and will allow Windows to work with the Mac specific devices: WiFi, Graphics, External Monitors, Webcam, Bluetooth and Audio. The Bootcamp Windows Support Software should be on the USB drive you created earlier.

  1. Insert your USB drive
  2. Run WindowsSupport -> Bootcamp -> setup.exe.
  3. This will install all the required drivers and may also install 'BootCamp for Windows' which you may wish to uninstall immediately.





This tool apparently works for upgrading Windows 10 to 11, bypassing TPM and other requirements:
As noted previously however, it might be better to defer moving to Windows 11 on a Classic Mac Pro
 
Last edited:
I guess using a VM means you don't need a working DVD drive or to create a DVD disk or USB flash drive (not sure if USB stick works for legacy install?).

The instructions in the original post use an entire drive for Windows or limit the number of partitions to 3. Different instructions are required for using a separate partition of an existing disk that contains many other partitions:
- use macOS to create the new partition (make it a FAT partition)
- convert the disk to hybrid MBR/GPT with up to 3 partitions made visible to Windows (include the one you just created)
- make sure the MBR has legacy boot code
- mark the new partition as active in the MBR
- when installing Windows, format the new partition as NTFS before installing - never use Windows to create new partitions.

Does VBox work with Hybrid MBR/GPT disk?

For creating the partition and setting up the MBR (whether MBR only or MBR/GPT hybrid), I use iPartition.app. One of the GPT fdisk tools (gdisk or cgdisk) can probably do it also.

For Windows drivers, after installing Boot Camp drivers, I use Driver Genius 20 to make sure all the drivers are up to date. I don't think there's a Boot Camp driver that would be overwritten by this or that any overwritten Boot Camp driver would be needed.
 
Does VBox work with Hybrid MBR/GPT disk?
Yes it does. All you need to do is deselect EFI firmware, or for UEFI installation you have to select EFI.
If you want to install on the same disk you can use modified Bootcamp assistant which will create hybrid MBR partition.
 
plus help you boot back to Mac OS from Windows desktop.
You don't want to use Boot Camp control panel to boot back to macOS if you have a custom boot loader (rEFInd, OpenCore, or APFS Patch).

Boot Camp drivers are useful for Apple or LG UltraFine display and keyboard features, etc.
 
anyone can help me?
why Error created File VMDK?
 

Attachments

  • Screen Shot 2020-08-26 at 20.26.52.jpg
    Screen Shot 2020-08-26 at 20.26.52.jpg
    134.4 KB · Views: 475
Try sudo VBoxManage internalcommands createrawvmdk -filename "${HOME}/Desktop/Win10.vmdk" -rawdisk /dev/disk#
 
Try sudo VBoxManage internalcommands createrawvmdk -filename "${HOME}/Desktop/Win10.vmdk" -rawdisk /dev/disk#
success created bro, but error on virtualBOX
 

Attachments

  • Screen Shot 2020-08-26 at 20.48.59.jpg
    Screen Shot 2020-08-26 at 20.48.59.jpg
    61.3 KB · Views: 457
Spotted an error in the instructions.
You need to unmount the disk before creating the virtual disk. So please go back and redo.
No need to download the things again but probably best to reboot your computer first.

Delete the VMK file you currently have and also try to follow the guide exactly as written.
 
Spotted an error in the instructions.
You need to unmount the disk before creating the virtual disk. So please go back and redo.
No need to download the things again but probably best to reboot your computer first.

Delete the VMK file you currently have and also try to follow the guide exactly as written.
Thanks for respon brother
Now proccessing install windows error, what using windows version for support ??
 

Attachments

  • 2718AACB-1246-4B3D-BD13-2136C32A1B94.jpeg
    2718AACB-1246-4B3D-BD13-2136C32A1B94.jpeg
    403.4 KB · Views: 685
No Idea. Format the disk and restart from the top.
Remember to follow the instructions exactly.
 
Should not matter which Windows Version but go ahead.
 
i successfully install windows but windows 8, and i try to upddate to 10 so crash, and now im back to win8 , how to detect on OC6?
 
PART 3 of 3

At this point, you will initiate the first steps of installation and reformat the installation disk for Windows.
You will stop the installation after the first stage and continue directly on your Mac.
The Virtual Machine can then be deleted afterwards.

Start the Installation:


Indicate that you don't have a Product Key (Unless you do) and move to the next screen. A product key can be added later:


Select the desired version of Windows. You will be typically be better off selecting Windows 10 Home instead of Windows 10 Pro:


Accept the license:


IMPORTANT: Select the Custom option on the next screen


You will then be presented with a screen that says Windows cannot be installed on the selected drive when you select WIN_DISK. At this stage, Format the disk.


Once formatted, you can proceed:


The installation will start and you need to keep an eye on it for when it gets to the Getting Finished stage:


When it completes this installation stage, the installer will issue a reboot on the Virtual Machine.
You will need to intervene and power down the Virtual Machine to stop this reboot.
You will then need to physically reboot your Mac and continue the installation. Basically switch from using a Virtual Machine.

The Reboot call takes 10 seconds to be activated once made (there is a count down) so prepare to shut down the Virtual Machine by navigating to the menu item shown below (Right Click on the VM Instance to bring this up).
Only press Power Off when the installer is attempting to reboot the VM.

View attachment 944853
This is easy, just shut down your Mac after the VM power down and reboot into the Windows Disk to continue the installation by following the Windows prompts.

Nothing special needs to be done at this point but I use a wired keyboard/mouse but those that use bluetooth and various other stuff, you may need to install drivers.

The Brigadier tool apparently works very well with installing these drivers when set to IMacPro 1,1.
Code:
brigadier -m iMacPro1,1

I haven't needed it myself but that might be because I keep everything hard wired.
PART 3 of 3

At this point, you will initiate the first steps of installation and reformat the installation disk for Windows.
You will stop the installation after the first stage and continue directly on your Mac.
The Virtual Machine can then be deleted afterwards.

Start the Installation:


Indicate that you don't have a Product Key (Unless you do) and move to the next screen. A product key can be added later:


Select the desired version of Windows. You will be typically be better off selecting Windows 10 Home instead of Windows 10 Pro:


Accept the license:


IMPORTANT: Select the Custom option on the next screen


You will then be presented with a screen that says Windows cannot be installed on the selected drive when you select WIN_DISK. At this stage, Format the disk.


Once formatted, you can proceed:


The installation will start and you need to keep an eye on it for when it gets to the Getting Finished stage:


When it completes this installation stage, the installer will issue a reboot on the Virtual Machine.
You will need to intervene and power down the Virtual Machine to stop this reboot.
You will then need to physically reboot your Mac and continue the installation. Basically switch from using a Virtual Machine.

The Reboot call takes 10 seconds to be activated once made (there is a count down) so prepare to shut down the Virtual Machine by navigating to the menu item shown below (Right Click on the VM Instance to bring this up).
Only press Power Off when the installer is attempting to reboot the VM.

View attachment 944853
This is easy, just shut down your Mac after the VM power down and reboot into the Windows Disk to continue the installation by following the Windows prompts.

Nothing special needs to be done at this point but I use a wired keyboard/mouse but those that use bluetooth and various other stuff, you may need to install drivers.

The Brigadier tool apparently works very well with installing these drivers when set to IMacPro 1,1.
Code:
brigadier -m iMacPro1,1

I haven't needed it myself but that might be because I keep everything hard wired.
So within MacOS you can change the drive for booting, so here you need to change to drive to the windows drive I guess? Cause I have the RX580 and can't do it in the bios. Is that correct?
 
Sorry, no experience with Brigadier.
You might want to search for a relevant thread or post a question
 
Last edited:
  • Like
Reactions: Teachermark01
Sorry, no experience with Brigadier.
You might be want to search for a relevant thread or post a question
No problem at all, you helpt me big time with this information. Took me a long time (cursing) to fix this haha.

So this is amazing!
 
Get this error when I am trying to add the Win10.vmdk to VirtualBox, what can I do? Also getting an error running the command...

Kind regards,

Mark
 

Attachments

  • Schermafbeelding 2020-11-02 om 19.58.50.png
    Schermafbeelding 2020-11-02 om 19.58.50.png
    54.9 KB · Views: 229
  • Schermafbeelding 2020-11-02 om 20.01.32.png
    Schermafbeelding 2020-11-02 om 20.01.32.png
    46.5 KB · Views: 222
Follow the guide carefully and make sure the disk is unmounted whenever it says it should be.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.