Sleep Wake Failure with High Sierra 10.13.2

I originally got on this discussion because my iMac (late 2013) was just really really slow to wake up from sleep. I fortunately haven't been getting the gray screen and all the other start up problems that you are all getting (yet at least). But besides this issue - which is major - this OS is full of problems. I've been dealing with a software of mine that won't launch since the install. Turns out the only solution was to rebuild a new user account. Sounds simple, but it screws up everything. I'm still getting permission errors, backups not running and printer drivers doing crazy things. Plus the Apple Photos app is totally not working - when you go to People (think it used to be faces) it crashes. Other discussions say to rebuild the catalog, but it doesn't work. The whole High Sierra OS is a mess. Apple is in total denial when I call. And their default answer is to wipe the mac completely and do a clean install. Like my business will survive more down time. Its awful. I thank all of you on this thread for continuing to call them and make them aware of this issue (and others) so they will (hopefully) fix some of this stuff.

Question: when we send in the "report to Apple" does it actually go to anyone? It sounds like most people are clicking on that every time this happens, but there has been no response from Apple. Why no "we are aware of this frustrating problem and are working to fix it" type of response? We probably all have spend thousands on Apple products, and this type of non-response is unacceptable.

I had a senior advisor tell me that those "anonymous" error reports to Apple are evaluated to discover error trends, but who knows? I guess only Apple knows and they won't say. Apple has really been tight lipped and non-responsive on most of the problems that the crappy High Sierra has caused. Very few of the 9 different advisors that I have contacted knew anything about the sleep wake failure before I talked to them and many tried to get me to wipe my drive and start over which fortunately I didn't do since no one on this discussion had any good results from doing that. I am afraid it could be months or longer before they come out with a solution. My iMac had not been restarting as often since I turned on Power Nap. Apple didn't even know that was a temporary work around.

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.

I did a pretty extreme test. I erased my disk, installed a fresh copy of High Sierra without importing any user or data, without installing any program, just High Sierra. And I still had the Sleep Wake Failure!

I erased my disk again and installed Sierra and no more Sleep Wake Failure. Then I contacted Apple about these tests and Senior Advisor was helpless. She told me I have to go to High Sierra again to see if the problem happens again... Pffff I just know this will happen again! I told her to read this forum. It did not seam like a knowed issue for her. Since I don't have High Sierra anymore, she told me she could not help me.

Hello brummmmme. This is worth framing!

brummmmme wrote:

I did a pretty extreme test. I erased my disk, installed a fresh copy of High Sierra without importing any user or data, without installing any program, just High Sierra. And I still had the Sleep Wake Failure!

I erased my disk again and installed Sierra and no more Sleep Wake Failure. Then I contacted Apple about these tests and Senior Advisor was helpless. She told me I have to go to High Sierra again to see if the problem happens again... Pffff I just know this will happen again! I told her to read this forum. It did not seam like a knowed issue for her. Since I don't have High Sierra anymore, she told me she could not help me.

By far the most revealing test and confirmation of the nature of Apple's Sleep Wake Failure calamity.

You could have recommended reading Joseph Heller to your Senior Adviser.

tingdong, could you be a little more specific, please. What is this fix and where can it be found?

just for completeness, post-brummmmme's contribution, I can confirm that, while considerably less conclusive, my experimentation strongly suggests that there is no connection (at least on my iMac) between any particular programs or combination thereof and the Sleep Wake Failure occurrences. They keep happening regardless and frequently.

It's frustrating and tiring, too.

I think that the "fix" tingdong was referring to was the 10.13.3 Supplemental update that fixed the Messages crash that was caused by entering a specific sequence of characters. I don't think that anything else was fixed. I have experienced the spontaneous restart problem even after installing that update.

I have just done a NVRAM restart and crossing my fingers it has woken up 3 times now including leaving it on all night. It hasn't solved the online banking though. That is a problem between Safara and my bank.

Close computer down and leave all night including 15 mins unplugged from wall.

Start computer and push Alt + Cmd+P+R immediately and hold down either for 20" or until the wake up sounds twice.

Release keys. Computer will start.

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:

After having installed the latest developer beta 4 of 10.13.4 (17E170c), I have not experienced any sleep/wake failures within the last 3 days since the update was installed. I also restored the default Energy Saver settings with the Power Nap setting disabled. This problem has also been occurring for me since the original High Sierra install version 10.13.1 and I have a Late 2012 iMac. Has anyone had the problem still occur after installing the latest developer beta 4 update of 10.13.4? Hoping that is the version with the code-fix we've all been waiting for. Fingers crossed!

cswimbound, thanks for the ray of hope. My late 2012 iMac has been malfunctioning with the SW FailUre since installing the wonderfully crafted High Sierra in November. I hope the .4 release will finally fix the problem and not lead to any other errors. I have certainly learned my lesson to not "upgrade" my OS, or at least until it is in its later versions.

Keeping my fingers crossed too.

I've been testing solutions since yesterday. Disabled pmset autopoweroff, didn't work. Changed hibernatemode to "0", didn't work. I increased the standby time to 24 hours, and autopoweroff as well. Didn't work.o

So I decided to test the apps I used to let opened while sleep. Usually, I let several Chrome tabs for the Google Apps I use, and the TeamViwer to get instant acces to other computers. Since yesterday, I started to close TeamViwer and no issues until now.

I will set the autopoweroff and standby time to it's default and see what happens.

Just saying, by now, maybe the issue happens because some apps. It's not an excuse to Apple ignore this problem. But can be a solution. Opening an app every time you open the lid can be less painful than restarting the whole system.

TJBHK:

Have you installed 10.13.4 developer beta 4? That seemed to fixed the issue for me and I haven't had a sleep wake failure for the last 4 days now, with energy saver settings restored to defaults. If you haven't installed the latest developer beta update (17E170c), try it out and hopefully it also resolves it for you as it did for me (fingers still crossed).