Kleopatra was successfully installed on my PC (running Windows 7, 64-bit). I successfully created a new certificate/key pair. I can also successfully decrypt a file from within Kleopatra via the "File" menu (i.e., File, Decrypt/Verify Files, then pick the file, then key in passphrase). However, the "Decrypt/Verify" choice is not available to me when I right-click on the encrypted file from Windows Explorer, which is the way we used to do this in the 32-bit world using PGP. I should be able to open an Explorer window, go to the directory containing the encrypted file(s), then right-click --> Decrypt/Verify. That choice isn't even available. According to the documentation in the GPG4Win compendium, chapter 18 says I should be able to do this using Kleopatra. Here's the URL: http://www.gpg4win.org/doc/en/gpg4win-compendium_24.html In the subsection "Decrypting a file" it shows a screenshot immediately after some text that says I can choose Decrypt and verify in the Windows Explorer context menu. Your help in resolving this problem would be greatly appreciated. Reproducible: Always Steps to Reproduce: 1. Open Windows explorer & find folder where encrypted file is located. 2. Select the file, then click with right mouse button. 3. No choices relevant to Kleopatra and/or GPG (such as "Decrypt/Verify") are available. Actual Results: The choice of "Decrypt/Verify" was not available. Expected Results: The choice of "Decrypt/Verify" should be available, and I should be able to decrypt a file from the Windows Explorer window. Computer configuration already noted above.
Hi, Thanks for your report, but the explorer extension of gnupg (gpgex) is currently not available for x64 Systems. There is currently work going on to change that and a new Version with x64 support should be available ~ June. Please monitor the gpg4win-announce mailing list for an announcement of a version with that feature. All this has nothing to do with KDE / kleopatra and a well known issue in gpg4win so I am closing this as invalid here to avoid clutter in this bugtracker. (Although the bugreport contained valid information) Regards, Andre