RFC-5280 states in 4.2.1.3 for Key Usage:

The error code is: No Readers Available. With the latest version you should have seen that string.

Meanwhile we did some more tests on Windows and so you many want to try our betas at

Can you please clarify this point: If you run on Unix with --disable-ccid-driver, do you get the same behavior as on Windows?

Run gpg --debug ipc --card-status to quickly see the communication with the scdaemon.

Please try to verify on the command line (cmd.exe):

The curve is not defined to be used for ECDH (encryption); in fact it should in general only be used with the EdDSA
algorithm. You need to use "Key-Type: eddsa". Note that the EdDSA signing algorithm is different than the commonly used ECDSA signing algorithm.

Can you please port this also to 1.8?

You can't use ecdh with ed25519.

Please install the Gnome Key Ring prompter tool or use the plain GTK pinentry.

Please have a look at the log:

You are right. The problem is that in a development version we use an envvar to locate the programs, so there is usually no problem because the software has already been installed and the final test doesn't catch this. We should add a version check to all components to catch such problems.

Given that we don't yet support TPM for Windows you should go ahead and apply this patch. tpm should also be removed from the list of components.

6f03 = Data with specified length not supported.
Needs to be fixed in GnuPG :-(

is more important

You can't use an EdDSA as subkey for encryption. Encryption is the default for a subkey unless you provide key usage parameters. Yes, we could flag this as an error, but I won't give it high priority. I would anyway suggest to use

Thanks, that was right in time for this weeks 2.3.1.