We recently noticed problem at a customer site with creating the standard rsa3072 keys. It basically stopped working. A likely cause for this seems to be some anti-malware software slowing down file system calls. In the wake of this we looked again at our file locking strategy and found a few things which are not as they should be. For example the release of the lock before a Close call. Trying to fix this unfortunately caused other problems, thus a couple of fixes are needed.

If a high-contrast mode is enabled then Gpg4win 4.4 (and VSD 3.4) will use the Fusion style which works much better with high contrast than the Windows XP/Vista style with animations that was used previously.

(auto resolved due to the keyword "resolved" in the commit message)

The window was not reenabled on failure see 8d174d5

Reading the commit log message in rG6dc3846d7819: sm: Support creation of EdDSA certificates.
I created a file to keygen.

Key-Type: ECDSA
Key-Length: 1024
Key-Grip: 0286DCA85E771F64AB9FD9C89717369524D55471
Key-Usage: sign,encrypt
Hash-Algo: sha384
Serial: random
Name-DN: CN=dummy test nistp384

That is on purpose. With a signed mail you have at least a way to tell who sent the mail. An unsigned but encrypted mail can be send by anyone and you netter don't use HTML links there.

I updated the branch.

This happens only in the 64-bit builds, i.e. with Gpg4win 5.

We also discussed emails that can't be decrypted. They are due to implementation details just currently skipped. They will also be so in the future as an implementation detail.

(removed: wrong statement)

Note: I also activated Sign/Encrypt by default, if that matters