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

That would be troublesome. I already have a 2TB encrypted TrueCrypt volume filled with data which would be very annoying to re-initialize. In addition, I use this TrueCrypt volume to share data between OS X (which is encrypted with FileVault so I can't access it from Windows) and Windows so it's gonna be hard to find another cross-platform encryption tool.

Consider bcrypt or ccrypt from MacPorts. TrueCrypt is no longer being maintained.

hcsradek wrote:

But what software do you recommend for Windows (this is the issue - to have something Working on Windows 10)?

BitLocker will work fine as a Windows-only tool. A cross-platform tool is a completely different proposition.

I have read that Windows 10 is having different drivers for drives - maybe the incompatibility between these new drivers and BootCamp drivers is the issue?

On the *nix side, each file system has its own driver thru the vfs/vnode model, which has grown and matured over the years. Monolithic file systems do not allow such modular growth. Does TrueCrypt work on a native PC? (I may asked this already. 😟 ).

When do you expect that Bootcamp will start to officially support Windows 10?

W10 is out end of this month, my guess is that it may take a few months to get driver packages from Apple to support it. W7-W8 drivers should be supported for backward compatibility.

My suggestion is to look at https://www.grc.com/misc/truecrypt/truecrypt.htm and see what i the possibility of making it work by downloading/modifying/testing the available source code. If the underlying OSes deprecate services which may be used in older version of software, it is difficult to continue to use older software.

Another option is to test it under a Virtualization engine.

With the same respect...

The problem cannot be undone (even after uninstalling Bootcamp on Windows NTFS drives are still not accessible).

Can you explain this statement in the OP? Does everything work without the BC drivers installed? Have you tested with individual drivers being installed one at a time to narrow down which driver is the culprit so a solution can be sought?

This may help solve the problem or at least have a logical explanation, instead of it not working at all for many users who come after us to read this discussion.

hcsradek wrote:

I have no idea what is being installed bu Bootcamp and why the installation process doesn't revert it...

My suggestion is to debug this a bit further.

hcsradek wrote:

After individual drivers being installed it works, however in this method I am not getting the full functionality of Bootcamp (for example management of brightness, the Bootcamp control panel in not installed etc.) - this suggests that this is something, what is installed besides the drivers.

Precisely. Please see Bootcamp.xml for the list of the entire driver set. My suspicion is the AppleHFS.sys and AppleMNT.sys are the culprits. Since you already have the capability to play around, can I suggest you remove these two and test? This will allow the entire BC driver set to be installed with a working TrueCrypt, if the two suspect drivers address the issue. This should help future users of a similar environment.

I downloaded the 7.1a source code from GRC, and will try and build it out of my own curiosity. The product is primarily for Windows. There is some very interesting material on DFS.

Can you download Sysinternals Autorun (https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx?f=255&MSPPError=- 2147217396) and look at the drivers in the Sysinternals and verify that these two are not there?

Please see Some known issues with boot camp 5.1 with windows 10 as a reference.

hcsradek wrote:

I have simply deleted both files from c:\Windows\System32\Drivers - now Autorun says that "file not found" but TrueCrypt works again with NTFS partitions and BootCamp installed :-).

Can you repair all your drivers, so you have full Apple hardware functionality, including screen brightness, sound, keyboard, etc. and then just remove these two to make sure it continues to work? The other option is remove Windows and install a new copy, remove these two and test.

I am 😀 to see it working. If I get a chance, I will debug further to check if the HFS/MNT can be made to coexist with TrueCrypt.