Lost Functionality with AxCrypt.App.Windows_3.1.6.0

[Gary]

<p>I have been using the Premium version of Axcrypt for a number of years. After installing v.3 for Windows 10, I have lost functionality with opening encrypted files in Windows Explorer. Previously, I could double-click an encrypted file and if I was not already logged into the app, I would be prompted to. Once logged in, the file would decrypt and I could access it. Now, if I double-click the file nothing happens. <br />Also, when I right click on the file, and I choose ‘Axcrypt’ from the Windows Explorer menu and choose either ‘Open’ or ‘Decrypt’, I get the same result. Nothing happens. <br /><br />I have uninstalled and reinstalled Axcrypt and the issue remains. <br /><br />I am running Windows 10-64bit with OS Build: 19045.6466. </p>

[geometry dash]

Hello, this sounds like a Windows Explorer integration issue in AxCrypt v3. Try repairing or reinstalling AxCrypt, ensure Explorer integration/file associations are enabled, and verify you’re using the latest version. If it persists, contact AxCrypt support as it may be a v3 bug.

[Linda Lundberg]

geometry dash wrote:

I have been using the Premium version of Axcrypt for a number of years. After installing v.3 for Windows 10, I have lost functionality with opening encrypted files in Windows Explorer. Previously, I could double-click an encrypted file and if I was not already logged into the app, I would be prompted to. Once logged in, the file would decrypt and I could access it. Now, if I double-click the file nothing happens. Also, when I right click on the file, and I choose ‘Axcrypt’ from the Windows Explorer menu and choose either ‘Open’ or ‘Decrypt’, I get the same result. Nothing happens. I have uninstalled and reinstalled Axcrypt and the issue remains. I am running Windows 10-64bit with OS Build: 19045.6466.

I think you should try resetting AxCrypt’s file associations by reinstalling the shell extension or setting .axx files to open with AxCrypt again. If that doesn’t work, the issue is likely specific to v3, so reverting to the previous version or contacting AxCrypt support may be the best option.

[Author]

Posts