Sleep Wake Failure with High Sierra 10.13.2

Hello again, here is a brief comment by 'janisfromhamburg' posted on the parallel thread at Re: Sleep Wake Failure: Reboots only after upgrading to High Sierra. (I have also copied my comment on that thread further below.)

"Today I was at the Apple Store in Hamburg. One of the "Geniuses" said, they knew about the problem of the SWF after updating to High Sierra. He also said, it should be fixed with the next macOS-Update. I hope thats true."

This is probably the brightest flicker in this long dark and muddy tunnel of the Apple SWF experience. Ever since I started to keep track of the discussions on these threads, I have seen innumerable reports, describing various systems, setups and myriad of settings attempting to identify possible reasons for the darn SWF problem. Looks like individual circumstances could contribute to some extend, but that same variety also suggests that there has to be a common underlying reason. That reason unequivocally points to the HS OS update.

It is also evident that Apple Support staff are not in sync with the problem (with or without internal instructions not to acknowledge it). Some commentators on these discussion fora have suggested that we should not 'complain' here but go and raise the issue directly with apple support. While I agree with the latter and have personally been in contact with apple support, it is a fact that for so many months and so many reported attempts, not a single case has been mentioned, where apple support have been able to help resolving the matter. The discussions, especially here on the 'neatly' moderated apple website, should be taken into consideration and respected as a source of information from genuinely concerned and mostly supportive apple users. To deny their existence and the issues raised is plain irresponsible.

So, for once, there seems to be some hope that the SWF will be banished at last.

Ghogoh,

I see that you're still running 10.13.5. I suggest that you update to 10.13.6. I noticed changes in the way sleep behaves after updating. Under 10.13.5, my iMac would often be semi-awake (screen dark, hard drive spinning) when I accessed it in the morning. Under 10.13.6, that is rarely the case. I am still running with Power Nap enabled. Under 10.13.6, it will take about 5 seconds for it to come fully awake to where I can enter my password. Much better than the minute or two that it takes if it goes into Safe Sleep when Power Nap is disabled.

I had this same issue for awhile now. I finally fixed if tonight (I hope). Always double reset, wouldn’t come out of sleep when I opened it up. For some reason one of my USB ports stopped working too. I tried every reset, reinstall, SMC, PRAM, network configuration, energy saver settings, etc. None of it worked.

I did a complete wipe of the hard drive, installed the original OS by booting with internet recovery for facotry OS (Shift+Option+Command+R) and installing Mountain Lion 10.8 (mid-2012 MBP). Next I upgraded to Yosemite 10.10.5. I have NOT and don’t plan to upgrade up to High Sierra again. As of tonight... my computer is faster, it wakes almost immediately every time (so far) and my USB ports work again. We’ll see if it holds up. I will jusy have to use older versions of a few pieces of software for this machine, but it saved me buying a new one.

Fingers crossed! For any who still have the SWF problem after updating to 10.13.6, I highly recommend turning on "Power Nap" in your "Energy Saver" preferences. There were changes made in that release that have modified the behavior of my iMac when I wake it. It now seems to be "asleep" more often than not when I wake it in the morning. It does take about 5 or 10 seconds to come awake enough with a screen allowing me to enter my password, but that is preferable to the couple minutes when in "Safe Sleep" with Power Nap disabled. Those of you with an SSD may have the advantage as far as your machine becoming responsive.

Hi again. Ok, I may have discovered a work-around to this problem.

This morning I went to wake my (27" late 2012) iMac (OS 10.13.6) but it would not wake. I have Power Nap enabled, as this has been suggested may be good practice for the SWF... and for the last few occasions this seems indeed to have made a difference. However, today it would not wake.

I wondered if I were to press the space bar (or any other keys) for a time then, because Power Nap is enabled, the Mac would "wake" during one of these presses (to check for mail or whatever) and "know" that it's being asked to wake.

No joy.

It then occurred to me that if I were to give it a real jolt, then that may be sufficient to wake it. So I plugged in a USB-powered drive... and hey presto, the Mac burst into life.

This only happened this morning, so I haven't repeated the experiment - thus I only offer this as a possible solution, and would be interested to hear if it works for others. Please let me know. Thanks.

I'm having this problem too. The workaround - on a desktop machine - is to leave the thing on all the time by disabling sleep, rather than turning it off.

iMac (2012?) High Sierra 10.13.4

I reset the SMC on my iMac and it has been almost 24 hours without the dreaded Sleep Wake Failure. I'm keeping my fingers crossed!

Disconnecting my second monitor prevents the issue from happening for me.

iMac (27-inch, Late 2013) 10.13.5

chriskingdesign,

In the next revision of 10.13 look for an explanation of what problems Apple has solved.

I have disabled bluetooth wake and implemented what AndyJLew recommended and it appears to be working.

(Sleep Wake Failure: Reboots only after upgrading to High Sierra)

I say appears because it does not happen often enough for me to be sure at this point.

Neither of the things I mentioned seem to work individually and I could still be wrong that this has fixed the problem.

I have MacBook Pro (Retina, 13-inch, Early 2015) with the same problem. I went back to Sierra for a while (did that at the genius bar) and that fixed it. Then I assumed after some updates that it was safe to update to High Sierra again - and the problem is back once again with a vengeance!

My advice don't update to HS if you can avoid it.

I have a temporary solution which is to use an app called "InsomniaX" which prevents sleep on lid closure (although it has been known to create overheating problems so you have to watch that closely. I use this when I carry my laptop from one room to another (it the lid closed). Otherwise when I move around it pretty much aways crashes. For longer journeys the computer has to be completely switched off now.

I have found that it is better to shut down my iMac rather than let it go to sleep mode and have a sleep wake issue restart.

It takes about 2 minutes to boot up from a shut down vs 4 minutes for a sleep wake restart

Still a major inconvenience I wish I did not have to deal with!

Here is my story. It started about a week ago. I found my supposed-to-be-sleeping MacBook Air (HS 12.3.3) awake in the middle of the night, green screen with a folder with a flashing question mark. Hard reboot, everything back to normal. From time to time, I started to have wake-from-sleep issues (ie, open the lid, black screen, nothing happens, hard reboot using the power button).


The flashing question mark folder re-appeared almost every night, or in the morning when opening the laptop lid.


Tried everything I found in internet, including PRAM, SMC, safeboot, recoverymode and diskutility, reisntalled combo 10.13.3, installed the recent 10.13.3 supplemental. Nothing works.


Going through console system.log, I found a weird "5 [RE] Reachability changed" as the last entry before the freeze. See these examples:


Feb 21 00:27:35 DZ-MacBookProi5 uc[67]: 5 [UP] Transitioning from 3 to 1


Feb 21 00:27:38 DZ-MacBookProi5 com.apple.xpc.launchd[1] (com.apple.preference.displays.MirrorDisplays): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Feb 21 00:27:41 DZ-MacBookProi5 uc[67]: 5 [RE] Reachability changed

Feb 21 08:27:38 localhost bootlog[0]: BOOT_TIME 1519198058 0

Feb 21 10:55:45 DZ-MacBookProi5 CheckmateIdleDaemon[117]: The system WILL go to sleep...


Feb 21 10:55:45 DZ-MacBookProi5 loginwindow[122]: magsafeStateChanged state changed old 1 new 2

Feb 21 10:55:46 DZ-MacBookProi5 fud[30895]: objc[30895]: Class MobileAssetUpdater is implemented in both /System/Library/PrivateFrameworks/MobileAccessoryUpdater.framework/Support/fud (0x102ec4e10) and /System/Library/AccessoryUpdaterBundles/ApplePowerAccessoryUpdater.bundle/Conte nts/MacOS/ApplePowerAccessoryUpdater (0x102fd28f8). One of the two will be used. Which one is undefined.

Feb 21 10:55:46 DZ-MacBookProi5 uc[64]: 5 [RE] Reachability changed

Feb 21 11:18:41 localhost bootlog[0]: BOOT_TIME 1519208321 0

Isthat "Reachability changed" entry involved with the freeze? this is the last entry in system.log before the freeze. Anybody seeing the same entry?


As last resort, I tried to disable safesleep.

In /private/var/vm i found a sleepimage file, created on February 15 (when I started to have the issue, but it might be a coincidence).


I disabled safesleep (pmset -a hybernatemode 0), rebooted in recovery mode (CMD+R), disabled SIP (csrutil disable), rebooted, deleted the safesleep file, rebooted in recovery mode, enabled SIP (csrutil enable) and re-booted normally.


System has created a new sleepimage file.


In summary, I removed the old sleepimage, I left hibernatemode on 0. Let's see what happens.


ghogoh wrote:

Whichever the case may be, hundreds of Apple users, at least those showing on this and the thread I mentioned above, quite likely many more, have been affected over an extended period of time and this forum becomes as good as any for them to express their expectations from Apple to help resolve the issue.

It is, however, pointless to do so. If you want to express something to Apple, contact them directly. Use the Contact Support button at the top right of every page. Use the feedback page. Or, make an appointment at the Genius Bar at your local Apple Store. If you contact Apple in any of those ways, they track the issues. That's how they learn the scope of a particular problem.

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.

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.