[SvanteSpectator]

Hello Aitch,

Please try again. We had a minor server issue that has now been addressed.

[SvanteSpectator]

Hello yann,

Please try again. We had a minor server issue that has now been addressed. It has nothing to do with your original issue.

[SvanteSpectator]

Hello Michael,

Please try again. We had a minor server issue that has now been addressed.

[SvanteSpectator]

Hello Brian,

Please try again. We had a minor server issue that has now been addressed.

[SvanteSpectator]

Hello Christine,

For one thing, you’re actually using a fairly old version. But do try again, we had a minor server issue that has now been addressed.

[SvanteSpectator]

Hello Travis,

We need more information. Can you please follow the instructions for step #2 at http://www.axcrypt.net/blog/send-complete-error-report/ .

[SvanteSpectator]

Hello yann,

Sorry for not responding instantly. Please understand that these are forums for free support of a free software.

Here’s what’s happened (all times are UTC, you are apparently in UTC-5, so subtract 5 hours for your local time):

2016-10-03 12:54:38 – You download AxCrypt.
2016-10-03 12:59:29 – You set your first password.
2016-10-03 13:07:xx – You encrypt the files in question.
2016-10-03 14:06:22 – You try to sign in again, but fail because you did not remember the password.
2016-10-03 14:08:18 – You give up trying to remember the password, and reset the password to your second password.

So, when you say “I need a password that I’ve never chosen before” this is unfortunately incorrect. You chose it at exactly 2016-10-03 12:59:29. Then you chose another one, which does not work for your files, at exactly 2016-10-03 14:08:18 .

You need to remember what this first password was, since that’s what your files are encrypted with!

Sorry, but this is a very clear-cut case of a forgotten password.

 

 

[SvanteSpectator]

Hello Waldemar,

Unforunately the old app was broken by iOS 9 already. But, we’re working on a new app, so if you can just survive for a month or so we should be getting there.

[SvanteSpectator]

Thank you! Please follow the steps for #2 here: http://www.axcrypt.net/blog/send-complete-error-report/ , AxCrypt configuration files and send me the files.

[SvanteSpectator]

Hello Jasnick,

This typically indicates a very bad corruption of the file, or that it simply is not an AxCrypt file.

The most common reason is that the file is on a USB drive, and it was removed from the computer without using the Windows Safe removal function.

[SvanteSpectator]

This would be a new feature that we could have. We don’t have it yet, I’m asking if it would solve your problem.

[SvanteSpectator]

Hello Mathew,

It sounds like you’re saying that you encrypted a file and then shared it to a recipient. In this case the recipient can’t open it of course.

You must add the recipients email to the list of users shared with using the key sharing feature. Right-click the file in Recent Files view, and select the Share Keys function.

[SvanteSpectator]

Hello,

Not for the first time after you install the software, no. The user can always do so before entering the password though.

Please be aware there’s a reason for the choice to display it! Most users will not be entering the password with a lot of watchers, and most users will start by setting the password. In this case it’s best to actually display the password, because it reduces the risk of mistypes.

[SvanteSpectator]

Hi,

There’s no such option yet. I’m asking if there was such a registry setting, would it solve your problem? Can you set such an entry using your group policy or whatever mechanism you are using to distribute AxCrypt to your users?

[SvanteSpectator]

Hello François,

Right now, we don’t have the option to disable version update checks. I see the problem though in a group policy deploy environment.

Would checking a registry key (that you would create) to disable this work for you?

[Author]

Posts