I'm running Fusion 11.5.1 on a 2018 15" MBP w/ i9 2.9GHz and 32GB ram.
Since upgrading from Mojave to Catalina 10.15.0 and now Catalina 10.15.1...
If I've got a VM running and I close the lid, putting the machine to sleep.... when I later awake the machine (by opening the lid), the keyboard and trackpad are dead. The touchbar and touchid work and I can unlock using my fingerprint. But, a few seconds after coming out of sleep, the keyboard & touchpad a non-responsive and I see a message window saying;
"Bluetooth Mouse or Trackpad Setup
There isn't a wireless mouse or trackpad connected.
Looking for a wireless mouse or trackpad. If one is found it will be connected to your computer. Check you cables if you expect to use a USB mouse. If you don't want to set up a mouser or trackpad, press Command-Q to Quit.
If you are attempting to use a wireless mouse or trackpad and it isn't found, make sure it is turned on and "discoverable." If you are using an Apple wireless mouse or trackpad, turn on your mouse or trackpad. If you are trying to use a non-Apple wireless mouse or trackpad, see the documentation tat came with the mouse or trackpad"
At that point I can not use the trackpad to move the mouse pointer, nor type anything on the keyboard. Infact the keyboard backlight is even dead at that point.
At first, I could not do anything but power down (by holding the power button for over 10 seconds) and power backup.
I've subsequently found that if I close the lid for a minute and then re-open the lid again, the keybaord and trackpad will usually coma back to life.
Again, this only seems to happen when putting the machine to sleep whilst a VM (either Win10 or Linux) is actively running and then trying to awake the machine from sleep.
Anyone else noticing this behavior?
Have had similar experiences which *may* be because of Fusion. Still a bunch of other things to exclude (new 16" MBP, Catalina, migration from Mojave), but Fusion's not off the hook.
Symptoms are intermittent lock-up of the trackpad and keyboard when unlocking the screen; touchbar still works. Normally use the MBP connected to Cinema displays (office & home), but have had this lockup when using the MBP standalone. Have also had it where the external keyboard and mouse is fine, but the mouse and keyboard on the laptop are locked.
Have seen some comments on this on Macrumors forums and thus far there's a common theme of Fusion.
Would be interested in other's experiences.
I know it's not an answer, but for a number of reasons it's always best to pause the VM before sleeping the host.
Had one where something went wrong, the guest didn't suspect, and the laptop not only burned through the battery charge, it almost burned through the bag!
Back to your original question, have you tried disabling 'allow bluetooth devices to wake this device' in the host preferences? I do that (for the same reason as above - cat walked on keyboard, laptop woke up, got on airplane with a very hot machine, and very empty battery).
Just wondering if it's something in the startup sequence on Catalina that's causing it - long shot to be sure.
This is exceedingly irritating.
16" MBP running Catalina with Fusion 11.5.1. Use spaces and Fusion full screen. Windos 2012r2.
Use Fusion, change focus to another space, close lid.
Open lid within a minute or two. The keyboard and mouse are then locked up. Trackbar works. Eventually a dialog "Cannot connect to a bluetooth keyboard and mouse" comes up.
If you connect to a monitor with keyboad and external mouse, you can use that BUT THE LAPTOP KEYBOARD AND TRACKPAD ARE STILL LOCKED.
"...Back to your original question, have you tried disabling 'allow bluetooth devices to wake this device' in the host preferences? I do that (for the same reason as above - cat walked on keyboard, laptop woke up, got on airplane with a very hot machine, and very empty battery)."
I've never had a problem putting the laptop to sleep while a VM is actively running (until now). Indeed, I've never had a Mac NOT fully go to sleep when I close the lid. But, based on the description of your experience, I may have to be more sensitive to that.
Anyway. I don't use any Bluetooth devices. So, Bluetooth is completely turned off on my machine, and always has been.
The problem seems to be very intermittent for me now [now that I'm trying to "make it happen"]. It happens maybe 10 - 20% of the time. And when it does happen, it seems to be when I have a VM running. I've seen it happen when the VM's window has focus and the mouse pointer is inside the VM (I run all my VM's in single window mode, as opposed to Unity or Full screen). But, I've also seen it happen when the VM's window does not have focus.
So far, I can get things to work again by simply closing the lid for 60 seconds and then re-opening the lid.
One thing to try is to disable passing bluetooth to the guest.
That would be first thing I would try if I had to troubleshoot your issue.
Especially as your error mentions bluetooth.
On the menu "Virtual Machine" go to "settings", select "USB & Bluetooth" and uncheck the "Share Bluetooth devices with Windows" checkbox.
This is probably a reasonable idea (disabling Bluetooth sharing) for desktop machines. But I don't believe the keyboard/trackpad in a MacBook is bluetooth-connected. (Someone correct me if wrong.)
Either way, I took it a step further and have started outright removing the USB controllers from my VMs. So far so good, but the unreliable nature of this bug obviously makes it hard to prove my method is foolproof.
No it isn't, neither is anybody complaining about their bluetooth devices no longer working, but there's a bluetooth error when the problem is happening.
I mentioned this as it looks like the bluetooth stack is part of the USB logic for VMware and there's a reasonable chance that it is blocking in certain cases.
For example because there's no bluetooth at the host, the code gets locked up in the bluetooth detection logic and thereby causes trouble for your keyboard & trackpad to function.
I've also seen a few other bluetooth problems pop up here at the forum for the 11.5.x release.
My suggestion is less invasive to test and would isolate the issue a bit more (if it helped).
However if you're not using USB in your guest then I guess your solution works too.
At least it appears to point into the correct direction.
Am pretty certain it's related to Fusion. The only time this happens is when Fusion's running.
I tend to run my Windos 2012r2 dev machine in a separate space. Don't normally sleep it unless it's for a reason. I normally use my Mac connected to an external display, both from home and the office, so consequently I don't notice the laptop keyboard and trackpad locking up.
However, if running Fusion as a laptop, locking the screen will more often than not result in this keyboard/trackpad lockup -- even if the focus isn't on the Fusion space. Have to close the lid and try again after a couple of mins.
And I've only ever seen that Bluetooth dialog message once. Normally it's just locked up (with me cursing and screaming at the machine, such is my frustration!)
Also, I've another issue which could be Fusion related.
When the MBP's connected to a Cinema display (others have reported other monitors too), when waking a locked screen, the external monitor's blank / black.
This could be Catalina, but just as well could be Fusion.
Anyone else noticed this?
I installed MacOS Catalina 10.15.2 on Dec 12th, and I haven't had the problem since then.
I've tried many different scenarios and I just can't make it happen now.
Anyone else still seeing the problem, after installing 10.15.2 ?
I'm having the same issue, and I've experienced it while running latest Catalina 10.15.2.
It seems to happen when I put my Macbook Pro (2019 16 inch) to sleep while having a VM running in VMWare Fusion. Built in keyboard and mouse are no longer recognized (and touch bar is completely black) when I wake the computer from sleep.
I can partly fix the issue by closing the macbook lid and putting the macbook to sleep again. By doing this, and waking the computer up again from sleep, I've managed to get the mouse + keyboard running again, however, the Touch Bar was still dead after doing this. To completely fix it, ie getting the Touch Bar working again, I had to soft restart the computer.
I'm experiencing the same issue but: I don't have VM installed … so it might be an Catalina/macbook issue.
Mine is a completely new 16" … fresh install … problem occured after a week. Only thing I installed recently was Turbo Boost Disabler Pro …
It takes about 15 seconds until my input devices are recognized again.
Glad I'm not alone on this one..
I thought it was a Macbook or OSX issue. I've done repair install, fresh install, PRAM & SMC reset but would not resolve this issue. I finally noticed this behavior occurs only when I have Fusion running. I began to suspect Fusion might be the underlying issue.
I also came across this post on the Apple community: https://discussions.apple.com/thread/250726669?page=1
I'm having the same problem with new 16" MBP, that shipped with Catalina. The only time, I've noticed the issue with loosing keyboard and trackpad I've had VMWare Fusion running. Saw something posted about this on the Apple Forums as well.
Super annoying, and time killing distraction.
Just a quick update... since installing Catalina 10.15.2 almost two months ago (on 12/12/2019), I haven't experienced the problem at all.
I installed Catalina 10.15.3 yesterday. I've only been thru a couple sleep/wake cycles. But, so far so good.
So, for me Catalina 10.15.2 seemed to fix the issue.
Will continue to test with 10.15.3 and report back.
I have used Fusion with every MacOS version since 2007 or so and I never had these issues until the 16" MBP and Catalina. Something is definitely broken. Mine is dead coming out of the bag about 60% of the time. It also drives the fans crazy. So bad that I have abandoned the beast of a machine and bought a Surface Laptop 3. 90% of my workflow is in Windows (or can be), Fusion has always been at least as reliable as any PC I have owned from the beginning unit this last go around, but this is completely unusable.
Yes, pausing the VM is a solution, but it has never been necessary until now. FTR, 10.15.2/3/4 have not helped.
Hi, I haven’t Catalina, but same problem. Nothing works at my system, until today.
Always, no keyboard. I spent 3 days on it....
Today I search again in internet and I found this in YouTube. It was new Uploaded today.
now, all works fine..