I wonder if this also works similar in a multi user system:

From the log I can see that GpgOL picks up the wrong "Sender" address. It thinks that you sent the mail yourself and then the mail address <> signature does not match. So it is not flagged as Trusted.

When we detect GnuPG > Version 2.1.15 Kleopatra now offers (and has it as default for ECC) to use cv25519 / EdDSA

Thanks for the report. The broken sentence came from an unterminated hyperlink. I fixed the spelling and the link.

I've started adding a workaround, but shelved it for now. Any workaround would not work for plain signed mails and would not be interoperable with other clients.

Sadly this is a known problem, the workaround is to unselect the mail and then move / modify it through the right click menu.

I'm not a fan of memoryhole. To say my criticism in one sentence: "Memoryhole is trying to sell the hide of the boar before it has been hunted."

This issue is not concrete enough to have some kind of "done" so ->invalid

This issue is invalid.

Thanks. Error is there:

That is weird, I've never heard of that before.

rW981a6fae5355 Fixes the problem with Kleopatra's config files.

Is it possible that your %APPDATA% directory is redirected? Maybe you are running into T3818 I also got "General Error" when trying to generate a key because of that bug.

What do you mean by "Does nothing"? The button should toggle and then when you send the mail kleopatra should show a dialog to select the signing / encryption keys.

With the attached commit gpgconf works. Key generation in Kleopatra also handles the case now that gpgconf does not work.

The underlying problem is that gpgconf does not work in such an environment.

Could you please try on the command line. (If you don't know how, see: https://www.wikihow.com/Open-the-Command-Prompt-in-Windows )