![]() Try shutting down Fusion and all running VMs, add that config option, then restart Fusion and whatever VMs you were using and you shouldn't see the caps lock switching like this on you. If you want to try, add =FALSE to your ~/.vmware/config or ~/Library/Preferences/VMware\ Fusion/config file. Example: "Mac mini Server (Mid 2011)".Īnd lastly, there is a config option that should turn this caps lock behavior off. Third, what Macs are people hitting this on? Please be specific, from About This Mac > Overview. Any chance you guys are using something like a Logitech Unifying Receiver USB dongle? Second, can I get some more information about exactly which peripherals are attached to the computers that are exhibiting this problem? Are there multiple keyboards attached, or multiple things that macOS might think are keyboard devices? For example, I use Logitech mice with their Unifying Receiver that lets me use both a keyboard and mouse with the computer. Can folks please reply back with what exact macOS version they're running, from About This Mac > Overview? What exact version of macOS are you hitting this with? I think I saw someone suggest maybe this problem was only happening on macOS High Sierra Beta 2 (10.13.2 Beta (17C67b)). Can I please get some more information from folks who are hitting this? Hey guys, so sorry to hear you're hitting problems with the caps lock between macOS hosts and VMs. If you're wondering, I'm running VMWare Fusion 10.0.1 on OS X 10.13.1. It's not a great workaround, but hopefully this relieves the frustration of not knowing WTF is happening w/ caps lock while you're trying to get some real work done. Go to SYSTEM PREFERENCES > KEYBOARD >, and select 'No action' for the caps lock key.Ĭlick again & re-enable the caps lock key.Īlways turn caps lock off before switching to the VM.Īlways use the 'Virtual Machine' menu to send caps lock to the VM. Turn off caps lock in the host OS by hitting the caps lock key. Make sure Caps lock is off in the VM (send Caps lock from the 'Virtual Machine' menu in VMWare). WORKAROUND (sort of) until VMWare fixes the issue: If you then turn caps lock off in the host OS and switch back to the VM, everything seems OK until you go back to the host OS. If you enable caps lock in the host OS, switch to the VM, and then switch back to the host, caps lock turns off while in the VM and caps lock will come back on when switching to the host OS. (VMWare reading the same variable it's writing for caps lock functionality?) I also can't get the VM to obey the keyboard caps lock, I have to send it from the menu this may or may not be related. ![]() I ahve seen much discussion of using Terminal to solve this, but I have little(no) familiarity with Terminal or Unix, so I'm a bit leery of doing so.It appears that VMWare is trying to keep track of the caps lock state of the host OS so it can put it back when you switch away from the VM, and it's failing. I have enabled my finder to Show All Files In Folder (), but still don't see the lock file. When I try to take ownership, it fails, then provides me with a Configuration file: /Users//Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional.vmx. ![]() After finding several documented cases of this, I went looking for the lock file, but it is not in my /Users//Documents/Virtual Machines folder. Once I did, it started up as per normal, but when I opened VMware to start my VM It told me the my Win XP Pro was locked. My Mac was unresponsive this morning (left it running all night) and so I held down the power button to restart it manually. I'm running VMware 2.0 on a MacBook Pro, and my VM is running Windows XP Pro. ![]() Sorry if this has been covered elsewhere, but I'm relatively new to the Mac and VMware, and my searching has proven fruitless, so I thought I'd try posting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |