Bootcamp drivers issue (Windows 10 + encrypted ntfs disk - TrueCrypt and all other)

Be aware that if you delete these two files, you lose readability of the OS X JHFS+ partition on your Mac. You cannot read CS volumes as of now. ELC may change it.

Hello, and thanks for the solution to get TrueCrypt mounting again.

Now to get your HFS volumes back for read/write. Go to Paragon Software's free tools page, download and install HFS+ for Windows® 8/8.1 Free Edition.

This is working for me.

Enjoy

Thanks. It is a good option. Very 😎.

Superb! Had same issue (Macbook Air, Windows 10, encryption software). Thnx

This also fixed my Veeam Endpoint Backup v1.1.0.110 issue on Windows 10 (VSS failure)...

BTW - I added back (I renamed didn't delete) AppleMNT.sys, and all remained well. Seems the only one you really need to remove from the mix is AppleHFS.sys.

Thanks for the update. Good to know Apple has kept the same known bugs in their software. 😁

AppleMNT.sys is the mounting driver. AppleHFS.sys is the file system driver and is the main culprit. AppleMNT.sys also supports other devices like Firewire external disks, etc.

So I understand that only AppleHFS.sys needs to be removed, right?

I could mount a hidden volume on USB drive with truecript but when I was trying to open it, it would give an error: Location is not accessible. Incorrect function. I only removed one file AppleHFS.sys from windows/System32/drivers and restarted and everything is working fine. Thank you.

I have upgraded from Windows 7 to Windows 10 on my PC, and experienced the same issue for my secondary 1 TB HDD.

I was able to boot from the primary SSD but the secondary HDD showed as a raw space on Disk Management. So I was not able to browse it and was receiving an error saying "F:\ is not accessible. Incorrect function." when I double-clicked it.

I actually had to use a data recovery tool to successfully access the HDD (data was indeed intact, I was able to copy files out of the drive) and was trying to free up some space for the recovery...

However, simply renaming "AppleHFS.sys" to "AppleHFS.sys.bkp" and rebooting fixed the issue in my configuration as well. Many thanks for the suggestion... You saved a lot of my time!

P.S. I have actually received paid technical support (which costed me around $149) from Microsoft and the case was escalated to level 2. It took around a week, many discussions on the phone, and a lot of remote access sessions for them to say that they were not able to resolve this issue, and they suggested me to seek for professional help from a data recovery office. Wish I could now show those guys how easy and fast this fix actually was :-). Also, it took around 3 months and at least 10 phone calls to get a full refund...

emreerokyar wrote:

P.S. I have actually received paid technical support (which costed me around $149) from Microsoft and the case was escalated to level 2. It took around a week, many discussions on the phone, and a lot of remote access sessions for them to say that they were not able to resolve this issue, and they suggested me to seek for professional help from a data recovery office. Wish I could now show those guys how easy and fast this fix actually was :-). Also, it took around 3 months and at least 10 phone calls to get a full refund...

Glad that they gave you back your money. 😎

Amazing, I was about to drop truecrypt because of this problem.

And so just to rename a widows32 apple driver, All work perfect

looking for solution in two wreaks, problem solved i 1 minut.

Thank you to all of you for your time and interest.

Please create a Windows System Restore point, and review all Windows updates before you apply them. A good backup of OSX and Windows is highly recommended.