Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
How to: Boot Camp without a Boot Screen
- Thread starter MisterAndrew
- Start date
- Sort by reaction score
Here is my script for booting SIP disabled:
This script is for a single boot only. If you want permanent boot partition change remove '-nextonly'
This script only allows selection of 3 boot partitions. Somebody can help modifying it to more selection options.
Disk Layout:
If you want to disable SIP from within OSX without boot picker screen:
Code:
do shell script "sudo diskutil mount 'Recovery HD'" with administrator privileges
delay 2
display dialog "Select a startup disk" buttons ¬
{"BOOTCAMPSSD", "Recovery HD", "WIN10SSD"}
set bootVol to the button returned of the result as text
do shell script ¬
"bless -mount \"/Volumes/" & bootVol & "\" -setBoot -nextonly" with administrator privileges
do shell script ¬
"shutdown -r now" with administrator privilegesThis script is for a single boot only. If you want permanent boot partition change remove '-nextonly'
This script only allows selection of 3 boot partitions. Somebody can help modifying it to more selection options.
Disk Layout:
Code:
/dev/disk0 (external):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 512.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS MojaveSSD 511.1 GB disk0s2
3: Apple_Boot RECOVERY HD 650.0 MB disk0s3
/dev/disk1 (external):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 512.1 GB disk1
1: EFI EFI 894.8 MB disk1s1
2: Microsoft Reserved 16.8 MB disk1s2
3: Microsoft Basic Data WIN10SSD 509.1 GB disk1s3
4: Windows Recovery 2.1 GB disk1s4
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *120.0 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Microsoft Reserved 16.8 MB disk2s2
3: Microsoft Basic Data BOOTCAMPSSD 119.3 GB disk2s3
4: Windows Recovery 487.6 MB disk2s4
/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *240.1 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_HFS 3.1 KB disk3s2
3: Apple_HFS SierraSSD 239.2 GB disk3s3
4: Apple_Boot Recovery HD 650.0 MB disk3s4
/dev/disk4 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk4
1: EFI EFI 209.7 MB disk4s1
2: Apple_HFS SIERRA 999.3 GB disk4s2
3: Apple_Boot 650.0 MB disk4s3
/dev/disk5 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *250.0 GB disk5
1: EFI ESXi 4.2 MB disk5s1
2: Microsoft Basic Data 4.3 GB disk5s2
3: AA31E02A-400F-11DB-9590-000C2911D1B8 242.1 GB disk5s3
4: Microsoft Basic Data 262.1 MB disk5s5
5: Microsoft Basic Data 262.1 MB disk5s6
6: 9D275380-40AD-11DB-BF97-000C2911D1B8 115.3 MB disk5s7
7: Microsoft Basic Data 299.9 MB disk5s8
8: 9D275380-40AD-11DB-BF97-000C2911D1B8 2.7 GB disk5s9
/dev/disk6 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *5.0 TB disk6
1: EFI EFI 209.7 MB disk6s1
2: Apple_HFS Backup 5.0 TB disk6s2If you want to disable SIP from within OSX without boot picker screen:
Code:
sudo nvram "recovery-boot-mode=unused" && sudo reboot recoveryI'm currently running my Win10 SSD in an ICY DOCK 3.5:2.5 adapter in bay 3...no real issues with speed, even though I know the drive is capable of a lot more on SATA3.
Doesn't look like there's a straightforward way of getting Win10 to boot from a PCIe sled...I'll leave it like this I think.
If you look at my layout :I'm currently running my Win10 SSD in an ICY DOCK 3.5:2.5 adapter in bay 3...no real issues with speed, even though I know the drive is capable of a lot more on SATA3.
Doesn't look like there's a straightforward way of getting Win10 to boot from a PCIe sled...I'll leave it like this I think.
Code:
/dev/disk1 (external):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 512.1 GB disk1
1: EFI EFI 894.8 MB disk1s1
2: Microsoft Reserved 16.8 MB disk1s2
3: Microsoft Basic Data WIN10SSD 509.1 GB disk1s3
4: Windows Recovery 2.1 GB disk1s4This windows Partition is on an nVME attached to an adapter. You can see it is detected as external. I can boot to that Partition using my script.
The other drive:
Code:
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *120.0 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Microsoft Reserved 16.8 MB disk2s2
3: Microsoft Basic Data BOOTCAMPSSD 119.3 GB disk2s3
4: Windows Recovery 487.6 MB disk2s4May give it a shot one day. For now I'm just grateful everything works, and that I have Boot Camp 6.1 to switch between OSes.
I use Win10 mainly for Assetto Corsa (racing simulator) and Mojave for all else. Assetto mainly uses the drive while loading data prior to a race, and not so much during.
I use Win10 mainly for Assetto Corsa (racing simulator) and Mojave for all else. Assetto mainly uses the drive while loading data prior to a race, and not so much during.
I try to find the solution to install BootCamp 6.1 in Windows 10 Pro WITHOUT any iMacPro and old BC5.1 Win7 drivers. I do not like an idea to clog the system with "alien" drivers for nonexistent iMacPro hardware.
Still no success.
The installation process is as described in this tread, through Command Promt and msiexec /i bootcamp.msi code.
Tried to delete (or rename) all drivers from BootCamp 6.1 folder, installation goes with different warnings (it says there no files etc.), after reboot bootcamp icon appear in Windows but doesn't affect at all.
Tried to delete some drivers from BootCamp 6.1 (leaving in the BC folder only Apple drivers), no warnings during installation in this case, but BootCamp doesn't reboot to macOS, only reboot back to Windows.
Also the problem is that if i install Bootcamp without drivers, and got the issue i wrote above, and then install normally with all drivers, nothing changes anyway, it seems something corrupt the system permanently, and for the following experiments i must to reinstall clean Windows (or reset it).
P.S. configuration: MacPro 4.1>5.1, flashed GTX680 GPU, both macOS Mojave and Windows 10 Pro are together in ONE SSD (tray) - it was another fun (or sad) story how to clean install both systems where Mojave do not recognize GTX680 as Metal GPU upon USB stick installation (createinstalledia etc.) and there no way to create hybrid GPT/MBR disk for macOS and Windows without BootCamp assistant, that doesn't work in Mojave...
Still no success.
The installation process is as described in this tread, through Command Promt and msiexec /i bootcamp.msi code.
Tried to delete (or rename) all drivers from BootCamp 6.1 folder, installation goes with different warnings (it says there no files etc.), after reboot bootcamp icon appear in Windows but doesn't affect at all.
Tried to delete some drivers from BootCamp 6.1 (leaving in the BC folder only Apple drivers), no warnings during installation in this case, but BootCamp doesn't reboot to macOS, only reboot back to Windows.
Also the problem is that if i install Bootcamp without drivers, and got the issue i wrote above, and then install normally with all drivers, nothing changes anyway, it seems something corrupt the system permanently, and for the following experiments i must to reinstall clean Windows (or reset it).
P.S. configuration: MacPro 4.1>5.1, flashed GTX680 GPU, both macOS Mojave and Windows 10 Pro are together in ONE SSD (tray) - it was another fun (or sad) story how to clean install both systems where Mojave do not recognize GTX680 as Metal GPU upon USB stick installation (createinstalledia etc.) and there no way to create hybrid GPT/MBR disk for macOS and Windows without BootCamp assistant, that doesn't work in Mojave...
Last edited:
For some reason '-nextonly' option does not work in HS, but works in Mojave. I am not sure if it is my drive or it is common to all HS. With '-nextonly' in HS it just reboots back to HS.
Update: I guess there was a problem with my drive. It worked fine on another HS drive I had. So the script works with '-nextonly' or without it (permanent change)
Last edited:
It is a mix. The BOOTCAMP is a legacy Windows 7 (you don't see it in my original post as I installed it later). BOOTCAMPSSD is an EFI Windows 10 on my Sonnet Tempo SSD Pro Plus. The WIN10SSD is an EFI Windows on a NVME on a DT-120. I can boot to legacy or EFI Windows, Recovery etc. with the same script without issues except on the other SSD with HS on the Sonnet Tempo SSD Pro Plus where the '-nextonly' does not work. But it works on the internal HDD SIERRA (another High Sierra drive)
Last edited:
I'm just saying I needed to include -legacy in my scripts for legacy-BIOS reboots to work correctly. Your situation may be different.
I'm guessing you already know about the risks of using Win 10 EFI on cMP versus using legacy-BIOS.
I have a MATT card installed for my firmware source. This way I also preserve my original chip from exhaustion, which is common for these chips.
My I ask how you switch between Mojave and Windows 10? Can you use Boot Camp Control Panel in Windows to switch to Mojave and use Startup Disk in Mojave to switch to Windows?
I don't get why this doesn't work for me (on High Sierra and Windows 10) if I change the startup disk in Windows to MacOS the computer ignores it and even if I remove the drive that has Windows on it and only have the drive with MacOS connected the computer still gets me to "No bootable device -- insert boot disk an press any key".
How can it do that when I only have my drive with MacOS connected? :-/
Easiest way to get booted back to macOS is clear your NVRAM (hold down command-option-P-R on the keyboard until you hear 2 more boot chimes).
I got stuck in that same cycle when I had Win10 installed in UEFI mode and then tried to set the Bootcamp partition in System Preferences->Startup Disk. With Win10 in UEFI mode you can't use that method. You have to either use the boot picker if you have a GPU capable of showing it or you have to use a third party app, script or terminal command. Maybe someone else can comment on good solutions there as I have no experience with any of them.
I wanted to use the native methods to switch back and forth, so I reinstalled Win10 in CSM mode via h98's fine tutorial posted earlier in this thread. Native tools work perfectly now.
Hi trying also to get the mac installation on NVME recognized in Windows.
I tried the method from h9826790 in post #214
Being a Mac user since 1993, I have not much of a clou about windows.
I can see that the command prompt is something similar to the terminal in Mac OS, but I have no Idea what Im doing. or what it meands if there is a Error 2.
I runned brigadier-0.2.4, it downloads the ESD but then I get Error 2
it tries to do something with in this folder: c:\jenkins\workspace\brigadier\build\brigadier\out00-PYZ.pyz\subprocess", line 896, in _execute_child
I dont have any folder c/jenkins
I copied the adress and downloaded the ESD over the browser,
can I trigger the install also manually or will that screw the installation ?
Here is what the out put of the Prompt looks like.
Thanks a lot.
I tried the method from h9826790 in post #214
Being a Mac user since 1993, I have not much of a clou about windows.
I can see that the command prompt is something similar to the terminal in Mac OS, but I have no Idea what Im doing. or what it meands if there is a Error 2.
I runned brigadier-0.2.4, it downloads the ESD but then I get Error 2
it tries to do something with in this folder: c:\jenkins\workspace\brigadier\build\brigadier\out00-PYZ.pyz\subprocess", line 896, in _execute_child
I dont have any folder c/jenkins
I copied the adress and downloaded the ESD over the browser,
can I trigger the install also manually or will that screw the installation ?
Here is what the out put of the Prompt looks like.
Code:
Microsoft Windows [Version 10.0.17134.648]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\Marc>e:
E:\>brigadier -m iMacPro1,1
Using Mac model: iMacPro1,1.
Model supported in package distribution file at http://swcdn.apple.com/content/downloads/61/44/041-39663/pv8irhxi3gnzuuvhnkk75o80xdtfq5fixi/041-39663.English.dist.
Distribution 041-39663 supports the following models: iMacPro1,1.
Making directory E:\BootCamp-041-39663..
Fetching Boot Camp product at URL http://swcdn.apple.com/content/downloads/61/44/041-39663/pv8irhxi3gnzuuvhnkk75o80xdtfq5fixi/BootCampESD.pkg.
100.0% 521936896 / 521932124 bytes
100.4% 1662976 / 1655808 bytes
Downloaded 7-zip to c:\users\marc\appdata\local\temp\tmpfenfcn\7z1514-x64.msi.
We need to install 7-Zip..
7-Zip install returned exit code 1603.
Extracting...
Calling 7-Zip command: C:\Program Files\7-Zip\7z.exe e -oc:\users\marc\appdata\local\temp\bootcamp-unpack_rwj4wm -y c:\users\marc\appdata\local\temp\bootcamp-unpack_rwj4wm\BootCampESD.pkg
Traceback (most recent call last):
File "<string>", line 339, in <module>
File "<string>", line 296, in main
File "<string>", line 73, in sevenzipExtract
File "c:\jenkins\workspace\brigadier\build\brigadier\out00-PYZ.pyz\subprocess", line 493, in call
File "c:\jenkins\workspace\brigadier\build\brigadier\out00-PYZ.pyz\subprocess", line 679, in __init__
File "c:\jenkins\workspace\brigadier\build\brigadier\out00-PYZ.pyz\subprocess", line 896, in _execute_child
WindowsError: [Error 2] The system cannot find the file specified
E:\>Thanks a lot.
Thanks, but I now have Windows installed as legacy boot (not UEFI) and still doesn't work to use native tools to switch between MacOS and Windows. I know about NVRAM reset and that it's supposed to revert back to MacOS, but am pretty sure it doesn't help in my case (I had this problem before and even a NVRAM reset didn't get me back into MacOS). Also we have the problem that SIP gets turned on, which makes the ”one time Windows booting” using tools such as Boot Manager to stop working https://forums.macrumors.com/thread...native-in-the-status-bar-of-your-mac.2145374/
Oh, well....
If you have Windows 10 you have to install latest imacpro1,1 bootcamp software to get an option to boot back to Mojave. Windows 7 with bootcamp 5 does not recognize Mojave.
Background: Mojave is installed on a PCIe to SATA SSD, and Windows 10 is installed on an SSD in one of the four drive bays. (Bay 3 IIRC)
I followed the instructions to install Mac Pro 5,1 drivers and iMac Pro 1,1 Boot Camp (v6.1). Through Mojave I change to Windows via Startup Disk, and in Windows I change to Mojave via Boot Camp tools.
Realized my old 8800gt had a 128k rom, flashed it. Have boot acreens. Installed win10 in csm mode on ssd. I made a whole other thread with details but might be better to post here since this is up the alley but if you want more info yiu can chexk my thread, want to keep it short here.
Don't like thst its emulating pata with ssd. Would like to try running in efi mode.
Mac pro 3,1
Flashed 8800gt, 960gtx unflashed, 4x250gb hd in apple sw raid0
Had my hds in slots 1,2,3,4 but windows wont see the extra sata ports so I had to rig it so my bay 2 plug piece ismpulled out for the ssd and then routed power and sata cable under slot 2 for the drive. Works but I think efi mode could let me put it back stock.
Win10 on ssd, osx 10.13.latest on raid0.
I also see a lot of people using refind. What are the benefits to that on a real mac?
How does one install windows in efi mode?m
I have read about certificate issues in efi mode with 5,1, not sure if it affects my 3,1
Btw I don't care about being able to switch OS in control panels, I prefer holding option or having a boot manager.
Don't like thst its emulating pata with ssd. Would like to try running in efi mode.
Mac pro 3,1
Flashed 8800gt, 960gtx unflashed, 4x250gb hd in apple sw raid0
Had my hds in slots 1,2,3,4 but windows wont see the extra sata ports so I had to rig it so my bay 2 plug piece ismpulled out for the ssd and then routed power and sata cable under slot 2 for the drive. Works but I think efi mode could let me put it back stock.
Win10 on ssd, osx 10.13.latest on raid0.
I also see a lot of people using refind. What are the benefits to that on a real mac?
How does one install windows in efi mode?m
I have read about certificate issues in efi mode with 5,1, not sure if it affects my 3,1
Btw I don't care about being able to switch OS in control panels, I prefer holding option or having a boot manager.
That's exactly what I have done. The difference being that I have High Sierra still and not Mojave. Maybe that's why it doesn't work?
Hi again,
Mac Pro genuine 5.1 W3520 updated with a W3680
10.13.6 on PCI NVME
Windows 10 on spinner second DVD port
Trying to get Titan Ridge working.
Unfortunately following the description of h9826790, installing the 6.1 boot camp didn't work.
Error 2.
Since I really have no idea about Windows, I didn't want to screw up the installation and
tried it by downloading the installer from here and extracting the actual Bootcamp installer with pacifist.
Now I know it won't install. Message: this software is not for this machine.
Ok, so I understand more what h9826790 did. the problem is I still don't get it why it didn't work.
II have to say I already had a install of Win10 so I skipped the steps 1) to 7)
could that be the problem ?
Thanks for the help =)
NoLemon
Mac Pro genuine 5.1 W3520 updated with a W3680
10.13.6 on PCI NVME
Windows 10 on spinner second DVD port
Trying to get Titan Ridge working.
Unfortunately following the description of h9826790, installing the 6.1 boot camp didn't work.
Error 2.
Since I really have no idea about Windows, I didn't want to screw up the installation and
tried it by downloading the installer from here and extracting the actual Bootcamp installer with pacifist.
Now I know it won't install. Message: this software is not for this machine.
Ok, so I understand more what h9826790 did. the problem is I still don't get it why it didn't work.
II have to say I already had a install of Win10 so I skipped the steps 1) to 7)
could that be the problem ?
Thanks for the help =)
NoLemon
The only thing which comes in mind is that you didn't uninstall the 5.1 properly before installing the imacpro1,1 drivers. Uninstall boot camp through cmd and install the new one through cmd later on .
I have also High Sierra, but I don't even get it installed.
Are the steps 1 through 7 essential for it to work, or should it work if W10 already is installed ?
I will install to a sata ssd in the end, but for now I use a spinner for testing, in case I screw up.
Im pretty sure its a legacy install, I started the installer DVD with the C key.
Are the steps 1 through 7 essential for it to work, or should it work if W10 already is installed ?
I will install to a sata ssd in the end, but for now I use a spinner for testing, in case I screw up.
Im pretty sure its a legacy install, I started the installer DVD with the C key.
Last edited:
Finally found it out. There is a part missing in the description, or then the way I did it works too.
Regarding the restarting loop in to windows, it seems that the Mac behaves differently if there is a NVME blade. With HDMI we should get a boot screen, don't know about PC Cards though.
Thunderbolt works too now, the only thing missing would be two scripts, one in Windows, which at startup, changes the boot volume to Mac and a automator script which sets the boot volume back to Windows, then it would be perfect (as long as there is no hack for the titan ridge)
Regarding the restarting loop in to windows, it seems that the Mac behaves differently if there is a NVME blade. With HDMI we should get a boot screen, don't know about PC Cards though.
Thunderbolt works too now, the only thing missing would be two scripts, one in Windows, which at startup, changes the boot volume to Mac and a automator script which sets the boot volume back to Windows, then it would be perfect (as long as there is no hack for the titan ridge)