Activity for Markus Schlögl
-
Markus Schlögl posted a comment on ticket #182
Since MS still wasn't able to include this natively, I'd highly appreciate this addition. Photoshop export is still clumsy, Lightroom exports natively, I'm using this every other day.
-
OK, but up til now it always worked exactly like that. The drive letters are "spaced" far from each other - G&H, then S&R - used to work flawlessly! Even when randomly connecting the external devices, the PW entry popped up, I entered, correct drive letter, every time. Now it just does... something, that must have a cause
-
Hey there, I had VC working flawlessly for about 2-3 years. No weirdness whatsoever, same machine, same drives. Recently, I connected a known external encrypted drive, and since then auto mount always assigns the wrong drive letters, even though they're stored and visible in the favourites. I have to cancel the PW entering popup a couple of times, then select the first drive letter of those two I regularly mount and it works, but connecting any of the 2 external drives results in them being assigned...
-
Hey Adrian, I removed all excessive drive letters, I didn't even know this was possible without rendering the drive unusable. So far, it seems everything is working fine again, so thank you very much, Adrian! On a sidenote, in case anyone ever searches for this: you can NOT run Google Drive in a VC container, as it's a virtual drive. It will display the files, file sizes etc, yet in a 0 KB folder. Make a Partition and encrypt it instead.
-
Since my version unfortunmately is in German, it maybe has a different name - I can access : add mounted Vol to favorites add mounted Vol to system avorites Favorite volume settings system favorite volume settings mount favorites fav vol1 fav vol 2 This is my backup disk, it's always connected, it's fully encrypted via VC! And the last couple of times, the drive letters were correct (except the container wouldn't mount automatically. I also found out it decrypts MUCH faster if I click on the hash...
-
Hi Adrian, I did precisely that. I just don't have the "organize" part, so I'll upgrade to the latest version of VC. The one removable drive I use has a specific drive letter assigned to it and I haven't connected it since weeks My screenshots:
-
Hi guys, sorry, I'm not good with this :-( I've been using VC 1.23 Hotix 2 for a while without issues, except every now and then the volume letter changing, crashing my Google Drive. Now I moved to a new apartment, upgraded the CPU, upgraded one HD to a larger drive, created a container and the 2 drives 81 fully encryted plus aforementioned container) I encrypted are either not mounted completely at startup (just the full physical drive, the container I have to mount separately) or mounted with the...
-
OK, I just found out that Veracrypt gives me this message and goes to the password entry window although both disks are already decrypted... the disks seem to be fine, after all, could there be some other reason this pops up?
-
Thanks for taking the time! I have 2 drives fully encrypted. One internal and one USB3 drive. I don't know if VC stops after failing to decrypt the first one, so maybe it's only one drive after all. So I'll proceed as proposed and try formatting. Thanks a lot!
-
Hey there, I haven't had this "Wrong password or no veracrypt volume" error for amost a year, then it started, and first time it occurred I kept retrying entering the passphrase, not trusting my eyes, until, at some point, VC reported back to me that the headers were damaged. Dismount/header restore/fix. No problem. I've read this is caused to an error within the drive that causes the surface, and thus the header, to change. According to Crystal Disk Info, my drives are fine, but I now have to restore...
-
I can't tell if this really helps, but I'me constantly having the same issue (will post about it separately). What I do: dismount the drives (2 of them) and restore the volume headers from embedded header files. Apparently, they are in fact mounted, but not readable due to a minute change within the hard drive, some error within the surface/file sructure that caused a change. That change makes the volume "unreadable". I also saved the header files externally, just to make sure. I wrote down what...
1
