Sleep Wake Failure with High Sierra 10.13.2

A couple of days ago I updated my iMac to macOS 10.13.5 and today has been the first real day that I have been able to try my Mac since the update. I switched it on this morning at 8am and then put it to sleep and then this afternoon I woke up my iMac and for the first time everything worked without any issues. My iMac still wakes from safe sleep mode but this I can deal with but after it did it's thing, everything all worked OK and I did not get any sleep wake failure error message.

Currently I do not allow any bluetooth device to be used to wake my Mac up from sleep, I will re-actavite this feature soon and try it again. I'm not yet holding my breath that it might be fixed but at the moment it's defiantly looking slightly better.

I'll post again once I have switched on the bluetooth feature.

So much for my desperate hopes the SWF saga would be finally over. Unfortunately, I did not have to wait for iDeMi's reply. After a month with the .5 beta without any problems, the dreaded double-chime of the SWF reboot returned. This is only a quick recap for the sake of continuity.

My hopes were quietly propped up by the lack of the usual daily notifications from the two SWF threads. Since people generally write more about problems than they do about the absence of such, it seemed there is a faint chance the solution might have been found, at last. Looks like it hasn't.

It should be pointed out that there definitely is a difference after the .5beta update in my case, at least. It has been a great relief that for a month my work was free of the daily SWF reboots, which I had mercilessly experienced for months before that. However, as I already mentioned in my first post .5beta update comment, it did not seem very convincing that a complete solution has been found, because the sleep state appeared different and not going to a hibernate-like mode.

For the sake of completeness, it has to be clarified that during all this time I always left the iMac to follow through the power management set period of display and computer sleep (5/10 min). Yesterday for the first time I used the 'apple menu' sleep command, which I used to do in the long distant past, before the SWF plague. It could have been coincidental, but having used the 'sleep' command combined with the passing of the arriving of 'autopoweroff' state, which most certainly invokes hibernation, appears to have caused this horrible SWF again, after otherwise uneventful and so much hopeful month.

Such a disappointment!

Pleased to read that things have started to look promising, Stitchy. Glad that some of my efforts have been of help. Thank you for your kind mention. Your comment is the closest to my understanding of the problem.

We may not be out of the woods yet, as I think that the 10.13.5 version may have only modified the 'sleep' state, so that hibernation now takes place only when autopoweroff is effected (typically after about 3-4 hours). This may only reduce the probability of processes clashing, as there is more chance for most completing, which could have been an issue with an earlier hibernation effect.

All this, of course, is still hypothesising before time or apple confirms the results. We hope.

This is really bizarre. I have not experienced a single SWF for two weeks after updating to 10.13.5. This is in complete contrast to the SWF reboots I had every day for months before that. Extended comment follows ...

Logan, only a small addition to jtonn's comment, the SWF problem discussed in this thread involves arbitrary, unintended and complete system reboots. Assuming this not being the situation in your case, it could be related to my previous comment, suggesting that the 10.13.5 also modifies the pmset parameters default values (possibly in an attempt to address the darn SWF). It is unlikely that people have kept records of what the settings were before their updates, but if someone has this could help corroborate my guesses.

If it turns out that an automatic and unannounced change of a setting is used to avoid rather than eliminate the SWF issue, in some cases it may not work and in others, like Logan's for example, it could even make things worse.

Requiring specific parameter value limitations, in order to avoid underperformance or malfunction, at the least should be officially documented, if not completely removed, as parameter ranges should work for all allowed vaulues for all users without product performance deterioration.

I use Parallels too and I think its "checking for update" don't cause the problem. Instead of this, every time that my Mac (High Sierra 10.13.5) goes to sleep mode I have to reboot later... and almost every time Parallels was running when the failure happened.

Here is my tuppence of an update. Following a sudden and disappointing disruption of about a month of SWF-free interval on 10.13.5 and the subsequent resurrection of hope, a week ago, with moving to 10.13.6, kindly prompted by jtonn, I have been without SWF events since. I shall deem this a miracle, since no reasonable explanation has been put forward and my iMac has been running the same applications all the time since the beginning of this sorry saga. Just hope this is not yet another disposable miracle.

I found it helpful to quit all of the apps at night. Then it doesn't have the sleep mode issue so bad. I also just started turning off the computer every night - that really solved the problem.

For those of us that use CAD- the problem is CAD doesn't upgrade their software as fast as apple is creating new operating systems. SO be careful..

Yes I absolutely agree. I have tried reinstalling HS already and the same problems just continue. The only way forward is to go back unfortunately.

I agree with you on this. I too installed beta 4 and have no sleep wake failure ever since. I hope Apple finally crushed this nasty bug.

High Sierra 10.13.4

The problems seem to have cropped back up after the steps I had listed above. Would be very curious if disabling "Put hard disks to sleep when possible" helps at all...

It isn't a problem with the update. I do not have such a problem. Didn't have a problem with 10.13 or 10.13.1 either. My suggestion is a problem in the underlying system you upgraded. So, the first thing I will recommend you try is this:

1. Resetting your Mac's PRAM and NVRAM.
2. Reset the System Management Controller (SMC) on your Mac - Apple Support.
3. Boot into Safe Mode - this takes longer than normal.

The second thing you want to do is:

Repair the Drive for El Capitan or Later

1. Restart the computer and after the chime hold down the Command and R keys until the Utility Menu appears.
2. Select Disk Utility and press the Continue button.
3. Then select the indented (usually, Macintosh HD) volume entry from the side list.
4. Click on the First Aid tab in the toolbar and wait for the Done button to activate. Click on it, then quit Disk Utility.
5. Select Restart from the Apple menu.

The third thing to do is: Download and install the macOS High Sierra 10.13.2 Combo Update.

That's it for now. After the Combo Updater is completed your computer should restart. However, if it does not then restart the computer normally.

I have the same problem since the 10.13.2 update... waking from sleep has a very high chance of crashing. I have the Macbook Pro (Retina, 15-inch, Mid 2015).

None of these suggestions worked for me:

1. resetting PRAM and VRAM

2. resetting SMC

3. starting in safe mode

4. repairing with firstAid

5. formatting the disk and reinstalling macOS 10.13.2

The thing that makes me sad is that we can't go back to 10.13.1 or 10.13.0. Or can we?

This is a tragedy, first Apple struggle with the root backdoor login, and now this...

I only use Mac, but now consider Windows.

Can someone please tell Apple to rehire thaws test engineers again and get serious about business?

T9

Just love how I get woken up at random times with this ridiculous downgrade High Sierra 10.13.2 I waited 4 months to upgrade and now issues with my MBP and whatever the recent update on Iphone 6 Plus. Really thinking of going back to Windows and an Android phone as this is like the Windows Vista nightmares all over again! Disappointing and frustrating.