Ok, I'm not asked, therefore I set this to done, but not resolved yet, as I'm not sure if the gpg version might have an influence.

Gpg4win 4.4:
Contrary to the task description are:
a) In the certifications tab the "tags" column is shown by default
b) in the UID tab, the "origin" column is shown by default (only the "tags" column is hidden)

The only difference that you should see in the UI is that there is no longer a menu that pops up when you drop files, asking you what to do with the files. So I guess, if things works fine as you described them, you can consider the ticket done

This ticket description does not give me anything to test.

tested with Gpg4win 4.4

tested with Gpg4win 4.4

Better a new ticket for the rest, see T7441

Backported for VSD 3.3 / Gpg4win 4.4.1.

I'll backport this for VSD 3.3 / Gpg4win 4.4.1. Regression risk is minimal.

Backported for VSD 3.3.x / Gpg4win 4.4.1

I'll backport this because this issue is a really bad usability problem for people using the Windows Explorer integration to decrypt files. And the regression risk is minimal.

I think you are right, it is fixed. I tried it now again with Gpg4win 4.4 with several cards and it works as you describe.

Gpg4win 4.4:
When a keyserver is configured you can now check a box to directly upload the revocation there:

In T7273#195063, @ebo wrote:

We could discuss how to make this a bit more easy to parse visually, but that would be a new task.

Gpg4win-Beta-94:
Looks good, here the file was changed after the first two signed it:

with Gpg4win-Beta-94: about that speed on Windows, too.

Could be a bit more refined in the future, but this would be for another ticket.

With the fix, the dialog opens instantly (< 1 second loading time)

Gpg4win-Beta-94: ok

Gpg4win-Beta-94: done

Gpg4win-Beta-94: works

Gpg4win-Beta-94: works

With Gpg4win-Beta-94 now all is fine, even own deactivated certificates are now shown (using the "Disabled" filter) in bold font

Fixed in Gpg4win-Beta-94

Well, T6893 was removed from this release, at least for the windows builds, therefore this ticket can not be tested on windows for vsd33

Yes, much improved, changes as described in https://dev.gnupg.org/T6933#181791

tested with Gpg4win-Beta-75++

Gpg4win-Beta-75++

Gpg4win-Beta-75++

Checked with Gpg4win-Beta-75++

Cancelling the password window works know.

With gpg4win-beta-75++ tryiing to import a secret key results in no import:

Error on generate keys on card is now: "Failed to generate new card keys and a certificate: Wrong PIN"

Tested with gpg4win-Beta-75++:

works in Gpg4win-Beta-75++

works with Gpg4win-Beta-75++

tested with Gpg4win-Beta-75++

Fixed (for Gpg4win 4.4 / VSD 3.3) by patching Qt's Windows Vista style.

Backported for VSD 3.3

A bunch more improvements (for gpg4win 5.0):

This doesn't need to be verified with VSD 3.3 after it was verified with Gpg4win.

This was fixed in gpgme and is therefore automatically in VSD 3.3

This might fix the issue https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpg4win.git;a=commit;h=cf13e915581ca32e05e229cc54ef8e35753128e0

This fix is also in VSD 3.3

This is included in test installers since some time already.

This change is also used for VSD 3.3

Gpg4win-Beta-75: works

Name of the window is now "GnuPG Configuration Overview" and "gpgconf -X" is preselected and executed in the window.

Works, you now get an error message that the card can not be found.

This has been backported for VSD 3.3 and Gpg4win

This symptom can be explained by the nPth bug of T7386.

I guess it's now ready for testing