This guide explains how to fix issues typing in a VMware terminal. It allows a smoother experience during the deployment of a scanner or a information server.


It can happen that when you are deploying your LSS (scanner) or IS (Information System) on VMware, and trying to type anything within the virtual machine terminal (for configuration purposes), that it doesn't work. See the screenshot below:


The screen shows the deployment of a LSS. Sometimes, as mentioned above, it can happen that one faces issue to type within the terminal as the cursor is not visible in the terminal. 


The following solutions are proposed by VMware:

Common input problems and solutions

ProblemSolution
Pressing Ctrl+Alt to release the mouse and keyboard causes a laptop to suspend.By default, Workstation Pro uses Ctrl+Alt to release the mouse and keyboard. Some laptops use this same key combination to suspend the host machine. In these cases, try using Ctrl and Alt on the right side of the keyboard. Workstation Pro recognizes both sets of Ctrl and Alt keys, but laptops usually recognize only the keys on the left side of the keyboard for the suspend function.
After you press Ctrl+Alt to release the mouse and keyboard, the keyboard does not function properly within the host operating system.Occasionally, Workstation Pro causes the host operating system to lose keyboard events, which in turn causes the host operating system to detect that keys are being pressed when they are not.

If keys do not respond as expected after you exit Workstation Pro, they might be stuck in the host operating system. Press and release each of the modifier keys individually, including Ctrl, Shift, and Alt. If the keys still do not respond, press and release more special keys, including the Windows, Esc, and Caps Lock keys.


On Linux hosts, pressing Ctrl+Alt does not release the cursorThe modifier keys might be mapped under X (in Linux) in unexpected ways. For example, the left Ctrl key might be mapped to Caps Lock, or an Alt key is generating special keystrokes. Run xmodmap -- kim -- kp and submit a support request to VMware technical support that includes the output.


Source: https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-D677B10A-3590-460A-8141-709B4F8E4685.html


If after applying this fix it still doesn't work, please contact support@beyondsecurity.com.