Keyboard problems with Parallels 12

R

Rick_B

Junior Member
Started having a problem with keyboard behavior in Parallels 12. This behavior did not exist in Parallels 11. The quick description is that Shift, CapsLock, and Control keys don't always pass through when I'm connected to a Remote Desktop session from a Parallels 12 VM. This happens with both Windows 10 and MacOS guest VMs, it happens under this arrangement on my MacBook Pro and Mac Pro. There seems to be a keyboard interrupt problem that is conflicting with Remote Desktop. To recreate, run a Windows 10 vm on a MacOS Sierra host. In the Windows 10 vm, open a Remote Desktop session to a terminal server. When connected to the terminal server, just open any text editor and try out exercises using Shift, ShiftLock, and Control.
 
Last edited:
Another update to this, it appears to work fine when using Windows 7 as the VM, then doing RDP into the Win2008 server. I also verified that Parallels 11 actually exhibits the same behavior as Parallels 12, so it's maybe pointing more to a Microsoft RDP issue when using a Parallels VM, with either MacOS or Win10 as the guest VM. Bloody heck, now let the finger pointing begin, I guess. I also tried uninstalling parallels tools from the Win10 guest, then RDP into Win2008 server, problem with Shift and Control keys still happens. Yet when I RDP into the Win2008 server directly from my MacOS host, without using a VM, Control and Shift keys work fine. So since it's happening with both Parallels 11 and 12, I'm going to suggest that this may be a Microsoft bug, but one that only occurs when doing RDP to a TS through a Parallels guest VM. Maybe I'll try setting up a vmware test with Win10 guest and see how that behaves.
 
Dinesh@Parallels said:
Hello @Rick_B ,
Did you try to change the mouse settings to ''Optimize for games" and checked the behaviour?
Click to expand...

Hi, thank you for your post, Dinesh. I have just stumbled upon some luck with this, at least in my Windows based guest VMs. The RDP setting on the Local Resources tab, Keyboard section, Apply Windows Key Combinations, I set to "On this computer", and now the remote terminal server behaves correctly with Shift/Control/ShiftLock keys. So I just tried my MacOS vm, connected via RDP to the remote server, and the only thing that doesn't behave right is the ShiftLock. I can't find any other settings in the RDP client for MacOS that could address this. It could be a Microsoft issue, which I'll assume at this point. Microsoft has been releasing lots of patch updates for the Mac version of RDP, which makes me more suspect of the RDP client.
 
Rick_B said:
Hi, thank you for your post, Dinesh. I have just stumbled upon some luck with this, at least in my Windows based guest VMs. The RDP setting on the Local Resources tab, Keyboard section, Apply Windows Key Combinations, I set to "On this computer", and now the remote terminal server behaves correctly with Shift/Control/ShiftLock keys. So I just tried my MacOS vm, connected via RDP to the remote server, and the only thing that doesn't behave right is the ShiftLock. I can't find any other settings in the RDP client for MacOS that could address this. It could be a Microsoft issue, which I'll assume at this point. Microsoft has been releasing lots of patch updates for the Mac version of RDP, which makes me more suspect of the RDP client.
Click to expand...
Hello Rick_B, please write back to us if you have any further questions and we will be happy to help!
 
Rick_B said:
Hi, thank you for your post, Dinesh. I have just stumbled upon some luck with this, at least in my Windows based guest VMs. The RDP setting on the Local Resources tab, Keyboard section, Apply Windows Key Combinations, I set to "On this computer", and now the remote terminal server behaves correctly with Shift/Control/ShiftLock keys. So I just tried my MacOS vm, connected via RDP to the remote server, and the only thing that doesn't behave right is the ShiftLock. I can't find any other settings in the RDP client for MacOS that could address this. It could be a Microsoft issue, which I'll assume at this point. Microsoft has been releasing lots of patch updates for the Mac version of RDP, which makes me more suspect of the RDP client.
Click to expand...
Thanks very much Rick_B. This workaround works for me too.
 
You must log in or register to reply here.
Back
Top