mysterylie Tracker

Re: Workstation 17.5.0: (enhanced?) keyboard driver problem

mysterylie — Mon, 06 Nov 2023 14:16:39 GMT

Yeah, I turned off the enhanced keyboard and used the 'Change/Modify' option in the installer to (attempt to?) remove it completely but the issue remained after a few reboots for good measure. It does seem that disabling this works for at least some people, so maybe we've got two variants of the issue.

Re: Workstation 17.5.0: (enhanced?) keyboard driver problem

mysterylie — Mon, 30 Oct 2023 16:51:43 GMT

Fascinating, thanks for the info. Do you know how I can disable it once and for all? Not seeing details in the VMWare announcement or docs about how to disable it, they basically just say "if you're using it VMWare Workstation Pro will work".

Microsoft's own docs just point to the thing I used. I've also run the command these mention.

Re: Workstation 17.5.0: (enhanced?) keyboard driver problem

mysterylie — Mon, 30 Oct 2023 13:17:09 GMT

Yeah, fair point. I meant that all the boxes next to Hyper-V are unchecked in the "Turn windows features on or off" dialog.

Re: Workstation 17.5.0: (enhanced?) keyboard driver problem

mysterylie — Mon, 30 Oct 2023 12:22:42 GMT

I'm downgrading, too. You can find the file on your system (assuming you didn't prune it) starting with: VMware-workstation-full-17.0.2

I never had Hyper-V enabled (previous issues with VirtualBox had me turn that off years ago). I _did_ install the enhanced keyboard driver because I, like many others, thought enhanced = better. I think this is not the case. However, even after removing the keyboard driver (which was a real pain because you need admin rights to modify things, and the control panel > add/remove programs doesn't give you this by default) and rebooting the issue persists.

Specifically, I'm running into this issue across 3 debian-based VMs. Everything works normally for a few minutes but then it looks like I have an infinite key glitch where the same character is repeated until I hard-stop or reboot the machine. I caught this by being in a terminal when it happened, but otherwise it just looks like everything is frozen and no input works.

Rolling back has solved the issue completely (and I shan't be installing any "enhancements" again any time soon!)