High Sierra freezing after wake from sleep

I had this problem too after updating to 10.13.4 on a MBP Late 2013. I did a clean install and the problem still occurred. What helped for me is to switch off FileVault or disk encryption. After this, everything ran smooth again and no freezes occurred anymore (for 3 days in a row now). Apparently FileVault and the newer APFS don't get along quite well yet, and freezes like these are one of the symptons (found this somewhere on StackExchange, but can't find the source anymore though).

I really hope Apple fixes this soon, but for now I'd advise to keep FileVault switched off and see if you still experience freezes...

A possible fix could be resetting the SMC if resetting the NVRAM doesn't work (Hopefully it does though)

To do this:

(Preferably after a successful wake from sleep but in this case it's optional)

1. Quit any applications running.

2. Restart your Mac (Unselect the re-open apps box)

3. Once it has come back on, shut down using the Apple Menu -> Shut Down. (If it's unresponsive you can hold down the power button)

4. Unplug the Power Cord

5. Wait 15 seconds - Plug back in.

6. Wait a further 5 seconds - Turn back on.

Hello!

I tried turning off hibernation during sleep on my Macbook Pro mid-2012 with an OCZ Agility 2 SSD, with these lines that I found on MacIssues:

sudo pmset standby 0

sudo pmset autopoweroff 0

I've woken it up from sleep mode many times now, and it hasn't frozen on me yet!

I deactived File Vault as suggested by gszabo. For one week, I had no single problem on wake up. It took only a few hours (and the first deep sleep / hibernation, probably) after I reactivated File Vault for the problem to come back. Contrarily to spearfishdoc, my MabBook Pro was always plugged in when it happened. I hear that this is an old and recurrent problem, but it definitely appeared for me shortly after I upgraded to macOS 10.13.4. I wonder if it can be related to Fusion Drive (I have a Fusion Drive) and transition to APFS, which was supposed to be supported for Fusion Drives, but finally no, but yes, maybe... I lost the thread about this story :/

I have never used FileVault, so for me the common factor is the 10.13.4 update.

I resolved my issue (for now) by following another's suggestion of turning off certain things via the terminal

sudo pmset standby 0

sudo pmset autopoweroff 0

I can still put my external display to sleep, but no more freezing when I wake the display.

Of course this is not a viable permanent solution.

I wonder if turning FileVault off or on simple changes the environment enough to make a difference to the bug they introduced in the above update. It does not necessarily mean FileVault is the cause, just one of the variables that effect the cause.

Yup, same issue on my end which appears to have started only since 10.13.5 on my iMac 27" 92013) 14,2.

In short, enabling the "Prevent computer from sleeping automatically..." within the Energy Saver options has macOS work without a hiccup. The moment you disable this feature and allow it to sleep as per its default schedule, waking either freezes/crashes the system OR sometimes displays a flashing folder with an ? embedded (which is generally an error related to the OS/file system not being found).

Note, extensive hardware tests including Apple's own AHT plus 3rd party tests have been performed on the usual suspects being memory and the SSD drive and both came back errorless.

I call bullsh!t on 10.13.5. This exact same issue occurred on a previous version of Mavericks which Apple (in their standard fashion) kept quite about and magically fixed in a point release after an uproar.

Come on Apple, we all remember https://www.vox.com/2017/12/22/16807056/apple-slow-iphone-batteries , let's not try the same scummy tactic on the Mac platform.

I have a similar problem with my 2013 MacBook Air. Same sort of symptoms. In my case, I am using wifi all the time, no ethernet cable.

Try this:

- before putting your computer to sleep, turn off wifi.

- after waking up your computer, turn on wifi.

In other words, manually disable / enable wifi before/after putting your computer to sleep.

I recently discovered this by accident. As inconvenient as it is to do this procedure, I've encountered zero "freeze-upon-wake" issues since then.

Edit: I've done the SMC/NVRAM/PRAM-whatever reset numerous times, and it's never seemed to be effective in my case.

Hi,

not sure if this tip will help any of you, but it's worth a try, won't do no harm (worked for us on a MBA):

in System Preferences, under Security & Privacy, check the FileVault tab. If FileVault is on, turn it off and reboot.

Try using the mac for a couple of days.

If the problem is gone, you can try turning FileVault back on.

This happens when I close the computer and leave it unplugged for any significant time and the computer goes into some form of "deep hibernation"? IF I leave the computer plugged in overnight, it doesn't freeze and lets me login normally. I DID try turning off the FileVault encryption?? and that seemed to work. When a re-enabled FileVault, the computer went back to freezing upon hibernation. There have been some suggestions to disable hibernation? but I'd assume that will drain the battery more and would rather it work properly (of course). Hoping to hear any other suggestions.

Apple care after seeing my logs and files told that my problem probably was cause by insomiax (app to prevent computer to go to sleep after closing lid. ) i need to reinstall Mac OS one more time and check this. Do all of you have some apps that somehow changes power managment of your device?

I think I just figured out the problem in my case.

For me it seems to be an issue with Unlox (formerly known as Mac ID), which is an app I use for logging in.

I have tried using my MacBook without running Unlox, and it stopped freezing at wake.

Today, once I had logged in, I ran Unlox and immediately the screen froze for 5 seconds or so.

I will contact the developer, who I know very well by the way, it shouldn't be a problem.

In your case, try disabling every app that auto launches at login I guess.

In my particular case, I found the culprit to be a VPN that has an 'internet kill switch'. The freezes relate to a process that requires admin access, thus prompting the admin password dialog. It requires access to the keychain, which in my case is iCloud enabled, which somewhat the VPN detects and without properly establishing connection to the VPN server, the app activates the kill switch, and renders the freezing. I've reached out to the VPN provider awaiting their response.

...a few hours later...

sudo pmset standby 0

sudo pmset autopoweroff 0

Seems to have done the trick for me.

Mac waking up with no issues whatsoever.

Anyone knows what the downsides of those settings are?? TIA, Raphael

HI

I had this problem with a brand new MBP 2018. Contacted Apple Support who suggested resetting the SMC. And that worked - most of the time. Not always and inconstant behaviour when trying to wake. If running on battery more likely to require a stab at the power button to get it to wake. And just posted elsewhere what running iTunes, if the screen goes to sleep, the whole thing goes dark requiring a restart. Resetting the SMC is a pain, but may need to be done more frequently than before. BTW. i had a mid 2012 MBP running 10.13.6 which didn't exhibit this, so perhaps a hardware related matter?

Andrew

For those still having this issue, the following suggested fix of resetting NVRAM worked for me:

hang - How to fix mac os high sierra, freeze? - Ask Different

Here are instructions on how to clear NVRAM by Apple:

macOS Sierra: Reset your computer’s NVRAM or PRAM

For what its worth, my freeze-on-wake issue started after having my keyboard replaced under the Apple warranty program. Resetting my SMC did not have any recognizable effect but resetting NVRAM fixed it for me.