Mac Won't Wake From Sleep? 13 Fixes That Actually Work

You close the lid, come back an hour later, and your Mac is a black rectangle that won't respond to anything. Keyboard, trackpad, mouse clicks — nothing brings the screen back. This is one of the most disruptive Mac problems because it usually happens at the worst possible moment, mid-workday, with unsaved documents open. It also feels scarier than it usually is: in the vast majority of cases we see at IT Cares, a Mac stuck asleep is a software or peripheral issue, not a dying logic board.

This guide walks through all 13 fixes, ordered from the fastest (try this first, it works more often than any other single step) to the deepest diagnostic tools built into macOS. We also cover how to tell a "won't wake" Mac apart from a Mac that's genuinely dead, and how to read the built-in crash log that names the exact cause.

Sleep-wake failures affect Intel and Apple Silicon Macs differently, and the fix that resolves one user's freeze can do nothing for another's — which is exactly why so many people spend hours resetting the same setting repeatedly with no change. The approach that actually works is diagnostic: identify which category your freeze falls into (a peripheral conflict, a power-management bug, a background task stall, or genuine hardware wear) before picking a fix, rather than trying every fix in a random order. This guide is organized so you can do exactly that.

We see this exact complaint constantly in our Montreal repair shop and through remote support across Canada — it's one of the top five Mac issues we're called about, right alongside overheating and slow performance. The pattern is consistent enough that we can usually narrow down the cause within the first two or three diagnostic questions, and this guide reflects that same triage order.

Why Macs Get Stuck in Sleep: The Short Version

When a Mac sleeps, macOS powers down almost everything except a small amount of RAM (to preserve your session) and a low-power monitoring circuit that watches for a wake signal. Waking up means re-powering the CPU, GPU, storage controller, and every connected peripheral in a specific sequence. If any single device in that sequence — most often an external display, USB-C hub, or Thunderbolt dock — fails to respond correctly, macOS can hang indefinitely waiting for it, leaving you with a black screen that never returns.

This is a fundamentally different failure mode than a crash or kernel panic, which is why the standard "restart and hope" advice for general Mac problems doesn't always apply cleanly here. A crash happens because something actively went wrong; a sleep-wake hang happens because the system is patiently waiting on a response that simply never arrives. That distinction is exactly why disconnecting the unresponsive peripheral, rather than reinstalling macOS outright, resolves the issue so much more often than people expect.

Symptom	Likely Cause	Where to Start
Black screen, fan silent, no light	Deep sleep failure or true power-off	Fix #1, then Fix #3 (force restart)
Black screen, fan audibly spinning	Mac woke internally but display didn't	Fix #2 (unplug displays/docks)
Wakes fine alone, freezes only with monitor connected	Display/dock re-negotiation failure	Fix #2 and Fix #6
Random freeze a few minutes after waking, not immediately	Power Nap background task stalling	Fix #7
Started right after a macOS update	Known point-release bug	Fix #5 (update again) or Fix #9 (downgrade info)

Use this table to jump to the most relevant fix first, but if you're not sure, work through the list in order — it's ranked by how often each step resolves the issue in our repair shop.

13 Fixes for a Mac That Won't Wake From Sleep

Common Mistakes That Make a Frozen Mac Worse

Before you keep going, it's worth flagging a few habits that make sleep-wake problems harder to diagnose or, in rare cases, genuinely worse. The most frequent one we see is repeatedly holding the power button for 20-30 seconds "just to be sure." Ten seconds is enough to force a shutdown; holding much longer than that on some Intel models can, in specific firmware states, trigger a different low-level reset than intended. Stick to the documented 10-second window.

The second common mistake is resetting the SMC and NVRAM over and over as a first resort before ruling out a peripheral. Because these resets are quick and don't require any technical knowledge, people default to them repeatedly, sometimes daily, without realizing the actual cause is a $30 USB-C hub sitting on their desk. If you find yourself resetting the SMC more than once every week or two, stop and go back to Fix #2 — disconnect every peripheral for a full day and see if the freezes stop entirely.

The third mistake is ignoring the Console.app logs entirely and jumping straight to a full macOS reinstall or a trip to the shop. The Sleep Wake Failure log is free, built into every Mac, and frequently names the exact culprit in plain text within the first few lines. Even non-technical users can usually spot a recognizable app or driver name once they know to look for it — skipping this step means solving the problem by trial and error instead of by evidence, which typically costs far more time in the long run than the five minutes it takes to open Console and search.

A fifth habit worth mentioning: closing the lid and immediately traveling with the Mac, assuming it's asleep, without confirming the screen actually went dark first. If a wake-related bug causes the Mac to stay partially awake inside a bag, the combination of heat buildup and battery drain can turn a simple software freeze into a separate, unrelated overheating or battery-health problem by the time you open the lid again. A quick glance to confirm the display has gone fully black before closing the bag takes two seconds and avoids compounding one problem into two.

Finally, don't assume that because a fix worked once, the problem is permanently solved. Sleep-wake issues caused by a specific macOS version bug, for instance, can reappear after the next update if Apple reintroduces a related regression — this has happened multiple times across recent macOS release cycles. If a resolved issue comes back weeks or months later, it's worth re-checking Console.app rather than assuming it's the exact same cause as before.

Reading a Sleep Wake Failure Log Like a Technician

The SleepWakeFailure-*.panic file in Console.app looks intimidating, but you only need to read three things: the timestamp (confirm it matches your freeze), the "last loaded kext" or "active driver" line near the top (this names the software component running when the hang occurred — a Thunderbolt driver, a specific USB controller, or a VPN kernel extension are the most common), and any line mentioning "AppleUSB," "IOThunderbolt," or a third-party bundle identifier (things like com.cisco.anyconnect or a printer driver bundle). If you see a third-party bundle identifier repeatedly across multiple crash logs, that app or driver is your cause — update it, or remove it and test again.

If the log only ever shows Apple system components (anything starting with com.apple.) and never a third-party name, the cause is more likely a macOS bug or a hardware issue rather than an installed app — prioritize Fix #5 (update) and Fix #13 (hardware check) in that case.

How Common Is This, and Is My Mac Actually Dying?

Sleep-wake failures are one of the most reported Mac issues across Apple's own support community, MacRumors forums, and Reddit's r/mac and r/MacOS communities, spanning every hardware generation from late-Intel MacBook Pros through the newest M-series chips. That volume is itself useful context: this is a widely shared, well-understood category of problem, not a sign that your specific unit is uniquely defective. Apple's own engineering teams track these reports closely, which is part of why sleep-wake fixes appear so consistently in point-release notes.

That said, frequency matters. An occasional freeze — once every few weeks, especially traceable to a specific peripheral or right after connecting a new accessory — is a normal, low-priority nuisance that the fixes above will resolve. A freeze that happens every single time the Mac sleeps, regardless of what's connected, disappears in Safe Mode, and returns the moment you boot normally, is a stronger signal of either a stubborn software conflict or, if it persists through a clean macOS reinstall, genuine hardware wear.

Age is a relevant factor for hardware-related causes specifically. Batteries on Macs older than 4-5 years are statistically more likely to have degraded to the point of affecting power delivery during the wake sequence — you can check battery health at System Settings > Battery > Battery Health. A battery reporting "Service Recommended" alongside frequent, unexplained wake failures on an older MacBook is a reasonable candidate for replacement, and often resolves the freezing as a side effect.

Certain hardware generations have also had well-documented, temporary issues that Apple later resolved: some early 16" MacBook Pro Intel models had a reported graphics-switching wake bug tied to discrete GPU power-down; some first-generation M1 MacBook Air units (fanless) showed occasional wake delays under specific external-display combinations before firmware updates addressed it. If you're running one of these models and the freeze started around a specific known macOS or firmware version, checking Apple's release notes for that version — searching "[your Mac model] wake issue [macOS version]" — often surfaces the exact bug report and confirms whether an update already fixes it.

Frequently Asked Questions

Why does my Mac go to sleep and never wake up?

The most common cause by far is an external display, USB-C hub, or Thunderbolt dock that fails to re-initialize when the Mac tries to wake — the Mac hangs waiting for a response from the peripheral that never comes. Other frequent causes include a corrupted power-management state (fixed by an SMC reset), a buggy macOS point release that Apple later patches, or Power Nap triggering a background task (Mail sync, Time Machine, an App Store download) that stalls partway through. Disconnect every peripheral except the charger and test again before assuming it's a hardware fault — this single step resolves the majority of cases we see in our repair shop.

Is it safe to force restart my Mac when it won't wake?

Yes. A force restart (holding the power button 10 seconds) is safe for the Mac's hardware and is the standard Apple-recommended step when nothing else brings the screen back. The only real risk is losing unsaved work in open documents, since a force restart doesn't give running apps a chance to save first. Apps with continuous auto-save — Pages, Notes, Keynote, most modern software including browsers — are unaffected. If you were actively editing in an older app without auto-save at the moment it froze, that specific change could be lost.

Can an external monitor really cause a Mac to freeze on wake?

Yes, and it's the single most common cause of Mac sleep-wake failures in real-world repair cases, especially with USB-C/Thunderbolt docks, DisplayLink adapters, and multi-monitor setups. When the Mac sleeps, the display's video circuitry powers down; if it fails to re-negotiate the connection on wake — a firmware timing issue on the monitor or dock's side, not the Mac's — macOS can hang indefinitely waiting for a handshake that never completes. Test by fully disconnecting all displays and docks, letting the Mac sleep, and waking it on the built-in screen alone for a few days before reconnecting one peripheral at a time to isolate the exact culprit.

Should I turn off Power Nap to fix sleep-wake issues?

If you're experiencing wake failures, disabling Power Nap is a reasonable and low-risk troubleshooting step. Power Nap lets a sleeping Mac periodically wake briefly to check Mail, sync iCloud and Photos, back up with Time Machine, and download App Store updates — all invisibly, while the lid stays closed. On some macOS versions and hardware combinations, one of these background wake cycles can stall and leave the Mac in a half-woken, unresponsive state that looks identical to a full freeze. Go to System Settings > Battery > Options and disable Power Nap on both battery and power adapter, then monitor for at least a week to see if the freezes stop.

How do I check what caused a Mac sleep-wake failure?

Open Console (Applications > Utilities > Console), select your Mac's name in the sidebar under Devices, and search for "Sleep Wake Failure" — or browse directly to ~/Library/Logs/DiagnosticReports in Finder (press Cmd+Shift+G to jump to that path) for files named SleepWakeFailure-*.panic. These logs name the specific driver, kernel extension, or process that was active when the freeze occurred, which tells you within a couple of minutes whether the cause is a peripheral, a third-party app, or a deeper macOS bug.

What's the difference between a Mac that "won't wake" and one that "won't turn on"?

A Mac that won't wake from sleep still has power — the fan may be spinning, a light may be on, and it responded completely normally before you closed the lid or let it idle. A Mac that won't turn on at all shows zero signs of power whatsoever (no fan noise, no chime, no light, no charging indicator) even when plugged directly into a known-working outlet. These are fundamentally different problems: one is almost always a software or peripheral state issue, the other usually points to a charging circuit, battery, or logic board fault. If your Mac shows absolutely no sign of power, see our guide on a Mac that won't turn on instead.

Is a Mac that won't wake from sleep a hardware problem?

Usually not. In our repair experience, roughly 90% of sleep-wake failures are resolved by disconnecting a problematic peripheral, resetting the SMC, disabling Power Nap, or installing a macOS update — all software-level fixes with no parts replacement required. True hardware causes (a failing logic board, a degraded battery affecting power delivery, a faulty display cable) are less common and are usually accompanied by other symptoms: repeated kernel panics unrelated to sleep specifically, visible battery swelling under the trackpad, or the exact same freeze happening even with zero peripherals connected on a freshly reinstalled copy of macOS.