Mounted Disk not accessible anymore on Windows
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
#634 Mounted Disk not accessible anymore on Windows
Hi,
I have a 6Tb SSD disk formatted in NTFS (also tried exFat) that worked fine on both Widnows and Mac using Fuese-T. Then, it's not possible to use it under Windows 11-64bit anymore.
It mounts correctly, but the disk is inaccessible.
Now I spent 10 days trying to see what's going on, downgrading to VeraCrypt 1.26.20 on all machines.
Reformatting the disk and copying again everythign back (that's what is time consuming)
What is interresting is that the disk seems to be accessible in Windows to a certain amount of data.
I have 5.2Tb of data on it and I wonder whether VeraCrypt correctly behaves passed 5Tb?
I also downgraded to 1.25.9, followed the instruction for the key, etc..
My disk doesn't have TrueCrypt trailing data, envelope, etc... it's formatted on windows each time in sha-512 with the latest VeraCrypt or 1.26.20 now
I did reformat it in 1.25.9 and tested again. Works fine up to a certain amount of data... but then mounts in windows but is not accessible. Windows says "the disk is not accessible".
Veracrypt on Widnows shows is as Type: Normal
On Windows it's shown as "Local disk" but doesn't have a name
A Repair Filesystem doesn't change anything
I have another disk that is 16Tb, encrypted with VeraCrypt, but in Apple APFS and it has no problem, but I don't mount it on Windows of course.
If I mount it on the Mac, no problem.
Any idea?
For your information, after intensive testing (and long nights copying back data) I put everything to 1.26.20 on each and every machine and this works.
Above 1.26.20, my disks are screwed and unreadable on Windows. They mount, but they're not accessible. Disk Repair doesn't change anything.
So I'm staying at 1.26.20 which seems to be the last version working cross-platform on NTFS disks.