Sleep Wake Failure with High Sierra 10.13.4

It’s not just you. Waking from sleep is much slower - but at least it doesn’t crash.

Same problem with my Mac Mini 2012 - FileVault is enabled too, everything was working fine before the update.

Through this support page Comment télécharger macOS Sierra - Assistance Apple I was able to find a downloadable macOS Sierra.

Bye bye High Sierra.

So you would advise deactivating encryption and then *re-encrypting* again under 10.3.5?

Thanks. I have been shutting down instead of sleeping my 2017 iMac 5K until I heard something about this being resolved. I have already updated to 10.3.5, and will try sleeping it now.

Sorry, this doesn't change anything 😠. Did you try it?

I disabled File Vault and the problem went away. My iMac was able to sleep overnight and woke normally.

For next steps, I'm going to re-apply the 10.13.4 combo update and then turn FileVault back on to see if that fixes the problem.

I also logged a bug report with Apple.

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.

Ok, I turned off File Vault and the problem went away. Once the drive had completed decrypting, I applied the 10.13.4 combo update and then turned File Vault back on.

It took a good three days for my drive (1 TB fusion drive) to encrypt and during that time I was able to login normally after my iMac woke from sleep. However, once the encryption completed, the same problem returned.

I've logged a bug report with Apple and would encourage others experiencing this issue to do the same.

Feedback - macOS - Apple

I have 2 iMac exhibiting the same problem, one late 2012 and one late 2014. Either going back to 10.13.3 or disabling FileVault make the problem go away.

Please all submit error reports. Here is the bug report form:

https://bugreport.apple.com/web/

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.

Ravi1066 wrote:

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

No, I tested 10.13.5 Beta 2 and this problem is still there. I already filed 2 bug reports to Apple for this particular issue via their beta feedback program.

I have over 600 Macbook Air deployed and 10.13.4 fixed a few of MDM related issues and yet it break the most basic functions.

My 27-inch, Late 2012 iMac's wake from sleep problem with File Vault enabled disappeared, but I can't specifically say it was 10.13.5 that fixed the problem.

To avoid the double bong and hard reset in the mornings, I disabled sleep altogether, and powered my iMac off every night. In the morning, at power on, I had time to go get a cup of coffee, literally, before it presented me with a logon prompt. Well, that symptom suddenly went away -- I started getting the logon prompt after mere seconds. (maybe 5-10?) Still on 10.13.4 at that time. Figuring I had nothing to loose, I went ahead and installed 10.13.5, re-enabled hard disk sleep after 30 minutes, and my wake from sleep problem is gone now. I've only been up for 1 day and 3 hours, but my Mac has gone to sleep and awakened several times since then -- the logon prompt appears quickly, and I can here the disk spin up, all is well.

So, I don't know what the solution was!? I have power nap enabled, maybe Apple pushed out some kind of fix that didn't get logged as an update? Being a retired software guy, that kind of 'fix' -- the problem just going away for no apparent reason -- is what used to give me nightmares. Whatever, I'll take it. Good luck to everyone.

Decrypt/re-encrypting did not correct the issue for me, it got worse, had to unplug and walk away for about an hour. Below is my timeline;

Same problem here also, mac mini 2012, started exactly after the 10.13.4 update.

I get the hang, log in screen with unresponsive keyboard and mouse, and I am using FileVault. Have already tried all of the recommended fixes including reinstalling macOS with negative result.

Since I should not have to relinquish FileVault, I'm looking for more options. Have not heard anything from Apple yet. One thing I am going to try tonight is running with the SLEEP MODE turned OFF;

{Choose Apple menu > System Preferences, then click Energy Saver}

I have read some tech notes that indicate the sleep mode has a record of interfering with log ons and boot ups as well as keyboard/mouse malfunctions.

I've seen where there is a 'combo update' available on this thread, not ready to try that yet. Anyone else with any ideas (except turn off FileVault) are welcome. toodles.

Update. After months of this issue every day, after turning off Sleep Mode, day one, the mini logged in normally with File Vault turned ON and all settings as they were prior to the update. Will run it a few days and advise.

Update 2; This works for me, turn OFF Sleep mode. {Choose Apple menu > System Preferences, then click Energy Saver}.

5 days into it and no problems logging it on. Try it, you'll like it.

However,,,,(there's always a however), now I discovered that I have to manually update passwords in Safari, and they don't stick unless I restart after updating said password(s). I don't know if this bug came with the update, or if it started when I turned off sleep mode.

For now this fix works for the log-on fiasco.

C'mon Apple, I am running out of bug spray.

UpDate 3; Updated to 10.13.5, this DID NOT resolve the sleep/wake failure with hang, log in screen with unresponsive keyboard and mouse, forcing me to hard shut down and start again. It DID resolve the weird password thing I listed above. Had to Turn OFF Sleep Mode again. File Vault is ON.

UpDate 4; Decrypt/Re-Encrypting did not correct the issue for me, it got worse, had to unplug and walk away for about an hour. The only thing that has worked is turn off the sleep mode {Choose Apple menu > System Preferences, then click Energy Saver}.

It appears that everyone's hardware and configuration differences have an effect on the fix (or no fix). I'm not a software engineer, but it's obvious that 10.13.4 created the sleep mode/log on problem and 10.13.5 made the problem worse. It's also obvious that there is a root issue (one if not more) revolving around the sleep mode. Hint Hint Apple!