No, I have no admin rights on that computer: I installed the portable version, too. I saw that the previous version had been uninstalled before installation.
On a different computer I tried to reproduce the situation where GPG4WIN had been installed the standard way. I did not see the effect there. However when upgrading I got a message that the c library could not be written; that was because some Kleopatra windows was still open. After manually closing that, a retry was successful. Other software installers close the application before trying an uninstall or update, however.

Just to be clear: You originally installed it as a portable applications and then you also installed a new version in the standard way?

after https://dev.gnupg.org/rW14d86c01819ef3ddbc7f03b34e821e367cea3b02 only qrencode is left:

currently not testable. some urls in download.sh are broken (404):

looks good to me on gpg4win-5.0.0-beta190@win10

Unfortunately, the attempt on my end still fails. The MSI package was successfully built; however, testing installing it on a Windows host resulted in garbled UI text and a bunch of errors.

Possibly related upstream bug:

light.exe : error LGHT0216 : An unexpected Win32 exception with error code 0x65B occurred: Function failed

I did not run the full tests becaue those would take some hours but one test case using the genhashdata tool from the libgcrypt test suite gives the correct value (see genhashdata.c source)

the included tools are intended to bootstrap things and are not optimized in any way. We don't run large data test either. Someone will look into it, thoigh. A better way is to use

Is not a GpgOL bug.
Full functionality will be possible with GpgOL/WEB.

In T6883#199155, @ebo wrote:

I guess this is done if QT6 versions have a pinentry?

I guess this is done if QT6 versions have a pinentry?

This even happens with native Windows applications thus normal priority. Users need to watch the taskbar for blinking items.

This is very similar to T5780 except that it concerns a different operation and thus a different window. The fix is likely the same as for T5780.

Okay. We now replace the standard Breeze icon of kleopatra with the red head for vsd and with a new blue head for gpd. The replacements are used for the About action and in the About dialog, but kwin (X11) insists on using the standard icon as window icon. And the system tray also shows the standard symbolic Breeze icon instead of the replacements. strace shows that the replacement icons embedded in the AppImage are loaded. No idea why kwin and the system tray still use the standard icons.

FWIW, for gpd and vsd we should use a different icon (blue head for gpd and red head for vsd)

Kleopatra with Breeze style:

I did a quick test with a test user running a Wayland session and the AppImage works now.

Needs to be tested/verified by other developers. In short you do

./autogen.sh
cd packages
./download.sh
cd ..
./build.sh --appimage --builddir=...

If you omit the --builddir=... option then ~/b/SRCDIRNAME-appimage will be used.

Building an AppImage including Kleopatra and Okular works now (again) in the gpg4win-5-branch.

aheinecke: Yeah, but I did quite some changes to build.sh for a real out-of-source build (w/o copying files)

Just so that its not overlooked and you are meaning something different. But I had the Qt6 / KF6 branch working with the --appimage parameter.

Thanks for that info. I tag it as FAQ and change the subject in case someone searches for such a problem.

After a lot of digging I finally found the problem. It's actually not Gpg4win/GnuPG, but it's the Bitwarden desktop app. They recently added support for it to function as an SSH agent, and even though I have not enabled that feature, it's hijacking the socket anyways. When I close Bitwarden the issue disappears. The issue is logged in bitwarden/clients#13150.

@werner Thank you for the response. Is there a nightly build or similar that I can grab from somewhere to see if using the latest master branch solves the issue?