I see no commits that change the behaviour or do the migration. Then this is not fixed. To clarify. For me this issue is about General config files of KDE / Qt. Not only about the kleopatragroupsrc Since the kleopatragroupsrc was fixed in the last release already.
In the state I left it for VSD 3.3 (master) qt.conf is only written for Gpg4win. And not for VS-Desktop. So testing with Gpg4win has different results. This was the underlying reason since qt.conf was written with FileWrite and not packaged. I only changed that in Gpg4win master.

With the new patch you get this now:

[GNUPG:] KEY_CONSIDERED F40ADB902B24264AA42E50BF92EDB04BFF325CF3 1
[GNUPG:] ERROR add_adsk 53
gpg: key "F40ADB902B24264AA42E50BF92EDB04BFF325CF3!" not found: Unusable public key
gpg: Did you specify the fingerprint of a subkey?
[GNUPG:] FAILURE gpg-exit 33554433

Yes, gpg logs "invalid ADSK ... specified", but it doesn't emit a status error. This needs to be changed in gpg.

Tested with VS-Desktop-3.2.94.2-Beta.
Works as expected on the cli.

works for VS-Desktop-3.2.94.2-Beta (Beta for VSD 3.2.4)

Test with gpg4win-Beta-50 shows the same as described in the last comment.

tested with gpg4win-Beta-50:
works as described in https://dev.gnupg.org/T6866#179915

Test on a dedicated Windows box (T 460, i5-6300U@2.40GHz, harddisk):

gpg4win-Beta-50:
Columns are now displayed as expected with a fresh installation, too.

Tested with gpg4win-beta-50:
Adding a subkey works, its possible to add A, E or S subkeys with different algorithms and expiration dates.

I knew that we'd need something like D604 when I saw rM409e31458227, but then I forgot about it. :/

Looks good! Thanks!

closing this ticket as duplicate as adding and changing expiry works.
Revocation of a single subkey is not yet possible in Kleopara, though

should be fixed with D604

As we now have tabs for the subkeys this task is obsolete, really. Its useful as a parent ticket though.

Overall effect of these changes tested on a small Windows VM is only 47 -> 26 seconds. Did also tests with --kbx-buffer-size but that does not make it better than the default, either.

Porting to 2.2 was straightforward - we won't give it an extra QA run.

We won't fix that for 2.2.

The OID is used for fingerprint computation, which complicates things.

gpg4win 4.3.1 was with keyboxd, too. And vsd33 is only to mark that it would need to be backported for the next release (if this is a Kleopatra issue)

Given that this only happens if keyboxd is used I doubt that this is relevant for VSD 3.3.

This happens only if keyboxd is used because then Kleopatra doesn't notice any changes in GNUPGHOME and therefore doesn't run a key listing.

gpgme should handle lists correctly. In Kleopatra those options are not shown in the configuration dialog because they are GC_LEVEL_INVISIBLE, i.e. Kleopatra can read them programmatically but they are not shown to the user.