Caps lock always turn on after switching from Windows 10 Virtual Machine to Host

[rakewell]

I have a really annoying problem since I upgraded to vmware fusion 10 (10.0.1) (why oh why do I keep upgrading)

When I move to the virtual machine which is hosting windows 10, no matter what caps state the virtual machine is in, my caps always goes on when I return to the host. So no caps in host to virtual machine no caps = CAPS when returning to host, no caps on host to caps on virtual machine = CAPS on host. I continually move from virtual machine to host which means that I constantly have to turn CAPS off. Can anyone tell me how I can fix this?

[vanRijn]

Thank you for the data, glenn380​. Please put "mks.keyboard.setHostLEDs=FALSE" in your ~/Library/Preferences/VMware Fusion/config file and restart Fusion. You can do this by running "echo `mks.keyboard.setHostLEDs=FALSE` >> "$HOME/Library/Preferences/VMware Fusion/config". We're working on this problem internally but doing the above should stop this behavior from happening.

[glenn380]

Thank you, vanRijn.

I added the config entry, but it still seems to happen, though possibly less often. Hard to say.

I also have key repeat problems, which, like the CL issue, seem better now that I maxed out my Windows key repeat delay, but it still happens.

Keep up the good fight.

[MattBirminghamG]

I'm also having this problem. I had been seeing issues with CapsLock and tracked it down to Fusion when I simply moused over my active Fusion client then back to OSX. Mousing over the client (Windows 10 Enterprise, v1607 build 14393.970 in single-window view) would turn the lock on. There was no way to make them sync.

I'm running High Sierra 10.13.1 on

MacBook Pro (Retina, 15-inch, Mid 2014)

Processor 2.5 GHz Intel Core i7

Graphics NVIDIA GeForce GT 750M 2 GB Intel Iris Pro 1536 MB

I'm connected to the MBP in clamshell-mode using a USB-connected Microsoft keyboard (Comfort Curve Keyboard 2000 v1.0) and the mouse is a Logitech MX Master (model M-R0052) connected via Bluetooth.

[1JGstaff]

ABOUT THIS MAC

macOS High Sierra

Version 10.13.1

iMac (27-inch, Late 2013)

Processor 3.4 GHz Intel Core i5

Memory 8 GB 1600 MHz DDR3

Startup Disk Macintosh HD

Graphics NVIDIA GeForce GTX 775M 2 GB

PERIPHERALS

Apple Wireless Keyboard

Satechi USB Numeric Keypad Model No. ST-U2NK (in case this makes a difference to you)

RECREATE THE ISSUE

Caps lock is disabled in host.

Switch to VM.

Click (anything, anywhere).

Press a keyboard button (any button).

Caps lock turns on (sometimes with the mouse click, other times with the press of any button).

Caps lock won’t turn on if I type immediately after switching to VM (i.e., before clicking anywhere).

[prach]

I use macOS High Sierra 10.13.1, VMWare Fusion 10.0.1, Macbook Pro Retina 15"  (2016)with touchbar (16 GB RAM, 2TB SSD, 2,9 GHz Intel Core i7, Radeon Pro 480 4GB), external monitor 27" Dell connected thru USB C thru Belkin USB C dock, external apple touchpad and mice and Mathias wireless keyboard. I have connected several thunderbolt and USB HDDs and Wacom Intuos pro tablet. The Caps Lock issue I have on Both (external and internal) keyboards.

[DavidRegalDevOp]

Thanks vanRijn for the moderation and feedback. If you're still collecting data points on systems with the problem, here's mine:

Host:

• MacOS 10.13.2
• MacBook Pro, 13 in, early 2015
• VMware Fusion 10.0.1

Guest:

• Windows 7, SP1

Before today, restarting VMware Fusion fixed the problem but not today. I'll try that preference workaround next.

[DavidRegalDevOp]

vanRijn​, Forgot to give you info on "... which peripherals are attached to the computers that are exhibiting this problem":

• Apple bluetooth keyboard model A1314.
• Apple bluetooth Magic Trackpad model A1339.

I applied the workaround in the config file. I'll be back here posting if it doesn't work.

[Mohannad]

Wanted to confirm that testing Fusion 10.1.0 Update - this issue and the slow VM resume issue are still present.

[TAG975]

Hello,

the problem with caps-lock is present also in the official update od Fusion 10.1.0., which I installed today. The problem wasn't there in the beginning, but appeared after a few hours of work, constantly switching between host (High Sierra) and virtual machine (Windows 10). Furthermore at one point the caps-lock key stopped working completely, remaining in small letters in virtual machine and in capital letters in Mac OS. Also the problem with caps-lock not working in High Sierra remains after the shut-down of the virtual machine (WIN 10) and needs restarting the computer. Very annoying problem which makes the work quite impossible.

The computer in use is a Macbook pro 13 with touchbar.

[vanRijn]

Excellent, thanks very much for the information, 1JGstaff​.  Can you clarify... your steps to recreate the issue...

1. Caps lock is disabled in host.
2. Switch to VM.
3. Click (anything, anywhere).
4. Press a keyboard button (any button).
5. Caps lock turns on (sometimes with the mouse click, other times with the press of any button).

I don't see a step to "Switch away from VM back to host". Are you seeing the Caps Lock turn on in the VM without switching back to the host OS?

One of the changes made recently that is relevant here is that the caps lock state is tracked separately for the VM and the host OS. So if the caps lock state is turned on the VM, switching to host OS and back to VM should result in the caps lock state being on once again while interacting with the VM. But if you are saying that the steps are like this:

1. Caps lock is disabled in host
2. Power on VM
3. "Grab" into VM so input is going there now.
4. Observe that caps lock state is off in VM and on keyboard light
5. Click (anything, anywhere) (this "grabs")
6. Press a keyboard button (any button)
7. Caps lock turns on and keyboard capslock LED lights up
8. Switch back to host OS and stop interacting with guest by CMD-Tabbing, pressing Cmd+Control to ungrab, or bringing a host application like Safari to the top above the VM

Is that what you're seeing? Or... can you clarify please with maybe some more specific steps? Thanks! =:)

[Woofs]

I too have been experiencing this problem recently. In fact, I am typing on my new BT keyboard as I thought my old one was going flaky. I bought a new one and found the issue remained.

I am running High Sierra 10.13.2 with VMware Fusion 10.1.0 with a Logitech K380 BT keyboard and a Logitech M705 mouse with a USB dongle. It also happened while using my first generation Apple Wireless Keyboard.

This has been driving me absolutely bonkers. I have implemented the mks.keyboard.setHostLEDs=FALSE to the config file, and in the short time since then, I've not seen it happen. Fingers crossed.

[Grammie]

I am brand new to VMware Fusion after getting a new MacBook Pro I made the switch from Parallels to Fusion. Regretting it already, as I too am having this CAP LOCKS issue and see it has been going on for a couple months and not yet fixed. I can NOT turn off Cap Locks when I return to host after working in the VM. I am just a very average user so can't get very technical. 

My experience:

After using Word in the VM and then going to the host, whether cap locks was on or off (or even USED) in the VM, I am stuck in CAP LOCK on the Host and Cap Lock will not work in the VM (though I can get a Cap with shift key in VM). Only fix is to restart. (I do not know that working in WORD has anything to so with it, as i usually am in it at one point or another, as well as a few other programs.)

MacBook Pro 15" w/ Retina and touch bar
High Sierra 10.13.2
VMware Fusion 10.1.1 (7520154)

And NOW suddenly in the VM I am in STUCK IN CAP LOCK (whether  indicator light is on or off) but can type lower case if I hold in the shift key. THIS IS NUTS. I do not know what made this suddenly change while I was typing this reply!!! I HAD TO ACCESS YOUR WEBSITE thru the VM so I could type in my password since it had lower case letter.:" btw shift key works properly for special character keys :"<>? but backward on all letter keys.

[mkilgore]

Quick check to see if this has been resolved.  I am running 10.1.1 guest CentOS 7.  I am currently seeing the issue were caps lock state is improperly restored to ON.  I have also experienced the 'permanently' (until reboot) locked caps lock.

I hope there will be a fix soon.  If more information is required to identify the reason for the issue, i would be happy to help

[scottyrotten]

Still having this issue.

Running VMware Fusion 10.1.1

MacOS High Sierra 10.13.3

Multiple VM's - Windows, Ubuntu, Kali Linux, Security Onion etc.

Behavior is:

Caps Lock Off when clicking inside of a VM, when returning to the host OS caps lock is enabled, re-enter VM caps lock enabled, return to host caps lock remains enabled.

[CAPS_LOCK]

I HAVE THIS PROBLEM TOO. SOME RANDOM EVENT IN THE VM IS LEAKING OUT TO THE HOST OS IN SUCH A WAY THAT THE CAPS LOCK KEY IS COMPLETELY STUCK. WHETHER THE LIGHT ON THE KEY IS ON OR OFF THE TEXT COMES OUT AS OF THE SHIFT KEY IS HELD DOWN.

ONLY ANSWER IS TO REBOOT THE MACHINE - VERY VERY ANNOYING.

IF IT WEREN'T FOR THE FACT THAT MY CAPS LOCK KEY WERE STUCK I MIGHT BE TEMPTED TO COMPLAIN IN ALL CAPS TO EXPRESS MY FRUSTRATION.

FIX THIS BUG PLEASE.

[vanRijn]

I just gotta say, @CAPS_LOCK, you made my day.

Anyway, just wanted to get an update out to you guys. I've found the problem and a solution. This has been fixed internally. I can't speak to when Fusion will put a new release out which contains the fix, but one should be coming at some point.

So sorry this bug was missed and is affecting all of you. Hang in there, a fix is coming.

[glenn380]

vanRijn​: glad to hear that this has been fixed internally.

Based on your experience, can you give us any guidance on when a release with this fix may come out? Days? Weeks? Months?

Thank you for your help.

[paultq]

The exact same problem here. Need to restart to fix it. really annoying

[jmd_sqp]

This is not working for me either. After paying €103 to upgrade, and having this issue every single day, trying to develop software, I am very annoyed. This happens to me when connecting to a remote VSphere machine too.

[Zongmin]

Hi all,

Sorry for this annoying issue! We already fixed this internally and the fix will be contained for the upcoming update release of Fusion 10.

Before the official fix, pls try following workaround documented in KB:VMware Knowledge Base.

Thanks!