El Capitan Frozen After Sleep

Hi,

I had no issue before upgrading to El Capitan. It started immediately. I am using nothing other than a bluetooth mouse. Nothing plugged in. If the computer sleeps long enough to drop to the login screen the mouse and keyboard don't respond and I am forced to hold the power button until it reboots.

I do use VMWare Fusion 7, which others have reported issues with. I have tried suspending the VM and still have the issue. I will try shutting it down completely and maybe even upgrading to 8.

Specs:

• OS X El Capitan Version 10.11
• Model Name: MacBook Pro
• Model Identifier: MacBookPro10,1
• Processor Name: Intel Core i7
• Processor Speed: 2.7 GHz
• Number of Processors: 1
• Total Number of Cores: 4
• L2 Cache (per Core): 256 KB
• L3 Cache: 6 MB
• Memory: 16 GB
• Boot ROM Version: MBP101.00EE.B09
• SMC Version (system): 2.3f36
• Serial Number (system): C02KN63LFFT1
• Hardware UUID: 1E44A918-06A0-5C57-B242-9FDF5B5DC6FE

Another thread: Re: Mouse and Touchpad not clicking after sleep - hard restart needed

So far the problem seems to be associated with, although not exclusively so, to VMWare v7.

Some people report the issue with VMWare that resolves with shutting down VMWare, implying causation.

Others report that even when shutting down VMWare, the issue remains. Correlation but not causation.

Others report the issue even with no VMWare installed.

Certainly a mystery....

I have the same/a similar issue since updating to 10.11.1 MacBook Pro 15" Mid-2015 here. I have VMware 6 installed but I have not fired it up since many months, certainly not since upgrading to El Capitan.

I also tried disabling safe sleep from the terminal (found it in some forum), to no effect. After longer sleep, I have to reboot completely, it seems as if the Mac shut down during sleep.

Any help would be greatly appreciated. Won't upgrade my wifes MB-Air to El Capitan until this is resolved...

I have El Capitan with the latest update patch 10.11.1 (15B42) on my pro retina mid 2012. Now when my macbook wakes up from sleep I can use it for approx 20 minutes (time varies*) and then everything freezes. Not sure if the actual system freezes or if it is the trackpad and keyboard. I do not have vmware. I have never had any issues before.

*I am not sure what it is that I'm doing that makes it freeze, I know the last time I was checking for office updates and this time I was installing java update.

Is this the same problem as everyone else or different?

Your problem seems different. This forum is for an issue whereby the Mac is frozen after waking from deep sleep, not freezing during use.

ok I see. My issue only happens after a long sleep as well. So hopefully any fix for this issue would be related.

I Surrendered to this issue. Called support. Visited Apple Store and successfully downloaded El Capitan in 35 min. Via Apple internet connection.

I've been pausig the VM and closing the application before close the lid and so far the problems seems to have disappeared. It has been around 1 week since the last froze happened. ( VMWare Fusion 7.1.1)

SSame issue and I run VMware 7.x

Same issue and I'm running Fusion 7.1.2.

Will try pausing my VM and Fusion before shutdown. This is a MAJOR PITA though. Hopefully VMWare issues a patch soon.

i'm having the same issue starting with 10.11.1 on my Late 2013 27". After it goes to sleep at night, the next morning the trackpad, keyboard, & mouse are all frozen, it won't wake up. I have to press the power button just to see the screen. I hardly have anything exotic on it, either -- MS Office 2011, Chrome, Firefox, Google Drive, Box Sync, OneDrive, & Boxcryptor.

Assuming the vmware is the cause of the issue here and not El Capitan -- or both together:

I am experiencing the same problems listed here on all of my MacBooks:

Early 2013 MacBook Pro 13" Retina 256gb - El Capitan - Fusion 7.1 - Window 8.1

Late 2015 MacBook 12" 511gb - El Capitan - Fusion 8 - Windows 8.1

Keyboard and mouse on both machines freeze upon sleep. Can only take back control Hard Restart. Consequently, WIndows 8.1 installation through VMWare Fusion 8 on MacBook 12" Retina has become corrupted. VM is the windows installation that exists on the machine's native bootcamp partition.

How do I reset SMC when I have a firmware password? The password prompt appears interrupting the reset. Do I have to disable firmware password do the SMC reset and then re–enable the firmware password?

I'm having the same problem running El Capitan 10.11.1 and VMware Fusion 6.0.6 on a MacBook Pro (Retina, 15-inch, Mid 2014).

I also have hibernatemode set to 25 and destroyfvkeyonstandby to 1 and when waking laptop after hibernate I'm able to enter the File Vault password but then the trackpad and keyboard freezes on User login.

However, I don't need to restart the laptop to regain control. If I instead close the lid one more time when I'm at the frozen User login (after entering File Vault password) and leave it for 2 - 5 minutes (haven't checked how long it takes..) and then open the lid again, then Voila! and I can enter my login password and everything works like it should, even if the Virtual machine is running. Hope this can be of help to someone...

Another issue I'm having, which I don't think is related to the freeze issue, is that if I connect/disconnect the power when I'm in sleep/hibernate then the computer crashes/shuts down instantly. So I'm forced to do a little ritual every time I disconnect the power and move with my laptop to avoid the unnecessary shut down/crash... Very annoying.

If I suspend/quit VMware before sleep/hibernate then the machine will wake without problems, so it definitely has something to do with VMware Fusion.

In this thread Mouse and Touchpad not clicking after sleep - hard restart needed I have been able to relate the issue to a BlueTooth trackpad that was connected as a ghost. I haven't used it in months, but apparently after the El Capitan update, it was somehow connecting to the computer automatically and blocking the trackpad click function. Connecting and disconnecting all BlueTooth devices has fixed the issue so far. I have no VMWare software whatsoever.