1.8.13 (T8224) and 1.12.2 (T8114) are released

I once creates this task, which is probably a duplicate now: T7954: Kleopatra: Highlight focused cell in tables

In general, we don't show the key IDs. User ID + creation date will almost always uniquely identify all keys. (And only the fingerprint truly identifies a key anyway.)

Seems I forgot to note that icon removal works when resetting to defaults. And the VSD related Categories are no longer shown in Gpg4win. Tested now with Gpg4win 5.0.2, but I believe it was already ok in 5.0.0.

If Tobias remembered correctly, then https://dev.gnupg.org/T7334#193396 still needs to be implemented.

I've removed the sentence in the German de.po on master.

Windows 10 since some build number also has real Local Sockets which avoids the trouble with Windows ACLs.

ok, neither is a no-brainer, i see. But I would vote for the left to right order, i.e. the alternative you mention. This has the advantage that the card type is listed on the left side with which one can maybe better identify the card. In my example the type is "Yubico OpenPGP-v.3.4-card", I do not see the info that it is a Yubikey anywhere else. Therefore a blind user will only get that info up front if the left side is read first.

There is no handling for installing a currently in use libwinpthread-1.dll and a few others. That will require a reboot anyway and thus it is only done for the more common cases like gpgol and gpgex. Workaround is to reboot and try again.

PIPE_REJECT_REMOTE_CLIENTS is from windows vista and onwards. I guess that's good enough for us.

This seems to be a newer flag, although not stated in the docs.. Hart does not mention this in Windows Systems Programming either. I recall that I did extensive tests with Named Pipes and Mailslots to find a way to restrict access to local processes only. Sure you can use capabilities to restrict access but that is a pretty complex beast and easy to get wrong. It did not worked back then when I tested this with NT 3.5 or so. Thus our solution was to to use TCP where you can easily specifcy the listening port.

Citing the API documentation of CreateNamedPipe (https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-createnamedpipea):

One of the following remote-client modes can be specified. Different instances of the same pipe can specify different remote-client modes.

PIPE_REJECT_REMOTE_CLIENTS Connections from remote clients are automatically rejected.
0x00000008

This happens occasionally and is not related to upgrading from 5.0.1 to 5.0.2. It can happen when installing any 5.0.x version (including the betas) over an installed 5.0.x.

With -C <DIRNAME> option, where <DIRNAME> is not exist is OK.