Sleep Wake Failure with High Sierra 10.13.4

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.

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

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

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

Restoring to defaults and then turning on "prevent computer from sleeping automatically when the display is off" doesn't fix it (it does toggle the "sleep" setting, though). I'll try the settings you suggested.

I don't know what else to tell you, I am basically now keep submitting bug reports to Apple to push them to get it fixed. I am also doing this with clean machines and clean install to eliminate non-Apple related software issues.

Does anyone know a rough time frame of when we should expect OS 10.13.5?

Also, I've noticed my startup screen is now grey instead of the usual blurred background when turning the computer on. I'm sure this has been since the last security update. Is this normal?

MotoMcLovin wrote:

Does anyone know a rough time frame of when we should expect OS 10.13.5?

Also, I've noticed my startup screen is now grey instead of the usual blurred background when turning the computer on. I'm sure this has been since the last security update. Is this normal?

It better not be soon because this sleep-wake issue is still on beta 3. It seems each update release fixes something and breaks some new stuff.

10.13 is probably one of the worst OS I've seen. It is enterprise "unfriendly" or even "hostile" and buggy (#iamroot anyone?). I rather fall back to 10.12 if I can choose again.

I am having the same issue. Apple has really hit it out the park with 10.13.4. I had to roll back because they broke external displays, I didn't even have time to notice this issue. Then I installed it because the display issue was fixed, and now sleep is broken.

MotoMcLovin wrote:

Does anyone know if the latest beta 4 version of os 10.13.5 released yesterday has fixed the sleep/wake problem?

Nope. It's the same, freezes on password prompt on wake up from hibernate.

I also want to point out I am still on HFS+ due to File Vault security token issues

I have this problem, too.

- iMac 21" late 2012

- Fusion Drive

- FileVault enabled

Already reinstalled OS once (had some kexts, etc., that I didn't trust), problem remained after enabling FileVault.

Haven't played with Power Management Settings.

Haven't tried 10.13.5 Beta on this system (running it on other Macs, but this is my PROD machine, so my personal policy is against using Beta on that one - was burned once already by the issue where APFS conversion killed machines with FusionDrive)

Have filed Bugreporter ID 40155960 with sysdiagnose in order to help Apple to identify and solve the problem.

Never happened on my 2017 MBP or 2015 MB, where I've been using every 10.13 Beta version available since 10.13.0, and where I am also using FileVault as well as hibernation, so it seems to trigger on Fusion Drive/Bluetooth or other iMac-related aspects.

I've neglected mentioning the Bluetooth issue because my issue with the sleep/wake appears to be related to File Vault. However, I did notice that when I had File Vault enabled on my iMac, the battery life on my Apple bluetooth keyboard was depleted in just a few days. I have the older keyboard that uses the AA batteries and even though they're rechargeable, their typical service life is several weeks. With FV disabled, battery life is back to normal.

MotoMcLovin wrote:

Dare I ask if anyone knows if this issue has been fixed with the beta 5 version that's just been released? I feel we are getting close to the final release 😐

I am testing them now, on beta 4 Apple asked me to provide more logs for troubleshooting.

Currently there seems to be a change in the wake-hibernation behavior, I ran 'sudo pmset standbydelay 1 hibernatemode 25 autopoweroffdelay 1' and put it into hibernate immediately, when I woke it, it immediately went back to state it was in.

I am not sure if this issue is "fixed" considered I expect to see a FileVault password prompt (for security) - I will find out once more testings are done.

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!

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