Latest KeePass 2.45 does not work with Latest VMware 15.5.2
A lightweight and easy-to-use password manager
Brought to you by:
dreichl
Hi Dominik,
I've just realised this but even the latest version of KeePass 2.45 does not seem to work with the latest version of VMware 15.5.2 when it comes to Auto-Type, it's really weird like it has worked intermittently before but now I can't get it to work..maybe when I was on 15.1 or something.
Anywhoo can you please fix this bug as this is a very much requested feature in KeePass 2.XX
Even if you have a development build I could test out, that would be appreciated?
Cheers
Which VMware client?
Is it this issue?
cheers, Paul
https://www.vmware.com/products/workstation-pro.html
No it's VMware Workstation Pro that's having the issues not Horizon
When did it last work? What version of KeePass / VMware worked?
cheers, Paul
Good question Paul,
That's what I'm trying to determine by back uninstalling versions of VMware and versions of KeePass to try and get a working combination.
At the moment it seems I can't get any version to work with auto-type:
KeePass 2.43 + VMware 15.5.0 Auto-Type Broken
KeePass 2.43 + VMware 15.5.1 Auto-Type Broken
KeePass 2.45 + VMware 15.5.2 Auto-Type Broken
There appears to be alot of VMware 15.X.X version's that are funny with KeePass Auto-Type...?
Still got more testing to do, so will keep you posted..
Thinking of going the other way by using VMware's old WSX plugin for Chrome and just using KeePass that way?
Thanks
Last edit: Jarrad Welsh 2020-05-17
Actually I might just go down the path of vSphere Web Client and test KeePass instead..
Trying to get it working with this plugin, KeePass 2.45:
https://rdc-keepass-plugin.appspot.com/
VMware Workstation Pro 15.5.1
Last edit: Jarrad Welsh 2020-05-17
OK weird one, I just converted one of my VM's to Shared for the WSX web console and didn't get anywhere with that, but interestingly enough, KeePass 2.45 seems to work now for VMware 15.5.1? when I try KP 2.45 on my other VM that's not converted to shared it fails? Any ideas?
Don't know the difference between shared and not.
Have you checked the VMware support forum?
It is worth testing with KeePass V1 portable as well. Gives us more information.
cheers, Paul
I've create a ticket ref another under their Forums:
https://communities.vmware.com/thread/633870
I thought at first it was to do with hardware comp but can't work it out, don't know what's in the shared VM that makes Auto-Type work?
Anyway heres a video for your ref:
Does this setting for VMware WS Pro interfere with KeePass Auto-Type?
2 Workaround(S) here:
https://communities.vmware.com/message/2950697#2950697
As mentioned in the VMware forum, newer VMware versions run on a higher integrity level than KeePass and thus auto-type doesn't work, because Windows doesn't allow regular processes to send input to higher integrity processes. In my opinion, the best solution would be if VMware lets its instances run on the regular integrity level again, like in previous versions. As a workaround for now, you can run KeePass with administrative rights, which grants a higher integrity level.
The fact that KeePass must run with at least the rights of the target application for auto-type to work is already mentioned on the auto-type help page [1]. However, it's of course not obvious that this is the issue here. As VMware Workstation is a popular software, I've now added a sentence on the help page that VMware Workstation is an example for this.
Thanks and best regards,
Dominik
[1] https://keepass.info/help/base/autotype.html