Kleopatra (Gpg4win 3.0.0) does not import or create keys

Under Gpg4win 2.3.4, I was able to create and import keys. I installed Gpg4win 3.0.0 over 2.3.4, and now I can do neither. When I try to import a key, it completed without an error, but the key does not appear under any tab. When I try to create a key, I get all the prompts and it freezes on the “Key Pair Creation Wizard | Creating Key Pair …” dialog box (I let it stay for an hour before pressing “Cancel” as I think 60 minutes is sufficient time to create a key pair).

Under 2.3.4, I centralized my keyrings, and “%appdata%\gnupg\gpg.conf” has

keyring …\pgp-keyrings\pubring.pgp
primary-keyring …\pgp-keyrings\pubring.pgp
secret-keyring …\pgp-keyrings\secring.gpg
trustdb-name …\pgp-keyrings\secring.gpg

The files are present in the centralized directory, and my account has full control over them.

Kleopatra (under Gpg4win 3.0.0) does allow me to view the keys currently there, though.

Dear John,

sorry to read that you are having issues with Gpg4win!

Assuming that you are talking about OpenPGP keys and importing

The keyring settings in gpg.conf maybe a problem, as GnuPG 2.0 to 2.2
changed the way OpenPGP keys are saved. And you trustdb-name setting looks
bad as well.

For diagnostic reasons could you try to import a pubkey on the command
line or create a key-pair there?

Maybe a way forward for you could be to save the files (a backup is always good as well)
then remove the keyring settings in gpg.conf and import the old files. If you can you could export the trustdb with the old version.

Best Regards,


Thanks for the reply. I was able to both import keys and create the keys via the command line. At the very least, I have a work-around.

You wrote that OpenPGP changed the way n which keys are saved. Does it still allow for a centralized repository location, of would I have to create the keys on each of the machines that will be using PGP. If I can still use the centralized directory, how would I specify where the directory is?

Let me try exporting and importing.



Hi John,
good to know that you have a work-around!

Regarding your question about a centralized place for the keys:
If you are thinking of using a network “drive”, it shall be possible.
One way would be to place the complete GNUPGHOME on a network drive
and there are probably other ways to specify where to place the directories
where the pubkey and secretkeys are used. Without trying I cannot say
you could look up the GnuPG documentation about in-depth configuration

Best Regards,