Page 1 of 1

AESCRYPT DO NOT OPEN

Posted: Tue May 05, 2020 12:34 am
by anton56
AES DECRYPT DOES NOT OPEN AND NOT MAKE AN ENTRY FOR WINDOW 10 MENU.

I installed accrording to instructions, changing compatibility, and no open GUI.

also tried installing ina a diffrent disk not a SSD.

What can I do?

Re: AESCRYPT DO NOT OPEN

Posted: Tue May 05, 2020 1:42 pm
by paulej
If you right-click on a file and don't see the "AES Encrypt" or "AES Decrypt" menu option, then you probably installed a 32-bit version on a 64-bit machine (or vice versa). Verify the architecture type for your operating system.

Since you installed AES Crypt already, first uninstall it and reboot to ensure its fully removed. Then you can safely install the correct version.

Re: AESCRYPT DO NOT OPEN

Posted: Wed Sep 13, 2023 10:52 pm
by Winfried
Hello,

On a new Windows10 computer, I installed AES Crypt using AESCrypt_v310_x64.zip. I got no error, so I guess it's OK.

But when right-clicking on a file > X64 > AES Crypt, nothing happens. Likewise, when right-clicking on an .AES file > X64 > AES Decrypt, nothing happens.

Rebooting didn't solve it.

What could it be?

Thank you.

Re: AESCRYPT DO NOT OPEN

Posted: Thu Sep 14, 2023 5:04 am
by paulej
I've never seen that X64 menu before. Is that created by some other application?

Anyway, on 64-bit Windows you 10 or 11, one should run only the 64-bit version of aescrypt.msi. it will install a context menu similar to this. On Windows 10, it would be in the main list. On Windows 11, Microsoft moved it, so one has to choose "Show more options". There, one should see "AES Enrypt" or "AES Decrypt" as choices when right-clicking on a file.

Are you right-clicking on a file to get that menu? Do you have 64-bit Windows? (If 32-bit Windows 10, you need to install the 32-bit aescrypt.msi.)

Once selecting "AES Encrypt", a dialog box should open promoting for a password.

Re: AESCRYPT DO NOT OPEN

Posted: Thu Sep 14, 2023 7:08 am
by Winfried
I had an idea while waking up this morning :-) See if it was because I was still using an old, 32-bit version of Total Commander.

Turns out that's what it was: Trying the latest, 64-bit release works fine.

Thank you.