I imported only a secret key file generated by "Backup secret key"

works. Including "Verschlüsseln".

See T6474 for the remaining issue.

The simplification works as described except in the following case for importing a private key:

File dialog and notepad now share the last used signature and encryption to self key. Works.

This works if the smartcard with the same private key is not connected, which it usually shouldn't be (outside of testing situations) so that's ok for me.
But I think we should inform the user what is done or isn't.
Currently we get in both cases:

gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg:                             unverändert: 1
gpg:              gelesene geheime Schlüssel: 1
gpg:            geheime Schlüssel importiert: 1

Which is not very clear in any case but in case the smart card is connected it is in fact wrong, there is no secret key imported, the keystub remains.

Ok, so this is not an issue for a standard user. Still I think "wrong PIN" should be given on the command line, too, and not only in the debugfile output.

works, at least for Yubikeys and Zeitcontrol cards

In Kleopatra an error window comes up in this case:

Kopieren des Schlüssels auf Karte fehlgeschlagen: 
Falsche PIN

works, a key with a revoked uid is accepted as VS-NfD compliant, VS-Desktop-3.1.27.0-beta44

The generate keys etc. actions in the keys part of the view are debatable. At least for VSD I think they should not be shown or greyed out for not VS-NfD compliant cards -> see T6786
(I think there were even algorithms offered for generation on card which would result in an error, but I won't investigate further at the moment.)

I already commented in T5836 which should be discussed here, instead:

The options for key backup+delete, delete and keep all work now, tested with VS-Desktop-3.1.27.0-beta44

Because of the imported certificates tab I mention T6447 and T6183 for the certify question. Closing.

gpg --edit-key; keytocard; save

work as expected.

The reported issue is definitively fixed, didn't test the rest yet

works

works

isn't T3456 the same issue?

my Yubikey works, too, if I disable PIV. With enabled PIV:

Test with GnuPG 2.4.1-beta76 failed with "error getting current key info: invalid name":

The crypto profiles have been removed in Gpg4win 4.1.1