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
