June 16, 2016 at 04:06 #3480
When attempting to clean open files, as well as when signing out, I get an error that an exception occurred – part of the path to the temp file is missing.
Checking, I found that the temp folder with the gibberish name was already gone. Instead of throwing an error, I imagine the software should just skip it. Now it won’t let me clear the other open files.
Thanks!June 16, 2016 at 09:03 #3485
Thank you for reporting this.
Can you send a screen shot of the error message please?
SvanteJune 16, 2016 at 14:34 #3491
YehudaJune 19, 2016 at 18:57 #3537
Everytime my computer locks, it tries to clean the open files and throws this error.
Thanks!June 19, 2016 at 21:07 #3538
We’ll be looking into this the coming week! Can you tell us a little more:
– What Windows-version
– What are you opening PDF files with?
– What version of AxCrypt are you running?
– Can you please use the function File | Options | Debug and then Debug | Open Error Report Snapshot and follow the instructions you should see then?
SvanteJune 20, 2016 at 03:56 #3540
Windows 10 64-bit
Opening PDFs with Adobe Acrobat 11, but I’m getting the same error for Word documents.
Thanks!June 20, 2016 at 08:48 #3542
We received the stack trace, thank you. Would you mind also sending the ‘FileSystemState.txt’ file from %localappdata%\AxCrypt ? It does contain the names of the encrypted files (i.e. the .axx-files, not the originals, but if you have not renamed they are of course very similar), otherwise there’s nothing sensitive in it.
SvanteJune 20, 2016 at 14:35 #3547
Sent – thank you so much!
I deleted one entry from the file.June 22, 2016 at 18:03 #3591
Update: I uninstalled AxCrypt, shredded my %localappdata%/AxCrypt folder, and reinstalled AxCrypt. It seems to be working now, with one caveat.
I tested the following with Microsoft Word 2016 (32-bit) and Adobe Acrobat 11 (32-bit) on Windows 10 64-bit:
- Open a non-encrypted file
- Open an encrypted file
- Close the encrypted file
AxCrypt does not recognize that the file was closed until all files open in that particular program are closed. Furthermore, clicking “Clean Open Files” does nothing. I am no expert in these areas, but it seems that both of these programs only have one process running for all open documents. If AxCrypt monitors the PID, this would explain what is happening.
From what I remember, version 1 did not have this drawback, but rather recognized when the specific document was closed. This is problematic, as now one can no longer assume that when an encrypted file is closed it’s decrypted version is wiped.
Thank you!June 22, 2016 at 19:07 #3593
Hello Yehuda, we’ll still be investigating your issue. There was no need to uninstall, deleting the %localappdata%\AxCrypt folder would have sufficed.
Anyway, yes you’re right – AxCrypt 2 has the behavior you describe. The reason is that although AxCrypt 1 was sometimes ‘smarter’ – it also failed worse. AxCrypt 2 has complemented a simple detection mechanism, with the ‘clean up’ broom. Which should work, if you in fact have closed the application. Otherwise, it will not.