-
I cannot reproduce this on any version of Windows.
Are you running 1.7.1836 ?
Does the problem go away if you uninstall, and reappear if you re-install?.
2009-11-09 12:20:35 UTC in AxCrypt - File Encryption for Windows
-
Hello,
This is by design. The original file name is kept encrypted inside the encrypted data, and is always used when the file is decrypted. This is to allow you to rename the encrypted file without affecting the original file name.
Svante.
2009-11-08 10:45:31 UTC in AxCrypt - File Encryption for Windows
-
This is basically a good idea, and will be considered for the next version of AxCrypt. Thank you for the suggestion!
2009-11-03 16:45:23 UTC in AxCrypt - File Encryption for Windows
-
This is by design, if I understand your situation correctly. You should need to respecify, and have access to, the key-file if used after a log off or reboot.
2009-11-03 16:44:37 UTC in AxCrypt - File Encryption for Windows
-
svante made 2 file-release changes.
2009-11-03 16:38:13 UTC in AxCrypt - File Encryption for Windows
-
Hello,
This is filed under group 1.7 Beta - is that the actual version you are installing?
Exactly what is the file name of the installer?.
2009-10-30 08:17:08 UTC in AxCrypt - File Encryption for Windows
-
Please try the current version 1.7 beta, available at http://www.axantum.com/ . It corrects many issues, including a memory leak that may be the root cause of this.
2009-10-27 21:06:30 UTC in AxCrypt - File Encryption for Windows
-
Hello,
Your results seem to indicate that the files and/or file system on your USB drive is severly damaged. It's hard to envision a situation where at least case '1' below is caused by an AxCrypt malfunction. It would seem that you should treat this as a case of a damaged device, and try whatever repair options are available to you for that.
In all honesty, it is seldom that much can be...
2009-10-16 09:48:10 UTC in AxCrypt - File Encryption for Windows
-
Hello,
To be perfectly honest - I don't think so. If the data is not written to the file, there is nothing to recover. It's also not possible to recover parts of the stream, even if there is data written at the end of the file - although it's more likely that the entire file is empty. You could check that with a binary editor.
The registry entry 'TryBroken etc' is still supported afik in...
2009-10-14 10:55:53 UTC in AxCrypt - File Encryption for Windows
-
Hello,
A "GUID Mismatch" error is usually the result of one of two situations: A file that was never properly written, or a file that simply is not an AxCrypt file.
The first case can typically occur when removing a USB-memory stick without using the "Safe Removal" function of Windows. In this case, the data is simply lost, becase the memory stick was removed before the data was ever...
2009-10-13 19:23:11 UTC in AxCrypt - File Encryption for Windows
