![]() ![]() I’ve not seen or heard of any problems with file-name collisions or special names. It helps understanding what has happened. I would really appreciate an snapshot report as I described above. There has of course been issues, but typically they will result in an error message. I’m a bit surprised about your descriptions – we’ve really not had any reports like yours. It addresses an issue with how files are handled, but typically you’d see an error message if you had that problem, and it’s been very uncommon. So now I have 35 files which can not be decrypred anymore.įirst of all – actually is the most recent version. MOV files which were encrypted yesterday can not be decrypted – Error Message = “Exception during processing of ”.Files which were encrypted yesterday can not be decrypted – Error Message = ” is not an AxCrypt file !.Today I noticed some more and even graver issues: Same problem for files like a-jpg.axx, where a.jpg already exists – decrypting seems to stop the complete process.If they are in the decrypt queue it seems like they are stopping/crashing the complete process System files – I guess some files (with ~ as prefix) where encrypted by accident.I will try to use the toolbar buttons instead. Progress bar – I guess you are right, encrypting from Windows Explorer is really very slow.The dialog issue has imo a low priority, but please check if the warning icon has issues (because it was not visible on my colleagues pc).Then in the Debug menu choose the Snapshot Report and follow the instructions. Enable Debug mode under File | Options | Debug. And, if I could bother you with a snapshot report after such a crash I’d appreciate it. ![]() I’m also concerned when you say ‘system files’ – are you attempting to encrypt such?Įspecially with #3 above in mind, I’d like to know what version you’re using. We’ve not received *any* similar reports.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |