Hey everyone. Quick question for the informed: does upgrading to High Sierra cause any issues with an existing Boot Camp partition? I really do not want to go through the hassle of trying to install Windows again. Thanks.
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.
Upgrading to High Sierra with Boot Camp
- Thread starter ceparker27
- Start date
- Sort by reaction score
My Windows 10 x64 install still exists and functions, however the Boot Camp utility in Windows no longer detects the macOS partition. To reboot into macOS I have to hold the option key when rebooting and then select "Macintosh HD". After entering macOS I have to go to "System Preferences" -> "Startup Disk" and select "Macintosh HD" if I want it to continue starting/rebooting into macOS.
This is using a mid 2015 MacBook Pro 11,5.
This is using a mid 2015 MacBook Pro 11,5.
Thank you for the info. Existing and functioning was my biggest concern. Not that I have to boot often to Windows but it's very important when I do. Is that System Preferences fix a one-time thing? Or do you have to go back and readjust that every time you boot into Windows?
If you use "System Preferences" -> "Startup Disk" to normally choose BOOTCAMP when restarting to Windows, you would need the option key method to return to macOS and reset the default boot partition to "Macintosh HD". It seems Apple needs to update the Boot Camp Utility in Windows so it recognizes the new APFS "Macintosh HD" boot partition as a selectable choice.
Can't speak for existing partitions, but I created a BootCamp partition after installing High Sierra with no problems (on an APFS SSD).
But as mentioned, the only way I can currently switch from Windows 10 to MacOS is by holding down the Option key during reboot.
But as mentioned, the only way I can currently switch from Windows 10 to MacOS is by holding down the Option key during reboot.
BootChamp with SIP disabled may be the solution. I have't try it yet, my cMP will encoding video at this moment. May able to try it in next few days.
I am wondering if I were to keep a second copy of Sierra or High Sierra on an HFS+ rotating drive, I could select that drive from the Boot Camp utility in Windows, then after booting into that select the primary APFS SSD from System Preferences > Startup Disk. The two step-process would be a pain, but would not require disabling SIP.
Boot into recovery partition to pick your next boot drive may work as well (if for any reason you prefer to keep SIP enable). And if you have a fast SSD, this option will be much faster than boot to HDD Sierra / HS. Of course, an OOTB GPU is required (non flashed PC GPU is fine).
Logically if you sierra installed on another drive it would be possible i think to do a two step reboot. I myself have another disk with Sierra but I counted to use this one to test High Sierra for some time but suddenly it puts everything into question. Would it be possible to have the manipulation to disable and reactivate the SIP, in case?
I just blew away my Boot Camp installation last night to fix the little "Reboot to macOS" issue. Unfortunately, I hadn't seen this thread yet and didn't know others were having the same issue. Stuck with having to hold down the Option key to get back into macOS. This is a minor annoyance, but a drag nonetheless. Also, macOS no longer correctly report the amount of free storage on the BOOTCAMP partition.
Bit of a snag when re-installing Windows, too. Microsoft recommends Mac users to install Anniversary Update and then update to Creators Update via Windows Update. Problem there is that Windows will run through the Creators Update immediately upon first log in, and you can easily miss the prompt to install the usual Boot Camp Software at that time. I didn't see the installation prompt for that until the update finished installing, and had to manually download the files from macOS, format a USB drive in ExFat, and install that way.
Bit of a snag when re-installing Windows, too. Microsoft recommends Mac users to install Anniversary Update and then update to Creators Update via Windows Update. Problem there is that Windows will run through the Creators Update immediately upon first log in, and you can easily miss the prompt to install the usual Boot Camp Software at that time. I didn't see the installation prompt for that until the update finished installing, and had to manually download the files from macOS, format a USB drive in ExFat, and install that way.
Last edited:
So, I have a (Late 2014) Mac Mini with Bootcamp partition, when I upgraded to High Sierra I could only boot into Windows, the progress bar getting into OSX stalled at 100%. Would not go further. Tried many things finally had
to restored back to Yosemite 10.10.5 from time machine. OSX booted, but got stuck in a Loop "Finder quit unexpectedly..." I had to reboot, COMMAND-R and reload Yosemite.
So, should I disable SIP, then upgrade to High Sierra?
I would like to, so I can get FileMaker 16 to work, as it won't with Yosemite 10.10.5.
Thank you,
David
to restored back to Yosemite 10.10.5 from time machine. OSX booted, but got stuck in a Loop "Finder quit unexpectedly..." I had to reboot, COMMAND-R and reload Yosemite.
So, should I disable SIP, then upgrade to High Sierra?
I would like to, so I can get FileMaker 16 to work, as it won't with Yosemite 10.10.5.
Thank you,
David
Does FileMaker 16 work in Sierra? If yes, then I see no good reason to upgrade to High Sierra. I'm lucky enough that everything works for me with Sierra. I refuse to go to High Sierra until Apple cleans up this mess. Additionally, I hate the idea to beta test the new file system when HFS+ still works so well.
Great question on FM16.....I just assumed it would if it doesn't work in Yosemite 10.10.5, although I wish I knew that before I paid for the upgrade to FM16.
I agree, I will wait at least until the end of January and see what is going on then.
The Mini is working great right now with the fresh load of Yosemite anyway.
I hate beta testing for anyone.
Thank you,
David
I agree, I will wait at least until the end of January and see what is going on then.
The Mini is working great right now with the fresh load of Yosemite anyway.
I hate beta testing for anyone.
Thank you,
David
I just upgraded my MacMini to High-Sierra v10.13.6. Everything (including BootCamp) still works fine.
Noticed that my main macOS partition (on my Kingston SSD) has been migrated to APFS.
My USB TimeMachine HDD was not (still MacOS Extended-Journaled)
My BOOTCAMP partition was not (still NTFS)
As before, SIP is still enabled (never messed with it).
$ csrutil status
System Integrity Protection status: enabled.
BootCamp Testing:
Restarted MacMini (and held-down Option-key at chime) to boot native Windows-10/64bit (v1703) on my BootCamp partition ... seems to work fine.
Shut-Down Windows and restarted MacMini to automatically default-boot back into High-Sierra again.
While I was inside Window-10, I ran Apple Software Update. It found a new "WiFi-Update for Boot-Camp", and I installed it.
Between this and normal updates in macOS, are there any other updates we need to install on our BootCamp-ed systems?