Forum Replies Created
-
AuthorPosts
-
August 28, 2018 at 22:34 in reply to: Ready to introduce AxCrypt across the organization… but can't contact support! #11148
Hello William,
I am glad you like AxCrypt!
The absolutely best way to get support, if you’re a Premium (Trial or paid) user is to use the Premium support form when you are signed in to the web site, https://forum.axcrypt.net/ .
You are also welcome just to send an email to support att axcrypt dott net . We typically respond within one business day. For non-technical issues, send an email to info att axcrypt dott net .
Hello William,
If the files have not changed, and the software has not changed… then I’m afraid it’s the password entered that has changed!
Please check for example that you don’t have num lock or caps lock, and also ensure that you’re not mixing up different passwords, it’s not uncommon.
Hello,
Thanks for the info. We’ll have to look into this and see if we can reproduce the behavior.
Hello Nikki,
A common cause for this is that someone has mistakenly encrypted the files using Windows Encrypting File System encryption. The easiest way to determine this is to look at how Windows Explorer displays the names. If the file names are displayed in green text, they are encrypted with EFS.
You then need to find who did that, and ask that person to decrypt them. If this is not the problem, it is indeed an access control issue – possibly on the share itself.
You can also try to copy them from the share to the local drive and see if you can access them there. This will help in understanding where the problem is – it’s not a solution, just a way of removing the network access issues from the equation.
Hello Deej,
It sounds like your iOS device is not synchronized with your Google Drive. AxCrypt does not talk directly to the drive cloud service, it replies on the drive app synchronization mechanism.
On the side note, the forums are using a wordpress-based forum software. We don’t have any personal information about you, but the forums support something called a gravatar – and if you see yourself here, it’s because you have previously authorized this connection. See http://en.gravatar.com/ for details. It’s not something we do, it’s something you’ve done to allow any other supporting platform access to your ‘gravatar’. Presumably you can remove yourself from there.
Hello Ramon,
Browse to http://www.axantum.com, klick the logo at the top left, and then select Download in the menu. (We’ll make this a little easier, but then again we don’t really want to encourage the use of obsolete, unmaintained software…).
Hello Michael,
Can you be more specific about how it is not working? What do you do, and what happens? Do you get an error message? If you can post a screen shot it helps a lot!
Hello Jon,
Backups are always essential for essential files. With, or without, AxCrypt.
Are you using AxCrypt 1.7 or 2.x ?
August 23, 2018 at 17:47 in reply to: Can not open my encripted file after Windows 10 restore #11116Hello Sep,
I am happy it worked out for you! Good luck.
Hello Jamie,
That’s an interesting scenario… There is always a problem with servers and long-running processes with credentials.
Right now we don’t support this out of the box I’m afraid, but it could probably be added relatively easily – *if* you are ok with storing the credentials in clear text somewhere on the server. Either directly in the startup command line arguments, or in an environment variable.
In the future we’ll support use of some form of credential store or encrypted credentials, but right now we don’t. The above can be implemented relatively easily, I think.
August 20, 2018 at 08:10 in reply to: Can not open my encripted file after Windows 10 restore #11079Hello Sep,
The most common reason for decryption problems after a Windows restore or re-installation is that the file is (sometimes also) encrypted with Windows Encrypting File System, EFS. This is typically indicated by the file name being shown with green text in Windows Explorer, and the error message ‘Access Denied’.
In your case, you say you get “wrong file extension”, but say it is “.axx”. This can be caused for example by manual renaming of a file, while at the same time having file extensions hidden in Windows. The actual name might then be “My File.axx.txt” – but Windows only shows “My File.axx”.
Please send a screen shot of both the file in question in Windows Explorer, as well as the AxCrypt windows including the error message you get.
Hello Shawn,
Under Options, enable ‘Debug’. Then in the Debug menu, chose ‘Try Broken File’.
Hello John,
What version of Android are you using? Can you send screen shots of the screens you get when you try to open it?
August 17, 2018 at 11:48 in reply to: Previously encrypted files won't open after AxCrypt premium trial #11065Hello Peter,
This means the file in question was *NOT* encrypted with AxCrypt 1.x, and thus *can’t* be using a key file, since version 2 does not use them (except as explained above to open legacy encrypted files).
So here it’s just a question of knowing the password used…
Hello Tim,
Yes, I agree. It’s not very helpful. But it is truthful. We *will* improve both performance and progress display. Will you get a new version with that done in the next 29 days? Probably not. Sorry.
We work issue-by-issue, and re-prioritize essentially daily. When we either have ‘enough’, or something critical we need to get out, then we go through the release process with regression testing, release documentation etc.
-
AuthorPosts
