How to: Boot Camp without a Boot Screen

[1151105]

OK, done!

Thanks for providing all the required info. This is my version of "how to do it".

1) Insert the Windows installation DVD into the super drive

nd have everything working as expected. e.g. Keyboard functions keys, Magic Mouse, BT 4.0, Wifi ac, USB 3.0, etc.

P.S. I am not sure if step 24 - 27 can be skipped or not. You may try, may safe you a minute for rebooting.

anybody else use brigadier?
why not just download from here: https://support.apple.com/downloads/macoscomponents

finally got iwndows installed, but maybe its too late to tackle the BC stuff...

 

[bookemdano]

anybody else use brigadier?
why not just download from here: https://support.apple.com/downloads/macoscomponents

finally got iwndows installed, but maybe its too late to tackle the BC stuff...

Most recent version on that page is from 2015. Brigadier (if you follow h9's directions) will get you version 6.1, which is the only one that can see APFS drives so you can use Boot Camp Control Panel to return to macOS.

 

[h9826790]

anybody else use brigadier?
why not just download from here: https://support.apple.com/downloads/macoscomponents

finally got iwndows installed, but maybe its too late to tackle the BC stuff...

Because Bootcamp 6.1 is not available at there. Or you can find the link?

 

[1151105]

6.1 is available here:
/https://digiex.net/threads/apple-wi...nload-applebcupdate-exe-april-1st-2016.14828/

and 5.1 is available here:
https://support.apple.com/downloads/macoscomponents

i followed h9's install method and it all installed fine, but i am getting this error in win bootcamp now:
"Could not locate the OS X boot volume"
this could be because i installed it on nvme... looking for a solution now.

 

[h9826790]

6.1 is available here:
/https://digiex.net/threads/apple-wi...nload-applebcupdate-exe-april-1st-2016.14828/

and 5.1 is available here:
https://support.apple.com/downloads/macoscomponents

i followed h9's install method and it all installed fine, but i am getting this error in win bootcamp now:
"Could not locate the OS X boot volume"
this could be because i installed it on nvme... looking for a solution now.

I have't really try to download from your link and compare the files. But from the text, it's not the iMac Pro's Bootcamp 6.1 package as per my guide. But just the normal Bootcamp 6 package for other Mac.

 

[1151105]

I have't really try to download from your link and compare the files. But from the text, it's not the iMac Pro's Bootcamp 6.1 package as per my guide. But just the normal Bootcamp 6 package for other Mac.

hahaha, i literally just noticed that!

maybe i will retry the 5.1 install and see if it works without the 6.1 as you mentioned in that post.
[doublepost=1543355091][/doublepost]

I have't really try to download from your link and compare the files. But from the text, it's not the iMac Pro's Bootcamp 6.1 package as per my guide. But just the normal Bootcamp 6 package for other Mac.

just uninstalled the 6.0 package which wasn't letting me restart to osx at all.
the 5.1 bootcamp in my win10 legacy install will reboot, but it goes straight back to windows.
does someone know how to search and pull from the sucatalog? where else to get 6.1?

 

[bookemdano]

hahaha, i literally just noticed that!

maybe i will retry the 5.1 install and see if it works without the 6.1 as you mentioned in that post.
[doublepost=1543355091][/doublepost]
just uninstalled the 6.0 package which wasn't letting me restart to osx at all.
the 5.1 bootcamp in my win10 legacy install will reboot, but it goes straight back to windows.
does someone know how to search and pull from the sucatalog? where else to get 6.1?

Man, no offense but I don't know why you won't just follow instructions. h9826790 provided perfectly easy to follow instructions for the entire process in this thread. Plenty of us have followed those same steps and have everything working great. I don't understand why you keep doing things a different way and then wonder why it's not working?

 

[1151105]

Man, no offense but I don't know why you won't just follow instructions. h9826790 provided perfectly easy to follow instructions for the entire process in this thread. Plenty of us have followed those same steps and have everything working great. I don't understand why you keep doing things a different way and then wonder why it's not working?

i followed them exactly and got different results... hence... troubleshooting. you think you're frustrated?

everything is working now. the cmd line was pausing brigadier when i clicked on the window.

+1 for h9's tut

 

[bookemdano]

i followed them exactly and got different results... hence... troubleshooting. you think you're frustrated?

I don't understand why you're installing old Boot Camp versions and questioning whether Brigadier is needed? h98's tutorial clearly says you need version 6.1 that is intended for the iMac Pro. No other version will work properly with Mojave. The only way to get it is to use brigadier. The instructions for exactly what to do are in h98's post.

 

[1151105]

I don't understand why you're installing old Boot Camp versions and questioning whether Brigadier is needed? h98's tutorial clearly says you need version 6.1 that is intended for the iMac Pro. No other version will work properly with Mojave. The only way to get it is to use brigadier. The instructions for exactly what to do are in h98's post.

i tried downloading them after brigadier wasn't working for me. would you just have given up?

these forums are here for troubleshooting. every single IT professional in the world uses forums just like these for this exact purpose. i don't know why you are hijacking this thread to try and berate me.

 

[setesousa]

OK, done!

Thanks for providing all the required info. This is my version of "how to do it".

1) Insert the Windows installation DVD into the super drive

2) Shutdown the Mac

3) Hold "C" to boot

4) Follow the on screen instruction until reach the "Where do you want to install Windows" step
View attachment 797517

5) "Delete" all the target SSD's partitions. In the above capture (downloaded from internet), you can see that there are 4 partitions for existing EFI mode Windows. Select each partition one by one, and click Delete. Be careful, do NOT remove other drive's partition. All partitions should be on the same drive. e.g. In the above example, all belongs to Drive 0. There is no requirement to remove any other hard drive from the cMP. But if you want to play safe, you can physically remove them between step 2 and 3 to avoid error.

Eventually will looks like this. No more partitions, but just a single large piece of Unallocated Space.
View attachment 797518

6) Click New. This will automatically create the correct and required partitions with all available space. For legacy installation, should be only two partitions automatically created.
View attachment 797527

7) Select the newly created partition, and continue the installation.

8) For Windows 10, the LAN line should work straight away after installation completed. So now, you can use Edge to access the internet.

9) Go to https://github.com/timsutton/brigadier/releases

10) Download brigadier.exe (0.2.4)

11) insert a USB drive (this is not mandatory, but just make the command prompt work easier)

12) Format the USB drive to FAT32

13) Copy brigadier.exe to the USB drive (assume it's the E drive)

14) Open Command Prompt (search CMD can find it)

15) type

e:

16) type

brigadier -m MacPro5,1

17) Once finished, rename the "Bootcampxxxxxxxxxx" folder to "Bootcamp5"

18 ) type

brigadier -m iMacPro1,1

19) Once finished, rename the "Bootcampxxxxxxxxxx" folder to "Bootcamp61"

20) search CMD again, but this time right click, and choose "run as admin"

21) type

e:

22) type

cd Bootcamp5/Bootcamp/Drivers/Apple

23) type

msiexec /i bootcamp.msi

24) After installation finished and reboot. Search CMD again, right click, and choose "run as admin"

25) type

e:

26) type

cd Bootcamp5/Bootcamp/Drivers/Apple

27) type

msiexec /x bootcamp.msi

This will NOT remove the drivers, but just the bootcamp apps

28) type

cd Bootcamp61/Bootcamp/Drivers/Apple

29) type

msiexec /i bootcamp.msi

30) Let it finish the installation and restart

So now, if you run the bootcamp apps. You should see something like this.
View attachment 797522
Language doesn't really matter, but you can see all the selections.

Those HFS+ High Sierra options will show the hard drive's name (e.g. 8T Backup)

Those APFS Mojave options will show as "Mac" above macOS.

From now on, you can use startup disk in Mojave to select Windows 10 (I renamed the SSD, usually it should shows BOOTCAMP, but not Win 10)
View attachment 797524

And of course, we can use bootcamp apps in Windows to select Mojave.

And have everything working as expected. e.g. Keyboard functions keys, Magic Mouse, BT 4.0, Wifi ac, USB 3.0, etc.

P.S. I am not sure if step 24 - 27 can be skipped or not. You may try, may safe you a minute for rebooting.

Thanks for the guide!
I followed your steps one by one and everything works fine except that my win10 (version 1809) can't see the HFS+ drives on my cMP. The BootCamp app runs great and I can switch back and forth from Win to macOS, but windows doesn't see the HFS+ drives. I tried to reinstall the Bootcamp 5 drivers but nothing changed. Anyone knows a workaround that don't compromise the safety of the data on the hfs+ drives (I read that you can manually try to mount the drives, but that can be dangerous and corrupt the data)
Thanks in advance

 

[h9826790]

Thanks for the guide!
I followed your steps one by one and everything works fine except that my win10 (version 1809) can't see the HFS+ drives on my cMP. The BootCamp app runs great and I can switch back and forth from Win to macOS, but windows doesn't see the HFS+ drives. I tried to reinstall the Bootcamp 5 drivers but nothing changed. Anyone knows a workaround that don't compromise the safety of the data on the hfs+ drives (I read that you can manually try to mount the drives, but that can be dangerous and corrupt the data)
Thanks in advance

You mean File Explorer cannot see the HFS+ drive?

That's normal. The Apple HFS+ driver breaks long time ago.

You can manually install some 3rd party HFS+ driver if you want to. But why?

I think it's better leave the HFS+ drives invisible in Windows. So that nothing can goes wrong.

If you want data only drives that can be share use in both macOS and Windows. Use ExFAT.

Or even use NAS etc as the "data bridge".

 

[marioliv66@]

Hello, since a few weeks I updated the Firmware of my MPc 4.1> 5.1 in version 140.0.0.0.0 and Mojave 10.14.1. No worries on the MacOS side. However next to that, I have an SSD on which I have installed Windows 10 for quite some time, but I do not remember how I installed it.

Since the update 140.0.0.0.0 and the problems that can be with windows 10, I hesitate to restart under W10. How do I know from Mac OS, if my SSD W10 is installed in EFI or not and what version of W10 is installed (1809?) Because W10 often updates automatically and the last time I opened it c was in October.

 

[h9826790]

Hello, since a few weeks I updated the Firmware of my MPc 4.1> 5.1 in version 140.0.0.0.0 and Mojave 10.14.1. No worries on the MacOS side. However next to that, I have an SSD on which I have installed Windows 10 for quite some time, but I do not remember how I installed it.

Since the update 140.0.0.0.0 and the problems that can be with windows 10, I hesitate to restart under W10. How do I know from Mac OS, if my SSD W10 is installed in EFI or not and what version of W10 is installed (1809?) Because W10 often updates automatically and the last time I opened it c was in October.

That's legacy Windows, not EFI

 

[marioliv66@]

That's legacy Windows, not EFI

So I can theoretically start on this w10 without problem?
I have another question, in the bootcamp 6.1 installation procedure on page 9 of this post. should i start from point 27 if i want to relocate the old bootcamp install on my w10 by that of the imac pro?

Thank’s

 

[h9826790]

So I can theoretically start on this w10 without problem?
I have another question, in the bootcamp 6.1 installation procedure on page 9 of this post. should i start from point 27 if i want to relocate the old bootcamp install on my w10 by that of the imac pro?

Thank’s

No, UNLESS you have the original (installed) bootcamp package INSTALLER on hand.

The command in step 27 ONLY works with the bootcamp installer that you already installed. AND you already navigate to that directory (e.g. step 26).

So, If you don't have that on hand. You will need to start from step 9, but skip step 21-24. (However, this still only works if your installed bootcamp version is the same as in step 16)

 

[marioliv66@]

Yes I already have a bootcamp (of 2014) installed on my w10

 

[Speedstar]

I was happy to find this tutorial but with Windows10Pro(64 Bit) 1809.17763.134 release maybe some things changed and need to be mentioned.

[ODE]brigadier -m MacPro5,1[/ODE]17) Once finished, rename the "Bootcampxxxxxxxxxx" folder to "Bootcamp5"

brigadier will download BootCamp 4 which was the last supported Version for win7 when you choose MacPro 5.1

23) type

msiexec /i bootcamp.msi

on windows 10 64bit you need to do msiexec /i bootcamp64.msi (in my case I started Setup.exe right klick as Admin worked too)
In Bootcamp Install-Folder I deleted Video Drivers I do not need, because setup installs both Ati/AMD and Nvidia.

24) After installation finished and reboot. Search CMD again, right click, and choose "run as admin"

After step 24 Your system will get destroyed after booting it will crash after AppleHFS.sys is loaded
usually max 20 sec after log in. You will not be able to do anything after log in...BSOD
That's why you need to rename or delete in
c:/windows/system32/drivers AppleHFS.sys
BEFORE REBOOTING...

This refers to all BootCamp Versions which are installed on Windows 1511 above
Starting with the anniversary update 1607 BootCamp versions below 6.1.xxxx will produce BSOD

24) After installation finished and reboot. Search CMD again, right click, and choose "run as admin"

27) type

msiexec /x bootcamp.msi

This will NOT remove the drivers, but just the bootcamp apps

I did not either reboot or uninstalled at step 24.
I had to search for InstallESD.PKG which was loaded by brigadier for MacPro1.1 in temporary directory
which is crashing during unpacking because it expects DMG file

I took the *xxxx.PKG file brigadier tried to unpack and crashed over to other Mac and unpacked it with pacifist
inside there was bootcamp.dmg opened this copied back to usb and
installed bootcamp.msi with right click on Win10 again. (I do not know a tool which uncompress pkg files under windows IsoBuster did it years ago)

now Bootcamp settings are not in WindowsStartBar/nextToClock infoIcons section anymore but only in SystemControl not in Settings !
and the new BootCamp Application does not show my RAID-HFS-HDs you have to decide
either APFS with bootcamp6.1 or choose maybe bootcamp5, or 6.0 to have the option to boot with HFS-Raid from Applet

Without the Drivers from BootCamp 4 (windows 10 pro 1809) on my MacPro5.1 did not have any bluetooth Wifi Ethernet and USB3 was not working after these procedure with different bootcamps all peripherals work.
In bootcamp applet I used combobox to activate F1 F2 etc PC Keys..




--------------------------------
Edit:

No I checked BootCamp facts again
I have no clue why brigadier chose the wrong versions

For the mac pro 2009 8.1 Windows drivers should work
BootCamp support software starts with 5.0.5033

( I don't know why in my case brigadier downloaded version 4.0)

 

[StrasRod]

OK, done!

Thanks for providing all the required info. This is my version of "how to do it".

1) Insert the Windows installation DVD into the super drive

2) Shutdown the Mac

3) Hold "C" to boot

Thank you ever so much to all the contributors of this this thread for providing such useful information!

I've been trying to update my old workhorse (12 core 2010 MacPro5,1) with a GTX 1080Ti and I also replaced the spinning disks with an NVME disk on the top PCIe slot. With OSX I'm limited to High Sierra because of the graphics card, but in any case the system is awesome.
For those who may be interested, I managed to compile the fast.ai Deep Learning libraries with this setup and run their course notebooks. Its wonderful to be able to do serious Machine Learning development in OSX while using all of my other utilities. The bootable NVME card runs at 1500MB/s in both read and write. This system completely outclasses my MacPro6,1 at work (apart from the fact that its slow to access external disks).

However, a couple of days ago I got greedy and tried to install Windows in a partition on the NVME disk, and ended up with the headache that the readers of this thread are aware of. For some reason the PRAM reset trick just kicks me back into Windows. At present, the only way I have to go between operating systems is by reinstalling my old ATI 5770 card, and pressing the option key on boot. But if I keep the old card in the machine, I cannot use the 1080Ti intensively (as I need to feed the ATI 5770).

I would like to follow the procedure outlined by h9826790 but before going ahead, I was wondering whether you think this procedure will work with an NVME boot disk that is partitioned between OSX and Windows. Alternatively, I could just add a SATA SSD drive to host Windows (which is not essential to me), but using the NVME would mean 7x better access times, so I would prefer to do that if possible.

Many thanks to all of you!

 

[bookemdano]

I was happy to find this tutorial but with Windows10Pro(64 Bit) 1809.17763.134 release maybe some things changed and need to be mentioned.



brigadier will download BootCamp 4 which was the last supported Version for win7 when you choose MacPro 5.1



on windows 10 64bit you need to do msiexec /i bootcamp64.msi (in my case I started Setup.exe right klick as Admin worked too)
In Bootcamp Install-Folder I deleted Video Drivers I do not need, because setup installs both Ati/AMD and Nvidia.



After step 24 Your system will get destroyed after booting it will crash after AppleHFS.sys is loaded
usually max 20 sec after log in. You will not be able to do anything after log in...
That's why you need to rename or delete in
c:/windows/system32/drivers AppleHFS.sys
BEFORE REBOOTING...






I did not either reboot or uninstalled at step 24.
I had to search for InstallESD.PKG which was loaded by brigadier for MacPro1.1 in temporary directory
which is crashing during unpacking because it expects DMG file

I took the *xxxx.PKG file brigadier tried to unpack and crashed over to other Mac and unpacked it with pacifist
inside there was bootcamp.dmg opened this copied back to usb and
installed bootcamp.msi with right click on Win10 again. (I do not know a tool which uncompress pkg files under windows IsoBuster did it years ago)

now Bootcamp settings are not in WindowsStartBar/nextToClock infoIcons section anymore but only in SystemControl not in Settings !
and the new BootCamp Application does not show my RAID-HFS-HDs you have to decide
either APFS with bootcamp6.1 or choose maybe bootcamp5, or 6.0 to have the option to boot with HFS-Raid from Applet

Without the Drivers from BootCamp 4 (windows 10 pro 1809) on my MacPro5.1 did not have any bluetooth Wifi Ethernet and USB3 was not working after these procedure with different bootcamps all peripherals work.
In bootcamp applet I used combobox to activate F1 F2 etc PC Keys..

FWIW I never installed the MacPro5,1 bootcamp package as I found none of its drivers were actually needed. Everything is either built-in, gets installed as part of the iMacPro1,1 bootcamp package, or comes in via Windows Update. To me it's a lot safer and easier to skip installing old Win7-era bootcamp stuff in Win10. The only thing that I didn't get a driver for was my updated 802.11ac/BT 4.0 airport card, but that wouldn't have been in the MacPro5,1 driver package either. I got the driver I needed for that from the 2015 iMac driver set.
[doublepost=1543601375][/doublepost]

Thank you ever so much to all the contributors of this this thread for providing such useful information!

I've been trying to update my old workhorse (12 core 2010 MacPro5,1) with a GTX 1080Ti and I also replaced the spinning disks with an NVME disk on the top PCIe slot. With OSX I'm limited to High Sierra because of the graphics card, but in any case the system is awesome.
For those who may be interested, I managed to compile the fast.ai Deep Learning libraries with this setup and run their course notebooks. Its wonderful to be able to do serious Machine Learning development in OSX while using all of my other utilities. The bootable NVME card runs at 1500MB/s in both read and write. This system completely outclasses my MacPro6,1 at work (apart from the fact that its slow to access external disks).

However, a couple of days ago I got greedy and tried to install Windows in a partition on the NVME disk, and ended up with the headache that the readers of this thread are aware of. For some reason the PRAM reset trick just kicks me back into Windows. At present, the only way I have to go between operating systems is by reinstalling my old ATI 5770 card, and pressing the option key on boot. But if I keep the old card in the machine, I cannot use the 1080Ti intensively (as I need to feed the ATI 5770).

I would like to follow the procedure outlined by h9826790 but before going ahead, I was wondering whether you think this procedure will work with an NVME boot disk that is partitioned between OSX and Windows. Alternatively, I could just add a SATA SSD drive to host Windows (which is not essential to me), but using the NVME would mean 7x better access times, so I would prefer to do that if possible.

Many thanks to all of you!

To be safe (and be able to switch back and forth using the built-in methods) you need to install Win10 in legacy BIOS/CSM mode.

But installed this way, you cannot install to an NVMe drive because the installer sees it as external. There are complicated workarounds but I would highly suggest just dedicating a normal SATA SSD to Windows. Much easier and safer too. Save NVMe for your macOS install.

 

[h9826790]

Thank you ever so much to all the contributors of this this thread for providing such useful information!

I've been trying to update my old workhorse (12 core 2010 MacPro5,1) with a GTX 1080Ti and I also replaced the spinning disks with an NVME disk on the top PCIe slot. With OSX I'm limited to High Sierra because of the graphics card, but in any case the system is awesome.
For those who may be interested, I managed to compile the fast.ai Deep Learning libraries with this setup and run their course notebooks. Its wonderful to be able to do serious Machine Learning development in OSX while using all of my other utilities. The bootable NVME card runs at 1500MB/s in both read and write. This system completely outclasses my MacPro6,1 at work (apart from the fact that its slow to access external disks).

However, a couple of days ago I got greedy and tried to install Windows in a partition on the NVME disk, and ended up with the headache that the readers of this thread are aware of. For some reason the PRAM reset trick just kicks me back into Windows. At present, the only way I have to go between operating systems is by reinstalling my old ATI 5770 card, and pressing the option key on boot. But if I keep the old card in the machine, I cannot use the 1080Ti intensively (as I need to feed the ATI 5770).

I would like to follow the procedure outlined by h9826790 but before going ahead, I was wondering whether you think this procedure will work with an NVME boot disk that is partitioned between OSX and Windows. Alternatively, I could just add a SATA SSD drive to host Windows (which is not essential to me), but using the NVME would mean 7x better access times, so I would prefer to do that if possible.

Many thanks to all of you!

I don't think it can work with NVMe.

And you won't get 7x better access time. You only get 7x faster sequential speed. Latency are pretty much the same on NVMe and SATA SSD. That's why your cMP won't boot 7x faster.

 

[mode11]

Got the Bootcamp 6,1 panel installed OK (thanks h9826790), but am having an issue on the Mac side. Startup Disk won't reboot into Windows 10 - says it can't bless the disk. Windows 10 and Mojave are on the same drivebay-mounted SATA SSD, both with latest updates. Can boot into Windows fine via Option at boot, or via Parallels. Anyone else had this issue?

 

[h9826790]

Got the Bootcamp 6,1 panel installed OK (thanks h9826790), but am having an issue on the Mac side. Startup Disk won't reboot into Windows 10 - says it can't bless the disk. Windows 10 and Mojave are on the same drivebay-mounted SATA SSD, both with latest updates. Can boot into Windows fine via Option at boot, or via Parallels. Anyone else had this issue?

Try BootChamp (with SIP disabled)

 

[mode11]

Thanks, I'll give it a go soon, but at the moment I'm trying to sort another (related) issue. I restored Mojave from a TM backup, which was painless enough and only took a couple of hours (500GB of stuff). This actually fixed the mid-boot delay with APFS + TRIM (yay!), but there's a new boot issue.

There's a longish delay before booting even starts, with a blank light-grey screen. I assume the Mac is looking for OSs to boot. When I go into Startup Disk to set macOS as the boot disk, I get a new bless message. This time it says "You can't change the startup disk to the selected disk. Running bless to place boot files failed".

I've tried resetting NVRAM but that didn't fix it. I ran Disk Utility on the Mac boot drive, but it had no issues. From reading around I get the impression bless has been deprecated, but I'd love to know of a terminal command or utility that could fix these issues.

 

[PianoPro]

Thanks, I'll give it a go soon, but at the moment I'm trying to sort another (related) issue. I restored Mojave from a TM backup, which was painless enough and only took a couple of hours (500GB of stuff). This actually fixed the mid-boot delay with APFS + TRIM (yay!), but there's a new boot issue.

There's a longish delay before booting even starts, with a blank light-grey screen. I assume the Mac is looking for OSs to boot. When I go into Startup Disk to set macOS as the boot disk, I get a new bless message. This time it says "You can't change the startup disk to the selected disk. Running bless to place boot files failed".

I've tried resetting NVRAM but that didn't fix it. I ran Disk Utility on the Mac boot drive, but it had no issues. From reading around I get the impression bless has been deprecated, but I'd love to know of a terminal command or utility that could fix these issues.

Bless works fine. I'm using bless scripts to boot to Win10, Mojave and High Sierra. It's much more convenient than using the Startup Disk Preference Pane because I include my password in the script and its available in the Menu bar. So that isn't your problem.

The Startup Disk preference pane works for Win10 legacy-BIOS booting, but not Win 10 EUFI booting when Win 10 is on a separate disk from Mac OS. I'm not sure what it can do when Win10 and a Mac OS are on the same disk. It sounds like your problems with Startup Disk are possibly related to where and what type of partitions are on your disk. Is there some reason you have Windows on the same disk as a Mac OS? It simplifies issues if you use separate disks. Are you sure you installed as legacy-BIOS and not somehow got a Win 10 UEFI boot installed?