Created attachment 110218 [details] screenshot 1 I have Kleo on my old laptop (runs Win 10) which has worked perfectly fine without a hitch. I now have a new laptop and I am trying to import my existing keys onto my new system (again Win 10) however everytime I try to import it goes through the same process and ends up telling me "Secret Keys NOT Imported: 1" (see screenshot 1) No matter what options I check when exporting my keys from my old machine the files that I get just simply won't import- same message everytime. Alright, I think. Maybe I'll just create a brand new key altogether and update others to the new public key. However, everytime I create a new key pair it runs through the process as if everything is just fine and when it comes time to create a backup of my newly generated key pair I get the message "Invalid UserID" (see screenshot 2) and then the keypair simply doesn't show up under my list of certificates in Kleopatra as if I never clicked the Create New Pair button. Kleo simply brings me right back to the Welcome page saying to begin I need to either Import or Create a New Key (screenshot 3) I read on forum that perhaps I should try using GPA instead to create the key. Whenever I open GPA I get the error "GPGME library returned an unexpected error. This could be an installation error" (screenshot 4) and once again any attempts at importing/creating keys are futile. I've fresh installed the newest version (3.0.3) and every other version going back to 3.0.0 to see if maybe there's an issue with the current update but nope, each fresh install gives me the exact same errors every time. I'm beginning to suspect it's not a bug with your software but some background process on my machine that is prohibiting a successful install but I've no idea what it could be. Running the .exe installation as an Admin doesn't help. I've also ran the self-test to check for errors but everything appears to be fine as per screenshot 5. Please if you've any idea on how to fix this it would be greatly appreciated!
Created attachment 110219 [details] screenshot 2
Created attachment 110220 [details] screenshot 3
Created attachment 110221 [details] screenshot 4
Created attachment 110222 [details] screenshot 5
This looks like: https://dev.gnupg.org/T3507 There was a possible keyring corruption that could happen on fresh installations of Gpg4win-3.0.0 and 3.0.1. Please shut down kleopatra and then move away the folder %APPDATA%\gnupg and try again. With a fresh directory and Gpg4win-3.0.3 it should work fine. I'm marking it here as "needsinfo fixed" because I think it was fixed with the fix for T3507. Please leave a comment if moving away your gnupg homedir dir not help.
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.