It may be worthwhile to gather the complete diagnostic information. Please review Collecting diagnostic information for VMware Workstation (1346) - https://kb.vmware.com/s/article/1346. Has the logs been reviewed on the time the issue is occuring? Also, can you provide the step by step instructions to properly re-produce the issue? This may also help.
Weirdly enough it does work when you convert your VM(s) to shared:
Have lodged a support ticket under sourceforge.net: https://sourceforge.net/p/keepass/bugs/1962/
Ref Below Ticket:
Here's a video for your ref regarding the issue:
office: Unit 1-6, 511 Abernethy Road, Kewdale, WA 6105, AU
e: firstname.lastname@example.org web: rct-global.com
1 person found this helpful
We run into problems with some applications that inject key events because our process is running at a higher Integrity level, and Microsoft blocks such applications from receiving injected input from lower Integrity level applications. That's my guess for what's happening here, particularly since it was a Workstation 12=>14 break.
You can sometimes work-around this by either:
(1) Converting the VMs to shared (so that we'll open a lower Integrity remote console into the VM, rather than a higher Integrity local console, albeit at the cost of losing some features/performance)
(2) Launching Workstation or the 3rd party app as Administrator (so that they start with elevated Integrity). (Various combinations of which one to start as Admin might work here depending on the application.)
(3) Disabling System Integrity protection (although that puts you at increased security risk)
(4) Upgrading the to the latest version of Win10/Workstation
I don't recall having seen the keyboard version of this before, but a mouse event version was seen in this thread which might have some other quirks/suggestions:
We're working towards resolving these issues in a future version of Workstation, but getting all of these cases is more of an architectural problem than a simple bug at this point, so I can't predict a timeline for it. There might be something simpler we can do for this specific case as a bug fix in a minor update, but I can't make any promises.
Thank you BM
(1) definitely works as I've converted all my VM's annoyingly you get the Upgrade this VM hardware window and it goes no where, def a bug...
(2) also works so will have to run KeePass + VMware as admin all the time until you guys can squish this annoying bug as Auto-Type in KeePass is very handy with VMware..
Cheers for your help