High Sierra and Boot Camp?

Thanks, I was having the same issue but this explains it. Basically, the Boot Camp Assistant is currently unable to see the new file system.

Pretty much right after I updated to High Sierra I applied a key to my Windows 10 partition. I had a pop-up in Windows 10 saying that I was almost out of space and to delete the old version of my operating system. I ALMOST clicked approve but then stopped and thought for a second. Looking at my HD in W10 it doesn't see a separate partition. I think if I clicked approve Windows 10 may have tried to delete my OS X. I can't verify this as I didn't approve the process but now I'm worried that Windows might start messing with my OS X partition accidentally due to not recognizing it.

Could Windows start switching the files to its file format with since it doesn't see the Mac partition?

ThornX wrote:

Could Windows start switching the files to its file format with since it doesn't see the Mac partition?

Windows does not/will not understand APFS. I suggest not using any third-party cross file system tools either. If you manually map APFS container/volumes, you will end up with corrupted macOS.

That's not a concern worth giving time to... Deleting your old install would have meant deleting a directory on you Windows system labelled "Windows.old" - literally a folder with old versions of files now updated in your CURRENT "Windows" directory...

As long as you're not using a partition or volume manager you have no worries about Windows trying to erase the MacOS end of things.

If have a similar issue but with the difference that after updating to HS my Windows 7 installation doesn't start at all. When I hit "alt" during the boot sequence I can only see the OSX partition. The Windows installation is not visible. When I chose Windows as the standard start volume in OSX the boot sequence end with the message "no bootable divide - insert boot disk and press any key". So OSX runs fine but Windows is not running after the update. HAs anybody any idea?

The only answer people seem to give to this isn't an answer at all. It's simply instructions on how to boot back into Mac OS. No response from Apple as to the fix for bootcamp and driver updates. It's been 3 months now. Apple is slow as **** to fix anything much less acknowledge something that's broken.

I understand your frustration. Provide Product Feedback (and wait!. BTW, you are competing with iPhone X 😉 ).

Another option is to not upgrade to High Sierra, or rollback to Sierra where it works as designated. If HS is a must, then there is at least a workaround.

For someone who also uses macOS/Windows remotely, this is worse than someone who has physical access to the Mac.

I sincerely doubt there's any competition going on. Surely Apple has multiple separate developer teams. I can't roll back I haven't backed up recently enough.

Next time I will not update till at least the x.1 release of that version is out.

In my specific case, I have HS on an external disk, which is installed on a HFS partition, so switching is not an issue. It is not an optimal solution, and the external disk can be a bother to manage.

Hie. I recently did a fresh installation of my mac os I installed a fresh copy of sierra high. Meaning I formatted my drive including the partition which had my Boot Camp on Sierra the first one. Now I have installed my Sierra High when I try to do installation for boot camp, When I reach a stage after booting, were I need to select disk to install windows when I select Boot Camp Drive, it says "this partition needs to be formatted", and there is no way I can skip this option. if I format the Boot Camp Drive it changes its name then after installation completion I cant find the boot camp menu. Or other features that comes with boot camp it will be just like an other ordinary windows disk.

My question is are there any boot camp updates for mac OS Sierra High drivers available yet.

I'm experiencing the same problem. I just tried to make a bootable USB for Win7 and every time I hit continue it always crashed right after that. I haven't tried on Win10 yet.

Also, I tried the alternative of running dd to try and directly install the .iso onto the flash drive but it kept giving me an error saying that it couldn't do it.

Since Bootcamp has a lot to do with the file system when you install this kind of stuff I have a feeling that bootcamp doesn't support the translation of the dd command from APFS to the FAT/NTFS file structure that has to be used when you create the bootable USB. If the dd command is failing, that's what bootcamp uses to create these "installmedia" drives I think so this would explain it's crashing.

worked perfect for my 13" 2012 2.9 i7 but the bootcamp control panel doesn't see my Mac install in the bootcamp control panel so when I say reboot to Mac it says a Mac volume cannot be found so I just restart Win 10 normally from start menu and hold down the option key to boot into Mac and then in the Mac side I have my startup disk control panel I can change to Mac OS and leave permantly so it boots to Mac by default. And if course if I want Windows I restart Mac and do just the opposite with option key and select Windows but neither is a big deal but it'd be nice is the win 10 BC control panel saw the Mac install in the control panel too....hopefully an update soon to bootcamp win 10

This issue of course is because High Uses a new APFS (File system) and boot camp hasn't been updated yet but using option after a reboot works fine unless you're just going to Mac from windows and Mac is your default startup drive so it's not a big deal either way really. just backup up Mac beforehand just in case the partitioning goes wrong. usually it doesn't but you never know....

Please also see Re: Bootcamp partitioning error in macOS 10.13 and the Time Machine-related issue.

I suggest you start a new discussion in Boot Camp .

HS should support the existing BC/Windows installation. The partitions do change in HS. Back up is critical, in case you need to nuke-and-pave.