Q: Windows 10 Anniversary + Boot Camp = no longer mounting Mac partition

I have a 12 inch Retina Macbook that has Windows 10 build 1511 on it, and I can't see my mac partitions.  I think this is because the SSD on the macbook was configured with core storage, which the bootcamp NTSF drivers don't support

I have a 5K iMac that doesn't have core storage, and I can see my Mac partitions just fine in bootcamp. 

To check if your drive is partitioned under core storage go to Terminal and type "diskutil cs list".  If it says "No CoreStorage logical volume groups found", then you don't have core storage.

Just wondering, is apple not enabling CoreStorage on all their new macs?  Are all the iMac 5K configured with core storage off, but Retina Macbooks come with it on for some reason?

CS is the default beginning with Yosemite. It is mandatory if you use FileVault2 or have a Fusion drive. If you do not use FV2, and your CS is revertible, you can revert to HFS+ which will be visible and read-only on the Windows side.

September 13, 2016 update:

KB3189866 is out, bringing Windows 10 up to build 14393.187

https://support.microsoft.com/en-us/kb/3189866

The Knowledge Base article states "Windows 10 updates are cumulative. Therefore, this package contains all previously released fixes." but it looks just as crappy as the previous updates, at least as far as this partition issue is concerned...

Maybe there is hope on the horizon:

http://answers.microsoft.com/en-us/windows/forum/windows_10-files/partitions-may -be-missing-after-installing-the/ffafb34…

Just trying to get my head round this issue. I have Windows 10 installed on my iMac 5K's (late 2015) fusion drive. If I let it update to the Anniversary Edition, will it actually damage the Mac OS partitions on the fusion drive or is this just an issue with accessing the Mac OS partition(s) from Windows 10?

Thanks in advance...

I suggest staying away from the Update. It breaks the two drivers used by Apple to allow read-only access to OS X partitions. Do no manipulate the Apple partitions in Windows Disk Management. Can you currently see the OS X partition in Windows?

Thanks for the reply - yes, I can see the OS X partition at the moment but I have no particular need to do so.

Create a Windows System Restore point, and then upgrade. If you have other unrelated issues, you can roll back to the Restore point in Windows Safe Boot.

Thanks - not too worried about the Windows 10 side of things; I just want to make sure that the Anniversary Update doesn't actually cause any problems for OS X. I wasn't sure whether it was actually hosing the partition table or not...

I have the win 10 1607 anniversary installed with bootcamp and I was unable to see the HFS+ partition (I have installed macOS Sierra). I wanted to reinstall it with the version 1511 but before that I just followed the mentioned steps from this link to disable CoreStoge and I was able to look the partition with Paragon HFS+, without Paragon the drive didn't show anyway but disabling CS I could use it as normally!

https://support.symantec.com/en_US/article.HOWTO109622.html

romanfromson wrote:

 

... I just followed the mentioned steps from this link to disable CoreStoge and I was able to look the partition with Paragon HFS+, without Paragon the drive didn't show anyway but disabling CS I could use it as normally!

The Apple HFS+ driver is still broken in 1607, but (commercial) Paragon HFS+ works. FV2 and Fusion drives are still

off-limits and have always been.

Let me put this story into perspective, this requires some explanations, so it's a rather long message!

I am running a MacBookAir 13'' mid 2013, 1,7GHz i7, 8GB Ram, 512 GB Apple SSD. Attached to an older cinema display, using the Apple wireless keyboard, a Logitech MX Revolution mouse along with Logitech ControlCenter 3.9.4 (most of the time) and the Apple magic mouse (sometimes).

---> I have Tuxera NTFS installed (currently the 2016 release candidate).

I recently updated from El Capitan to Sierra - this worked,  although not entirely well and the machine freezes now from time to time, an as yet unresolved issue which I suspect may be related to the Logitech stuff, but that's another story.

Under El Capitan I installed win10 from scratch closely following the official Apple routine for bootcamp installations. I got my win10 directly from Microsoft, it was NOT the anniversary edition but the one before that. Installation went smoothly and everything worked fine but for the Apple wireless keyboard which did not connect with a driver error message. See the separate, rather lengthy discussion of this somewhere else in this forum.

The keyboard issue can be solved, btw, to some extent by simply deleting the respective Apple driver (also out of win10, otherwise it gets reinstalled every time upon booting) and reverting to the on board Microsoft driver. This works "so so", screen brightness, volume are NOT adressable via the wireless keyboard - which is not that important - but unfortunately the "delete" button also does not work for deletion of files (you must do it via the mouse).

Anyway, apart from this issue, both OS ran fine and without any complaints.

I then both updated from El Capitan to Sierra and from win10/Nov2015 to the win10 anniversary release.

The win10 update as such went smoothly with my setup, other than users report in the internet the installation proceeded without any problems.

However, I did no longer "see" the HFS partition under bootcamp win10 AND I did no longer see the win 10 partition under Sierra!

I then checked the partition scheme and found out that win10 had created a fifth partition for win recovery, the so called "450MB-partition".

Via Tuxera I could mount the win10 partition alright under MacOS, but this had to be done every time upon booting.

So I installed under bootcamp win10 the AOMEI partition manager, deleted that fifth recovery partition and enlarged the preexisting win10 partition lying right in front of that 450MB recovery partition presumably back to its original size.

This worked fine and thereafter the win10 partition was recognized under Sierra alright.

But I still did not get the MacOS partition mounted under win10. There are suggestions in the net such as to install the MiniTool partition wizard under win10 and by using this program the partition should mount.

I can NOT confirm this, neither for the MiniTool nor for the AOMEI partitioning program.

BUT - upon installing Paragon HFS+ software the MacOS partition reappears under win10 (and leaves the macos situation otherwise unaffected, i.e. fine).

Taken together: Merging the newly created win10 recovery partition with the preexisting win10 bootcamp partition and installing Paragon HFS+ likely will solve the problems encountered with the bootcamp win10 anniversary update.

The Paragon software is free for 10 days only, then you must pay for it (it does provide both read AND write permissions from within win onto macos, which I consider potentially dangerous).

So for the time being I rather would refrain from updating to the win10 anniversary edition (and possibly also from updating to Sierra!).

Siggi Engelbrecht