Sleep Wake Failure with High Sierra 10.13.2

Very interesting. On my system, disksleep and displaysleep are both set at 10, and sleep at 1. I've now set sleep to 10, let's see what happens...

My particular variation on this problem (now in 10.13.6) is that I experience the sleep wake failure when connecting my MacBook Pro mid-2015 to my Thunderbolt Display in closed-clamshell mode.

I have tried the lock method and it resulted in the same result as the screensaver options.

No, it's affecting them too. I've got a MacBook Pro (Retina, 15-inch, Mid 2014) and _had_ this issue too. It started after upgrading to 10.13.2

I formatted my hard drive in HGFS and installed Sierra to escape the problem. A few days later (after making a clone and deciding I wanted to feel some pain) I upgraded again because...well I didn't really expect the bug not to return but...well it didn't.

So, I've got rid of this _very_ annoying bug which was massive pain but I've no idea why and how it worked. One thing to note is: I tried a clean install of High Sierra and that didn't fix the problem.

Sorry for my English. My problem was resolved after uninstalled ESET antivirus for Mac. So if you have this Application on your iMac , uninstall and see if its works. I tried with SMC and NVRAM reset but the problem still remain. I hope helped some people. PS: I have Mac OS High Sierra 10.13.3.

Nothing for a few days and then it comes back again. This is only the last one out of several in the past few days:

Report Version: 26

Hardware model: iMac13,1

Time Awake Since Boot: 36000s

Binary Images:

...

The randomness and absence of association with a particular event or activity is maddening.

Yesterday evening, I turned off WiFi on my MacBook Air, and unplugged an USB key I keep connected to the MBA.

Selected sleep from the apple menu, and then I close the lid.

This morning I opened the lid, the "apple" light on the back turned on, but I was welcomed by a black screen (not totally black... I would say a low luminescence, screen less "dark" than when turned off). Nothing helped: close/open the lid, type password blindly, touch the power button, etc. Only way to get out, a forced restard, pushing the power button.

Once rebooted, I did not get the "kernel panic" screen, but the login page (I have automatic login on).

It sounded like an interesting hypothesis, but at list on my system, does not appear to be the cause.

PS: over the weekend I did a reinstall of High Sierra 10.13.3 + recent update.

I don’t know if you have seen any of my previous posts because I’m not sure if replies that I make to other people are readable by all. I have a 21.5” late 2012 iMac and I started having the Sleep Wake Failure the day I “upgraded” to highly flawed High Sierra (Nov. 27, 2017) I am now working with my 9^th Apple advisor and have done all sort of testing on my machine. They have never found any problem with my hardware or any of my apps. They keep telling me that Apple is aware of the problem and the engineers are working on an iOS upgrade to fix the problem. There have been so many other serious defects in HS that I think the Wake Sleep Failure has been pushed to the end of the line. I have installed the 10.13.3 Supplemental and it still causes the failure. There are 2 things that I have found that help some. If I shut down my machine every night I get far fewer restarts and it takes less time for the computer to boot from a fresh turn on that it takes it to restart itself. The other thing that helps is I have enabled Power Nap in the System Preference, Energy Saver. I never used this setting before HS but when I have it checked I have fewer slow wakeups and self initiated restarts. Everyone who is experiencing the annoying Wake Sleep Failure needs to call support and complain otherwise they will never get it fixes. Good luck.

I have taken screen shots of every sleep wake "Error Report" that I forwarded to Apple (yes, I have a lot of screen shots, but it captures the date and time to show frequency and shows when it started, which is right after I upgraded to HS). I've also taken screen shots of the same problems others are having as a result of HS. If the constant sleep wake error creates other problems (in addition to just being annoying), then I will have Apple replace my computer. Hopefully they do the right thing and fix it soon, but if not, I'm not going to just accept it. People don't accept cold fries at McDonald's, I'm definitely not going to accept this.

My brand new office iMac is ethernet only. Wake from sleep problem as well.

It only happens when I put it to sleep at the end of the day.

During the day, I set it to never sleep, display goes dark only.

Keeps doing it regardless. Every day.

I do sympathise with everyone suffering this problem. It is not only the time wasting and damaging effect of the SWF that we all have to bear, but the lack of recognition and acknowledgement is a further insult to users and loyal customers.

Nevertheless, we have no choice but keep trying. As we have talked earlier on this thread, setting or not PN can only circumvent the problem, but cannot be a resolution. This and any other possible change of how one works may only superficially alleviate the SWF problem. The bottom line is:

It should not happen whatever the user's choice of preference settings!

Being realistic, we should not fail to acknowledge that SWF apparently affects only some computers, as no matter how significant the number of people who have reported it here, there must be many others who do not appear to be experiencing the issue. To be entirely fair, I am aware of two MacBookAir laptops, belonging to relatives, running High Sierra, which have not shown this malfunction, at least over the past month and a half, since they have upgraded the OS. (unlike my iMac, which has done the SWF since day one of HS)

This seems indicative that the SWF problem (while still likely an OS fault) might be also triggered circumstantially. That is depending on particular type and combination of application software in use. Unless I have been pushed to the state of hallucination, it seems to me that the SWF happens on my iMac differently, depending on the programs running. Initially I suspected my browser (deliberately not specifying), however now I have started to suspect that it is more the number of programs running, when the iMac goes to sleep, rather than any specific one.

I have experimented with various combinations, but it is not so simple, as I certainly have a lot more pressing work to do. If anyone can spare time and attention to try this (admittedly flimsy) hypothesis, I'd be curious.

Lost count. Sleep Wake Failure every day, some days more than once. A feeble curiosity - statistically most of the SWFs on my iMac happen in the mornings (9-11am GMT). Clearly this is an active time and perhaps more frequently the computer is left to go to sleep. But similar activities do happen other times of the day and it very rarely does SWF at night although it does go to 'deep' sleep every night.

Occasionally the applications that I'm running happen to be financially sensitive. The SWF inevitably causes disruptions, which cause my incurring loss. I believe other people, including on this forum, are affected similarly.

There has not been a single comment on this or other threads discussing Sleep Wake Failure, which reports a resolution provided by an Apple Support Adviser. No sign of anyone at Apple helping the situation.

And here is the first one of today.

Report Version: 26

Hardware model: iMac13,1

Time Awake Since Boot: 28000s

Binary Images:

I had this problem for many a month. Finally decided to erase disk, reinstall High Sierra and restore from time machine backup. In the process, somehow had to create another user. Don't remember the steps to get to the point where one had to create another user. In any case, I did create another user and restored files from time machine backup.

Have not had the problem for more than a month. The trick might be adding a new user and logging in as that one.

Hope it helps someone.

I was going to wait a few more weeks to be sure, but it looks like it's a Bluetooth issue for me too. I've been turning off the BT before sleeping the Mac for over 2 hours or so.

It's a hassle, I've got a USB mouse connected and I'm using it to toggle the BT for the BT mouse.

However, I've not had any sleep-wake restart for over two weeks. I will post if this changes, hopefully it won't.

Sadly, I was woken from a restful sleep about 3:30 am by the double startup chime on my late 2013 iMac. After a few days of running 10.13.5 with Power Nap enabled, I decided to try turning it off. All was well except that it was kind of annoying to wait for Safe Sleep to reload the contents of RAM that got backed up to disk sometime overnight. I figured it was a small tradeoff for having RAM contents safely tucked away in the event of an unexpected power failure. Sigh.