Forum Replies Created
-
AuthorPosts
-
Hello Jonathan,
AxCrypt 2 opens all AxCrypt 1-encrypted files. However, we’ve seen a similar issue with some custom text file associations, specifically when .txt is associated with another program, whose only purpose is to launch a second program and then exit. This confuses AxCrypt who thinks the first program is the real program, notes that it has exited and thus concludes you’re done with the file and then remove it.
We’ll be doing something to fix this, but we’re also trying to avoid getting into the AxCrypt 1-trap of trying to ad-hoc second guess various applications weird behavior. In the end, we may simply never automatically remove files, but always use the clean up (the red broom) function.
Hello Infogroup,
Please sign in to your account at https://forum.axcrypt.net/ and create a Premium support ticket. If you don’t have Premium there either send an email to support att axcrypt dott net .
Please include screenshots of the error messages you are getting.
Hello Zorkoff,
Thank you for your very thoughtful views. They are certainly worth considering. We constantly review our terminology and try to be as consistent as possible.
We may indeed revert back to encryption / decryption, but it’s also very costly because we have another 10 languages to consider the translation for. So it’s not an easy decision.
Generally, we’ve tried to target end users in our terminology, and explain for technical persons what we mean with the “friendly terms”. Maybe we’re wrong.
Thanks Dennis!
Hello Drain0,
See the FAQ https://forum.axcrypt.net/support/faq/#lavasoft-crash . If you’re getting “File Encryption for .NET and Mono has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.” you have the Lavasoft Web Companion installed, whether you know it or not, I’m 99% sure. So far, we’ve had many users reprots this error and exactly 100% have finally found the Lavasoft component, even after initial statements of not having it, and after uninstall all works fine again.
Hello Drain0,
Just exactly what message are you getting when you say “New version stops working on my Windows 10 64bit PC”. Many users have “Web Companion” installed without knowing.
Hello Peter,
Don’t walk away from your computer without using a password protected screen saver, at the least! See https://forum.axcrypt.net/blog/leaving-computer-axcrypt/ for a longer discussion about this.
That being said, we will be adding the the timeout option, even if it does promote a false sense of security – if you walk away from a computer without locking it, you are *** anyway as far as security goes. In the end we’ll be spending less time implementing it than answering questions about it ;-)
Hello Rakesh CR,
AxCrypt 2 does not and never will run on XP I’m afraid. You’ll have to borrow a friends’ more modern system to decrypt the files. There’s a limit to how far back we can support things, and Windows XP is so dead that it just doesn’t make sense for us to limit us to that. Sorry.
Hello Zorkoff,
You’re entirely right – if you’re confused, we can do better. We’re continously trying to take input such as yours into account. Thank you!
“Password Reset” is not greyed when you’re online and not signed in – that’s the only situation that it makes sense. You can’t really “reset” an encryption password, and that’s not we do either. We do reset the account sign in password, but it won’t let you open any files encrypted with the pre-reset password. It can’t. It’s encryption after all.
It’s hard to be consistent, but we should not be using encrypt/decrypt in the how-to page. The intention is that we use secure/unsecure consistently, and in the technical section explain just exactly what this entails (i.e. encryption/decryption).
Not sure about the missing right-click, if that’s the case, but the most common reason is using a third party 32-bit shell (‘explorer’) in 64-bit Windows. AxCrypt supports both 32-bit and 64-bit, but not the hybrid of a 32-bit shell in a 64-bit Windows. The second most common is a broken or incomplete installation, followed by no installation – running the portable / standalone version instead.
Hello J,
A screen shot of what actually fails would help determine your problem. It’s not clear what version of AxCrypt you’re running now, nor what preceeded the current problem.
Two situations are common:
1) You’ve downgraded to version 1, and you can’t open some files because they were upgraded to version 2 automatically when you did use version 2.
2) You upgraded, set a password, opened some old files which were upgraded and re-encrypted with the version 2 sign in password. Then you came back, realized you’d forgotten the sign in password and issued a password *reset* for the account. Now you have some files which are encrypted with the forgotten password.
Hello Craig,
Right – or Andy can install 64-bit Xplorer2 (if there’s such a thing) or go mainstream and just use the built in Windows Explorer shell that comes with Windows. In both cases context menu (right-click) functionality is available.
Hello Zorkoff,
Ladislav responded well to most questions (thank you!) but I’ll add some info as well.
4) The reset password is greyed out when you are signed because it does not make sense to RESET your password when you know the old one. Then you do a password CHANGE.
6) We decided to do the auto-upgrade to version 1 by default, because this works well for most users. Before we did that, we had a lot of questions why a password was required twice all the time (which happens when the AxCrypt 2 sign in password is different from the AxCrypt 1 file password).
Hello Everone!
Some clarification is on order.
AxCrypt 2 still supports both 32-bit and 64-bit Windows.
The problem here is that Andy is using a 3rd party 32-bit shell (Xplorer2) on 64-bit Windows.
AxCrypt will install a 64-bit shell extension on 64-bit Windows (and a 32-bit shell on 32-bit Windows). But a 32-bit shell can’t load a 64-bit shell extension (makes sense, right?).
This mixed bitness scenario between Windows and 3rd party shells scenario will never be supported, and it’s somewhat of an abomination anyway… ;-) Sorry. I go with my initial suggestion – get with the times and go 64-bit all the way, your problems will not become less with time, only worse.
April 10, 2017 at 12:00 in reply to: Latest AxCrypt changed logos on encrypted files, but passwords invalid #6004Hello Wayne,
AxCrypt 2 will use the account and password you originally registered with AxCrypt 1 – possibly a long time ago.
If you do not remember the password to your account, you can always reset it. This is not a way to recover encrypted files! It’s only to allow you to sign in to the AxCrypt app and web. The new password will be used to encrypt new files. Go to https://account.axcrypt.net/Home/PasswordReset to do this, or you can also go there from AxCrypt with File | Options | Password Reset .
Hello Gordon,
Sorry about that, it’s something we’ll be improving.
For now, the easiest way to switch sign in identities is to click “Cancel” when prompted for the sign in password, and then go to File | Options | Clear All Settings and Exit
-
AuthorPosts