Closing this as invalid.

Ok, the behavior in gpg4win-5.0.0-beta413 @ win10 is the same (< 1s).
I can also reproduce the same behavior in other windows dialogs, e.g. in the explorer (changing the location address, clicking on the search input field).
So i'd also say, that this is a virtualbox or win issue and would just close this as invalid without further testing?

I'll also retest this with gpg4win-5.0.0-beta413. I think, this bug was different back then (no need to do it quickly). If it's gone there, too, it might have been a virtualbox or win bug. If it's still there, it might hint at qt/kde.

It turns out that the problem occurs if one clicks with the mouse quickly (< 1 s) after typing a character.

I was too fast with closing this, seems it is reproducible under special conditions. But not by me, here it works.

Me neither, neither on Win10 or 11. I tried the original description and https://dev.gnupg.org/T7943#208784

I can still reproduce this with gpg4win-5.0.1 @ win11

I cannot reproduce this with the released Gpg4win 5.0.1 on Windows 10 (VM).