Sleep Wake Failure with High Sierra 10.13.4

I have also noticed a Sleep Wake failure since updating to OS 10.13.4. I have a late 2013 iMac. It is FireVault enabled. If the computer sleeps for about an hour it wakes normally with a press of a key/click of mouse. If it sleeps for longer periods the only way to wake it is to press the power button. The iMac then essentially re-starts with the Apple logo and chime and login page. The only difference to a normal restart is that all my windows remain open as they were prior to the sleep. Sometimes it even chimes twice as if resetting the NVRAM. I have also experienced the frozen login screen with the orange exclamation mark that others have described.

I have called Apple and they have suggested all the usual things:

Reset SMC

Reset NVRAM

Deleted a few things in various folders

Change Power Save menu options

Nothing worked.

I then did a clean install of High Sierra and initially things were fine.

However... once I re-enabled FireVault and the encryption process had finished the problem started again.

I have tried various settings in the Power Save menu including disabling the 'put hard disks to sleep' option but still no change.

So I believe the problem is indeed a bug with FireVault enabled. I can only hope that Apple are taking notice of this and actually acknowledge that a couple of hundred computer literate people are not simply having this issue because of "a problem with the user account due to downloaded software" and that it cannot be rectified by "re-installing everything from a back-up".

looper84 wrote:

System-wide power settings:

Currently in use:

standbydelay 10800

standby 1

womp 1

halfdim 1

hibernatefile /var/vm/sleepimage

powernap 0

gpuswitch 2

networkoversleep 0

disksleep 0

sleep 0

autopoweroffdelay 28800

hibernatemode 3

autopoweroff 1

ttyskeepawake 1

displaysleep 3

tcpkeepalive 1

acwake 0

lidwake 1

You might want to try "sudo pmset -a restoredefaults" to reset everything first and try again. The out of the box on a MacBook Air 2017 should be follow:

Currently in use:

standbydelay 10800

standby 1

womp 1

halfdim 1

hibernatefile /var/vm/sleepimage

powernap 1

gpuswitch 2

networkoversleep 0

disksleep 10

sleep 1 (sleep prevented by SubmitDiagInfo, nsurlsessiond)

autopoweroffdelay 28800

hibernatemode 3

autopoweroff 1

ttyskeepawake 1

displaysleep 10

acwake 0

lidwake 1

When I turned off FileVault, it needed hours to decrypt the disk, so I disable both "Prevent computer from sleeping..." and "Enable Power Nap" under Energy Saver to prevent my iMac from sleeping during the decryption. Once that was done, I re-enabled those 2 settings, so I can't tell for certain whether the problem was fixed by disabling FileVault or re-enabling the Energy Saver settings.

Hope this helps!

10.13.5 has fixed the sleep wake issue for me but it is definitely much slower to wake from sleep. Used to be pretty instant, now takes a while to wake and the login screen flashes twice before letting me type. Not sure if this is just me?

Agreed hardmod! This is a fundemental flaw, and when you do a google search for this problem it seems that it has been a repeating issue since as far back as 5 years ago. Seems they keep making similar mistakes.

For anyone interested I have been following this thread and I contacted apple support. I am still on 10.13.4 but it seems the issue for me as been fixed by adjusting the energy saving settings and unchecking "put hard disks to sleep when possible". Seems ridiculous that I am forced to give up energy savings to make my mac usable, but so far it has worked.

Updating to 10.13.5 solved this issue on both my iMac's. After updating on Monday, re-encrypting the Fusion Drive and resetting the energy settings to default values both iMacs go to sleep and wake up without problems. Logon is possible. No red X on the Login screen and no strange shutdowns.

The only thing I noticed was that the iMacs take much longer to wake up from deep sleep - maybe 15+ seconds.

Same here with an '14 iMac 5k and FileVault. Did a complete reinstall with 10.13.3 to get rid of this problem.

I've confirmed that the sleep wake failure is fixed in 10.13.5 Beta (17F35e) with APFS encrypted disk. So, we'll have to wait until 10.13.5 for the proper fix.

The issue is fixed in the latest macOS 10.13.5 beta. We'll have to wait for its release.

Thanks for the tip! My Mac stop crashing after I disabled FileVault. Apple's quality is going downhill and I hope they will release a real fix soon.

Additional info: Deactivated FileVault (which executed much faster than expected) and the problem disappeared. Seems like apple didn't use encrypted volumes on their testing systems. Anyway, this is absolutely no solution for us as we are obliged to use encrypted volumes for data security reasons.

looper84 wrote:

I have a different issue, but it might be related.

I’m using MacOS 10.13.4 with FileVault enabled. The computer goes into sleep mode when the display is off, even though I’ve set it not to.

Go to terminal and run pmset -g and post the output here

I've just tested 10.14.5 Beta 3 and this problem is still present. The only way out is to run pmset -a standby 0 autopoweroff 0

Hi Joschu,

for me I did a time machine restore after a full reinstall an no bug. BUT as soon as I reactivated Filevault the Sleep Wake fault reappeared.

I ended up downgrading to 10.13.3 to fix this issue. Can anyone else confirm that this security update has worked for them?

Looks like Beta 5 fixed this issue, in fact the boot time from hibernation seems to be faster like waking from sleep.

I confirmed the sleepimage has been written so it did go to hibernate and woke up.