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

Thanks a lot for the patience. Now I get it that when CoreStorage LVM is enabled, Windows won't see Mac partition.

And Apple is moving towards CoreStorage.

But I don't get this statement:

"The driver is no longer bundled with SW downloads"

The JHFS+ driver is in the latest BootCamp 6 download right? I downloaded BootCamp 6 and installed less than 3 week ago for my MacBook Air with Win10 version 1511. I can see my Mac JHFS+ partition from Win 10 version 1511.

Bootcamp BC driver packages for 2012-2015 models which may use 6.0.6136 (release date 31 Mar 2016) can still get the driver package, since it has not been removed. Newer models which use newer BC6 packages will no longer have these drivers. I have a 2013 rMBP, which needs 6.0.6136 which has this driver and works with 1511_2 but breaks under 1607 version of the ISO.

The changes between 1511 and 1607 ISOs is where the issue lies. I tested 1511_2 to 1607 upgrade today on a 2013 rMBP and these two drivers stopped working. It would be prudent to look at external disks as shared storage between the two OSes, or staying with older Macs (and older W10 builds or W7/W8.1) if the read-only functionality is critical.

Apple is most likely not going to update the BC packages for older models and will leave the current versions as they are (containing these files) for users of older Macs.

Thanks again, now this is very clear.

I will stay away from Win10 1607, and I won't buy new Mac until this issue is resolved.

By the way, the Boot Camp version I am using on my MacBook Air mid-2012 is not built from Boot Camp assistant, I downloaded Windows Boot Camp package from Apple support page, the version is 6.0.6201.

I googled the download link, now I don't remember the link now.

Prof Z10 wrote:

By the way, the Boot Camp version I am using on my MacBook Air mid-2012 is not built from Boot Camp assistant,

Can you identify which one of these two do you have (reference - How to identify your MacBook Air - Apple Support)?

Mine is 13 inch 256 GB flash.

I identify it by clicking "About This Mac".

Prof Z10 wrote:

Mine is 13 inch 256 GB flash.

I identify it by clicking "About This Mac".

For MBA5,1 and 5,2, I get 6.0.6136. If you searched on the web, and found references to it on a Chinese/Korean web site, and downloaded it to your Windows side, I suggest you remove Windows and re-install with the official Apple version provided via BC Assistant.

Also, the BC Assistant version on El Capitan 10.11.6 is 6.0.1 (6024.40.2).

Someone posted the link on reddit, it is apple.com link.

http://swcdn.apple.com/content/downloads/16/10/031-55711/ufi4c7o3x20i5ge93l2yu86 9yegn222i8l/AppleBcUpdate.exe

I don't recommend other people to do this, I did out of laziness, I just used it to upgrade my existing Boot Camp. I do not have 4GB USB create Boot Camp USB from BC Assistant.

That is a Windows executable. Using Brigadier, I get 031-55710...

./brigadier -m MacBookAir5,2 -o Bootcamp-MBA5.2

Using Mac model: MacBookAir5,2.

Model supported in package distribution file at http://swcdn.apple.com/content/downloads/39/14/031-55710/u2c6bi4yl91ud1lqc3k53bx 9860hvsnf7z/031-55710.English.dist.

Distribution 031-55710 supports the following models: MacBook8,1, MacBookAir5,1, MacBookAir5,2, MacBookAir6,1, MacBookAir6,2, MacBookAir7,1, MacBookAir7,2, MacBookPro9,1, MacBookPro9,2, MacBookPro11,1, MacBookPro11,2, MacBookPro11,3, MacBookPro11,4, MacBookPro11,5, MacBookPro12,1, MacPro6,1, Macmini6,1, Macmini6,2, Macmini7,1, iMac13,1, iMac13,2, iMac13,3, iMac14,1, iMac14,2, iMac14,3, iMac14,4, iMac15,1.

Model supported in package distribution file at http://swcdn.apple.com/content/downloads/53/19/031-0787/e59hg9xe761b8zzeyrffkjo2 i2zuogqd9g/031-0787.English.dist.

Distribution 031-0787 supports the following models: MacBookAir4,1, MacBookAir4,2, MacBookAir5,1, MacBookAir5,2, MacBookPro6,1, MacBookPro6,2, MacBookPro8,1, MacBookPro8,2, MacBookPro8,3, MacBookPro9,1, MacBookPro9,2, MacPro4,1, MacPro5,1, Macmini5,1, Macmini5,2, Macmini5,3, Macmini6,1, Macmini6,2, iMac11,3, iMac12,1, iMac12,2, iMac13,1, iMac13,2, iMac13,3.

Model supported in package distribution file at http://swcdn.apple.com/content/downloads/14/07/031-11365/cccsb0mg8mn39rykh4yj8qo a2ao3q94t0w/BootCampESD.dst/031-11365.English.dist.

Distribution 031-11365 supports the following models: MacBookAir5,1, MacBookAir5,2.

There is more than one ESD product available for this model:

031-55710: PostDate 2016-04-01 22:22:52

031-0787: PostDate 2014-02-11 21:35:32

031-11365: PostDate 2015-02-09 18:42:37

Selecting 031-55710 as it's the most recently posted.

Making directory Bootcamp-MBA5.2/BootCamp-031-55710..

Fetching Boot Camp product at URL http://swcdn.apple.com/content/downloads/39/14/031-55710/u2c6bi4yl91ud1lqc3k53bx 9860hvsnf7z/BootCampESD.pkg.

100.0% 1614454784 / 1614454648 bytes

Expanding flat package...

Extracting Payload...

Extracted to Bootcamp-MBA5.2/BootCamp-031-55710/WindowsSupport.dmg.

Done.

This is from http://news.softpedia.com/news/windows-10-anniversary-update-might-hide-partitio ns-after-install-507247.shtml:

One of the issues experienced by users after installing the Windows 10 Anniversary Update concerns partitions, as many of those who upgraded their computers reported that a number of partitions disappeared from File Explorer.

Furthermore, all partitions show up as RAW in Disk Management, which makes most people believe that all their data has been removed and nothing can be recovered.

Microsoft, however, claims that this is just a bug discovered in the Windows 10 Anniversary Update install system, and while no files are lost, it’s critical for users not to try to recover anything with third-party apps because this could lead to completely breaking down the partitions and removal of data.

“Microsoft is aware of this issue and is working on a solution to be released through Windows Update. Any data you have stored on the affected partition is still there. We recommend that you not try to recover or otherwise write data to the affected partition, nor should you format the partition,” the company says.

You can also downgrade in the meantime

Microsoft’s Sharath Srinivasa goes on to explain that a patch will be released to users when it’s available and states that users who do not want to wait for it can always downgrade to their previous Windows version. Partitions should be then just as you created them, with all files once again accessible.

Rolling back to build 1511 works and hopefully not too many people will have hosed their BootCamp partition in the meantime.

djpenn wrote:

Rolling back to build 1511 works and hopefully not too many people won't have hosed their BootCamp partition in the meantime.

This is as expected. It is a bug in 1607 and Anniversary builds, both.

Loner_t wrote:

Testing so far has pointed the finger squarely at Microsoft. If Apple will give me the driver code, I can debug it further.

I hope this gets fixed by Microsoft or Apple, it's really bugging me

I've been looking here every single day:

https://support.microsoft.com/en-us/help/12387/windows-10-update-history

I'm hoping we don't have to wait until the next Patch Tuesday (Sept. 13), but that seems like the most likely release date 😠

I had the same problem. Glad I'm not the only one. Gone back to previous build until this is fixed. Not sure if this is Microsoft problem or Apple..

Neil12134 wrote:

Not sure if this is Microsoft problem or Apple..

Microsoft....

Update:

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

Description from https://support.microsoft.com/en-us/help/12387/windows-10-update-history

mentions among other things:

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Improved reliability of [...] Storage Spaces Direct [...].
• Improved performance of Storage Spaces Direct with many nodes or disks, [...].
• Addressed additional issues with [...] software compatibility, [...] driver setup, [...] disk-to-enclosure mappings not working, [...].

For more information about the complete list of affected files, see KB3176934.

Those seem to be the only things noted that might conceivably have some impact on the disappearing partition issue. Has anyone tried it? I can't until next week or so after an image backup and then updating to build 1607. Let us know if you have it; you will be able to tell by typing Windows Key+R (or right clicking on Start menu/pearl button and selecting Run...) > then type in winver > click OK. After the KB3176934 update it will be OS Build 14393.82 (as opposed to 14393.51 as of the August 9 update).