Yup, I've tested both methods now and they work exactly as described. =D Ext2FSD is pretty wonky though. In addition to the problem where the window closes after clicking the checkbox, I also had an issue where when trying to change the drive letter the letter would disappear completely and then reappear as having all three of the values I switched between (showing "D:G:F:"). But after I got it down to one letter and having the permanent mount option I verified it as working between reboots and that it created the exact registry key you described (well different volume number from the example but otherwise the same). Running the Ext2FSD uninstaller removed the key, so I added it back manually and it's working the same. Thank you for this!Hello, I've discovered a method which worked for all my hackintoshes. Apple bootcamp 6.0 drivers work fine after 1607 update, they just have problems mounting the drives... Give it a try if you like, this may end up to be the solution;
-Install 6.0 drivers just like before anniversary update, reboot. Nothing will show up..
-Download ext2fsd even though you probably have nothing to do with ext2 or linux.
-Open Ext2 Volume Manager. In "File System" tab, your macOS partition will show as "HFS". If you installed ext2fsd before succesfully installing bootcamp drivers, it will just show as "RAW". (kind of proving bootcamp drivers do work)
-Right click, select assign drive letter (or change drive letter).
-In the pop-up menu, select the drive letter first, then select the tick "Create a permanent MountPoint via Session Manager." It -weirdly- closes the pop-up before you click "OK" (at least on version 0.66 I am using, it may be a bug).
-Reboot, and the macOS partition will be there just like before anniversary update. (On one of my computers, it didn't show on first reboot, I've gone into ext2 volume manager, redid everything then rebooted, it showed on second time.)
It worked for me on Mavericks, 10.10.5, 10.12.2. It also worked for me on 10.6.8 + Win 10 + 32bit bootcamp 4 drivers. This site helped me by providing bootcamp drivers, I hope I am returning the favor.
Also, it MAY be possible to add a registry entry via regedit, which is exactly what ext2fsd does for permanent mounts.. Honestly, I haven't tried this. I already use ext2fsd for my linux partition, and I don't want to risk breaking my perfectly working systems. Afterall, this functionality may depend on something installed via ext2 driver and may not work anyway.. Perhaps someone could try that as this may be a better solution than downloading some program:
Run regedit, navigate to:
HKEY_LOCAL_MACHINE/system/CurrentControlSet/Control/Session Manager/DOS Devices/
Right click-> new-> add string..
Enter the drive letter you desire for macos partition with ":", in my example its "G:", then in data section type in; "\Device\HarddiskVolume#"
# will be your volume number as would be seen in MS-DOS. I am sure someone could suggest a more elegant solution for this one, but you can simply go to control panel/administartive tools/computer management/disk management, and count all your partitions starting with 1 (not 0). I, for example have 1 partition in disk0, and my macos partition is the 2nd one in disk1, so my volume number is 3. In my registry, it writes "G:", "REG_SZ" and "\Device\HarddiskVolume3" for name type and data respectively.
You can -probably- do trial and error on this one (rebooting each time to be sure), nothing should break so long as your drive letter doesn't contradict with anything you already have..
Please report back if this works.
Cheers that did actually work (surprised the heck out of me), although I had to install it only for me rather than all users otherwise the installer failed. I wish it let you choose to mount the drives as Read Only (coz I'm paranoid and just want to read the data)Paragon HFS+ for Windows 8/8.1 free edition works with Windows 10 Anniversary Update.
I haven't had any problems so far. You just have to register to get Product Key & Serial Number.
[doublepost=1486294509][/doublepost]your method of bootcamp just fried my windows 7 startup, how to start it now?These are the Read-Only HFS+ drivers that comes with Boot Camp.
They can be installed on any matching Windows Vista, 7, 8, 8.1 or 10 machine without the need to install the Boot Camp package (and also easily removed if necessary). - Technically v6.0 should work on Vista/7/8 but it has not been tested.
If you are using the Windows 10 Anniversary update uninstall the driver and use Paragon until things are sorted out.
How to Install:
1) Uninstall Paragon or MacDrive
2) Copy AppleHFS.sys & AppleMNT.sys to C:\Windows\System32\drivers\
3) Merge Add_AppleHFS.reg
Are you using a fusion drive?[doublepost=1486294509][/doublepost]your method of bootcamp just fried my windows 7 startup, how to start it now?
Method I've written a few posts above still works on all HFS+ drives, on latest Windows as of now (1709 build 16299.248) and on latest High Sierra 10.13.4 beta *without* APFS filesystem. I still use it on the same 3 computers since I've written that post a year ago, no issues whatsoever on any of them..Is there an up-to-date guide that works with latest W10?
Many thanks for this shared work @Quad5Ny, I took the risk and installed them on a "clean" Windows 10 Pro system, after Paragon HFS+ Trial Expired and was forced to uninstall (with a couple of reboots). The test USB stick (Sandisk Cruzer 32GB) worked fine in Read-Only mode, after rebooting of course. My Windows is the April 2018 update 1803 (Build 17134.112). Doesn't seem to work (i.e. mount) with external HDD or SSD in enclosures, but was worth the effort (it says please insert disk or something). Many thanks again.[Boot Camp 6] Windows 8.1 and 10
- Description: Read-Only HFS+ driver from Boot Camp 6.0 (Build 6237)
- Name: Apple_HFS_Read_Only_Driver_v126.96.36.199.zip
- Size: 47,252 bytes
- SHA-1: 480cb9a87fabd99cd680f37f0b4288af7aa790a1
- VirusTotal: https://www.virustotal.com/en/file/...6f5f83b32cbe0df957f1bb22b52e2fffc0b/analysis/
Oh! That’s interesting. I wish there was some sort of logging process so that we could see what was going wrong with my registry. Three consecutive clean reinstallations caused the same problem (it was the first and only thing I did on the second reinstalls), so I just gave up the concept for now and am trying to create an NTFS-formatted external hard drive so that I can copy my files over the hard way.My windows 10 redstone 4 does not crash after the files have been placed and the registry to enable merged.