Since installing 10.13.2 I have a sleep wake failure on iMac. Was working perfectly before installed latest update on Dec 8.
This is not an uncommon problem but the "fixes/solutions" one reads on the internet are all over the place.
Is there a fix or is this simply something only Apple can solve for all those now plagued by the problem? It is irritating in the extreme.
iMac, macOS High Sierra (10.13.2)
I had the same problem on a macbook air (13-inch, Mid 2012, macBookAir5,2) since OSX 10.13.2.
I tried everything proposed on this and on other forums.
Recently, I did 2 things:
1) I downloaded 10.13.4 FULL installer (no combo, the full installer) and reinstalled High Sierra, over the previous installation.
2) I replaced the SSD disk few years ago, I have a OWC Aura Pro 2012 480GB SSD disk. I became aware of a conflict between high sierra and old OWC aura disks. I updated the firmware version to 603ABBF0 (got it from here: OWC Mercury SSD Firmware Updater via USB Drive or CD/DVD Disc). The problem also affects other OWC Aura models (http://macosuninstaller.com/one-click-removal-tutorial/unfortunately-time-owcs-a ura-ssds-not-support-macos-high-sierra/).
Since 1 and 2, the black screen/freeze after sleep, as well as a blinking folder with question mark at boot issue, stopped. I keep my finger crossed. Hope this helps.
I updated to 10.13.6 once it came out last week. I still have Power Nap turned on but I notice that my iMac (late 2013) actually seems to be asleep in the morning before I wake it. Under 10.13.5, I could hear it running although the screen was off while on PN. So, something has changed with this latest update.
Next step will be trying to turn PN off to see if that restores the old behavior that existed under 10.12.x
OS Version: Mac OS X 10.13.5 (Build 17F77)
Architecture: x86_64
Report Version: 26
Data Source: Stackshots
Event: Sleep Wake Failure
Duration: 0.09s
Steps: 9
Hardware model: iMac13,1
Active cpus: 4
Time Awake Since Boot: 130000s
Only a few days back I thought of writing an update, just to mention that the current OS ‘sleep’ mode is somewhat strange, with the computer every now and then apparently not going to the state of system sleep (where the current work space image is saved to persistent memory). Every time this happened, a note would appear next to the power management setting, looking like this:
I would have speculated that rather than resolving the SWF problem, the issue has been somehow suppressed by various restrictions on the ‘system sleep’ mode, effectively preventing sleep, when a situation arises that could potentially lead to SWF. This, suspiciously, is NOT a solution to the problem, just a workaround, which was bound to fail sooner or later and, in my case, apparently it just did.
If Apple have decided that compromising the power management settings would somehow sweep the SWF problem under the carpet, then many unsuspecting users are probably unaware that while believing they no longer have the SWF events, their work is less protected, because their computer would not be ‘sleeping’ as specifications would require.
I have the same issue with the new I9 MacBook pro. This issue is still present after the upgrade to Mojave. Once the screensaver starts, roughly 25 mins later a reboot takes place and you to provide my password to log in (touchId will not work)
This happens you set a corner to be a hot corner that triggers the screen saver and you are required to log in to get back into the MacBook.
If you close the lid you do not have the issue. Once you reopen the lid you can use touchId to get into the MacBook and all applications are in the same state as you left them.
I will try lock screen from the apple in the upper right corner next to see if that makes any difference after roughly 25 mins?
Have you tried to re/move time machine backup and create new one from scratch?
10.13.2 additional upgrade (and later 10.13.3) solved my problem on macbook 12 2015 :-) (after months....thats the negative side...
Hello, TJBHK? The latest Mac Operating System is v10.13.3, not v10.3.2. Try to install v10.13.3: this might fix your problem?
Just an Idea. Good Luck. :-)
Apple replaced my SSD and it issue doesn't come up anymore. I am glad my issue is fixed but I highly doubt few hundred users all the sudden has hardware issue since HS install.
The only solution which I believe to work is to install Sierra.
I've "solved" it by (a) going into Settings and setting the Mac to never sleep; and (b) by mentally resolving not to by other Apple products in future.
I will say, that if I keep chrome running when it goes to sleep, there is like a 75% chance I will awake next morning to find the computer stuck in startup.
Clue, #1
I am on 10.13.5 beta (17F66a), but unfortunately encountered the problem once again. :-( Will now try with disabling "Put hard disks to sleep when possible".
iDeMi, could you, please, elaborate. What made you say this? What bug are you referring to exactly? What machine does it happen on? What effect precisely are you experiencing?
PS: 10.13.6 update notification came at last; will follow through.
Same problem here with a MacPro. I can't really tell if the MacPro is sleeping but my main indication that it is not is the RAID array will not sleep at all. Have to shut the system down nightly until Apple fixes bug local Apple store states.
Same problem. 2012 iMac. Updated to 10.13.2, sleep is broken. When I come back my machine has reset itself, I have to login and wait for everything to come up again. This all seems related to graphics cards and processors. I haven't touched the hardware, so the Apple OS update fouled up the system.
Sleep Wake Failure with High Sierra 10.13.2
