Windows 10 and Treucrypt 7.1a problem

[Iridio]

Hi,
I just upgraded to Windows 10 and I am not able to access my tc files anymore.
I can mount them without problems, but when I try to access them from file Explorer, I get an error saying that the "f:\ is not accessible. Function not correct".
I can mount them from osx or Windows 8.1.
If I create a new file everything works fine, but, before migrating my tc files, I would like to know if someone has already had and solved this problem. Maybe after a week I will be stuck at the same point?
Also my external encrypted HDDs have the same problem.

[AdrianK_IT]

I'm speculating, since I don't have your problem; my (clean install of) Win 10 Developer Preview (now upgraded to RTM?) works with TC without issues.

I wonder if there's a problem with the IDs for mounted devices (possible duplication?) as a result of the upgrade (from what OS?). Look in the registry at HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices, where the mapping between IDs and drive letters (as created in diskmgmt.msc) is stored.

You can flush the entries by removing/unmounting all but fixed drives, and running mountvol /r from an admin command prompt. (You'll need afterwards to recreate the drive letters you want to pre-allocate to eg removable drives in diskmgmt.msc.)

[Iridio]

The trick did not work, I also tried on a fresh install of Windows 10, but same results.
My main pc is an upgrade from Windows 8.1 to rtm 10.

[AdrianK_IT]

Well, I guess you have to assume it's a W10 problem, and not a TC one, if your TC files mount and are accessible elsewhere.

The only other thing I can suggest is to try the Nirsoft utility DriveLetterView: http://www.nirsoft.net/utils/drive_letter_view.html

This gives a lot of info about how mounted devices (past and present) are represented by the OS; perhaps you might get some clues from studying the relevant TC entries.

[Iridio]

I though the same and, honestly, I was hoping to not be alone, naked in the rain
I will try the software you suggest, see if I can find a solution and get back here.
Thanks a lot for your time

[Iridio]

Hi,
I have tried the software and here are the porperties of the mounted file: http://tinypic.com/r/2uggzs6/8
everything is empty. Also if I use chkdsk f: from a command prompt, it can access the disk and give me all the info about free space and how many files there are. But if I try to launch F: I get the incorrect function error.
This evening I will invest some time and try to understand what is really happening.
plan B (recreate and copy the files) is a lot of work but doable without too much hassle

[seba]

I have the same issue. Creating a fresh encrypted partition under Windows 10 does work fine, although the partition I created is much smaller than the one that is not working. When comparing the properties of both these encrypted partitions with the DriveLetterview tool, there are differences: In the working partition, FILE SYSTEM is set (FAT32) and VOLUME SERIAL NUMBER also, whereas in the non-working partition, both fields are empty.

[r2d2]

i read in some other post that one fixed by giving the user he uses in win10 over the security tab over the drive rights and he could access the drive now

so right mouse on the drive than properties than security and than add the user with rights

[Iridio]

There is no security tab. It appear correctly for the other disks, but it does not for the truecrypt's one.

[r2d2]

there must be some security tab where you can give users rights for write/delete/access and so on for the drive in explorer

http://www.sevenforums.com/tutorials/122666-permissions-allow-deny-users-groups.html

[AdrianK_IT]

There'll only be a security tab if the TC file was formatted NTFS.

[Iridio]

My disk are NTFS, but I suppose I do not see the security tab because the system (except chkdsk) can not access the partition

[dmathew]

I posted the post below on a Microsoft Community forum on 5 August. My solution was very tedious: to decrypt over 250GB of files from various volumes and encrypt them again.

"I had 2 Truecrypt encrypted volumes on the Bootcamp partition of my late 2013 Macbook Air. They were not whole disk encryptions. I did not decrypt them before the upgrade. They were both inaccessible from the
upgraded laptop after the upgrade.

I copied one of the volumes over to an older Macbook Air running W7 and could mount it fine on that machine. So my files were OK. Since the upgrade I have also tried to create NTFS volumes on the Windows 10 machine but have been unable to do so. I have tried with Truecrypt 7.1a and the current version of VeraCrypt without success. FAT volumes are fine."

[seba]

Are you on a Mac, using Bootcamp? Then this thread worked for me, although a bit hacky. (In a nutshell: Rename AppleHFS.sys and AppleMNT.sys, reboot. And optionally recover HFS accessibility with 3rd party drivers, see further down the thread)

[Iridio]

Thanks seba. Now it works!
Now I remain with a PC with a fresh install that still does not work. I will try a new fresh install and see what happens

Thanks again.

[Iridio]

For the records, with BootCamp 6.0 the problem persists. It is still necessary to rename the HFS drivers

[LedaOhio9]

You need to set yourself as OWNER and give yourself AUDIT rights.
Right click drive in file manager Properties / Security / Advanced

Add your boot login name and give yourself FULL in there