Rich Thompson

Also, should I just permanently decrypt the drive? Would that truly remove all traces of any VC on the drive? Make things simpler?

Thanks. Does this mean this is truly no longer a VeraCrypt problem at all? I still don't get why I'm seeing these random file formats with huge file sizes, do you think if I wait the full 48-72 hours or whatever it will "figure out" what the files really are?

Unfortunately, I am still running in to some issues. Is there a tool out there that's regarded as reputable? I'm not in love with the ones I have tried, and the companies are the kinds that come up frequently when you google some Windows error and the "suggestions" are update the drivers, some other generic stuff, and if that doesn't work, buy our product! They all keep spitting out huge files of formats I know I didn't have on the drive. 700mb .doc files, gz files, etc. I'm not sure what to do from...

HOLY FUCKING SHIT Okay, so I did that, put in the password with read only, backup header, and only create virtual device with no drive letter And Veracrypt accepted the password. But now what? When I right click on the thing in VC and click open nothing happens. Hope you accept Paypal or Venmo dude!

HOLY FUCKING SHIT

For testing purposes I encrypted a flash drive, there's a distinct difference between it and the 12TB drive right now. It defaults to say partition1 instead of 0. and in the select a partition it has an entry under the device. Selecting just the stick changes it to partition0 but that doesn't work with the password .I'm going to format it in the Win11 install screen and see what happens next. I can in fact mount Partition0 of the flash drive if I tick "use embedded backup header if available"

For testing purposes I encrypted a flash drive, there's a distinct difference between it and the 12TB drive right now. It defaults to say partition1 instead of 0 (and 0 didnt work) and in the select a partition it has an entry under the device. I'm going to format it in the Win11 install screen and see what happens next.

If I modify the path by hand to say \Device\Harddisk0 I get handle invalid source: mount:5109 If I modify it and put a \ at the end \Device\Harddisk0\ I get a syntax error source:mount:5109 One thing I sort of forgot about, but when the drive was working I always saw a drive in file explorer that if I clicked on, I'd get an error. When I unlocked the actual drive that weird phantom drive would remain.