Sleep Wake Failure with High Sierra 10.13.4

As far as I can tell, Apple has not issued any guidance as to what to do. And disabling FileVault is not acceptable to me - as it provides valuable security protections. I have taken to shutting my machine off instead of putting it to sleep.

Haven’t done that on a Mac for years.

Apple, can you at least public acknowledge that there is a problem here?

I had this issue on an iMac (late 2013, i7 3.5GHz, Apple-fitted fusion drive) with filevault active.

I sleep it most nights, and it didn't ever sucessfully wake up after updating.

I turned off filevault (took over 9 hours), and no problems since then, when waking from sleep.

I'll re-activate filevault when this gets fixed.

Same problem here.

MacBook Pro 13” Retina with 10.13.4 and FileVault enabled.

After having the MBP in sleep mode for 3 hours (standby delay 10800), when opening the screen, the login screen is shown and after entering the password the computer freezes.

Filed a bug with Apple. I hope issue gets fixed in 10.13.5.

As a workaround, I've extended autopoweroff and standby to more than 12 hours. It should keep the MBP in the sleep mode overnight.

Same problem here - Late 2012 iMac with fusion drive. I haven't got Filevault on though and still getting these sleep wake failures. Read somewhere people suggested it may be related to Bluetooth so will try turning that off overnight.

Same problem, same iMac, same OS version. 3TB Fusion Drive. After much research and testing, I found that standby / hibernate do not work on High Sierra 10.13.4 with FileVault on, but works fine with it off. Two configurations where wake from extended sleep works : 1. FileVault on, standby 0 and hibernate 0 (sudo pmset -a standby 0, sudo pmset -a hibernate 0) and 2. FileVault off, standby 1, hibernate 0 or 3.

I opted for config 1 since power outages are rare and security is more important to me. Also I habitually save and close out my work at the end of a session so the risk of data loss for me in a power outage is very small. This behaviour started when I upgraded to High Sierra. Notably, this is not an issue on my two laptops, which both have standby and hibernate set to 1 and 3 respectively. I conclude then that this is a bug in High Sierra that affects iMacs with Fusion drives,. It seems the system is trying to restore from the sleepimage on the fusion drive every time, (even though there was no power outage) which it cannot access due to encryption, causing hang at wake up. My understandi

ng is that only hibernate set to 25 should force wake from the sleepimage every time (ie where there has not been a power outage). Therefore there are two parts to the bug 1. Waking from the sleepimage when it is not supposed to and 2. Not being able to access the sleepimage due to encryption. Hope this helps but happy to share more if there are questions.

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".

I share your hope. I have been dealing with this same problem for weeks. I have one other wish - proof that Apple actually reads these message boards and responds to its customers who are being victimized by an update gone wrong.

My bug report was posted a week ago, I've provided all logs they asked, but silence since then.

There is 10.13.5 beta 2 released on Apr 17th, but no sign of the acknowledgement of this issue in the Release Notes.

Hi David, yes apple reads this thread... I was contacted by them soon after my first posts and was actively helping to find the cause of the problem by doing tests on my machine. No solution was found at the moment, but, as far as I could see, Apple is working on it.

@RecheRech, I hope the analysis we have done here gives Apple a really good start as to where to look! Glad the configs from my testing helped you.

I think it is particularly interrsting that Fusion drive iMacs seem to have the problem but, for me anyway, my MBP, which does not have a Fusion drive, does not.

Same issue here with a Late 2013 iMac 21.5 inch Core i7 with Fusion Drive. Scheduled sleep/wake worked perfectly until 10.13.4 installation. I do not, and have never had, FileVault enabled. A SMC Controller reset, and an NVRAM reboot solve the issue but only for 24-48 hours. The machine won;'t go into sleep mode when it's supposed to, and when the screen is "awakened" after overnight, the 5-minute sleep warning appears. Something is preventing the sleep countdown cycle from beginning at the proper time, and when the screen activates, the iMac "believes" that it's time to go to sleep.

Awaiting this to be fixed in 10.13.5 and I've reported it using the Feedback Form.

A huge let down on a point release. Apple is in a dire need to get their QA testing improved drastically. Their priorities seem to be everything to do with iOS these days. No Mac mini updates for 4 years, no new Mac Pro, MacOS Server no longer a "server", no Aperture, and dumbing down of iWork, Pro Apps, etc. Bring back Scot Forstall!

Problem is fixed in 10.13.5 beta. Verified in build 17F45c with APFS encrypted disk on MBP Early 2014.

I agree. This update is garbage... MacBook won't wake without hard restart . safari won't open half the pages I navigate to, Chrome will not open at all and neither will firefox, external monitor is not recognized ... Really disappointed with this one!!

Hi corvax,

quote:

I got my solution!

I've MacBook Pro 13' 2016.

1 - have a time capsule backup.

2 - reinstall original macOS Sierra

3 - update macOS sierra to High Sierra 10.13.4

4 - using Migration Assistant restore your data and program.

working perfect 🙂

thanks for sharing, i did almost the same and can confirm that it works.

- installed a fresh macOS High Sierra 10.13.4

- use Time Machine to restore

(MacBook 15" early 2013)

I guess the most interesting thing may be: I did not activate file vault (disc encryption).

Can you confirm, that it still works even with file vault active?

I just asking because in some threads it is mentioned that the active file vault seems to be the cause.

Beside that:

In my case it started on no specific event using 10.13.3.

I'm very sure it was 10.13.3 because my hopes where in 10.13.4 to fix it.

Hi, I was very optimistic with yesterday’s security update. I turned sleep back on and left the computer alone. After about 3 hours I heard it restart all by itself with 2 startup chimes, an Apple logo, progress bar and a grey login screen. So sadly didn’t work for me. I don’t understand why pride cannot be swallowed and Apple can’t think of customers who have given them thousands of pounds/dollars to ‘benefit’ from a good user experience.