<\/p>\n\n\n\n
Sometimes a MacBook Pro does something extremely annoying: you click Apple menu \u2192 Shut Down<\/strong>, the screen turns off for a moment, and then the Mac starts again by itself.<\/p>\n\n\n\n At first it feels like a normal restart, but actually it may be a wake\/power-management issue<\/strong>. The Mac begins shutting down, but a hardware, network, USB-C, monitor, dock, Bluetooth, or macOS power event wakes it again.<\/p>\n\n\n\n In our real case, the logs showed the issue was coming from the Wi-Fi\/network wake path<\/strong>, not from a normal app like Chrome, Slack, VS Code, or Docker. The key log lines showed Apple also notes that unexpected restarts can be caused by software or connected devices, so both macOS services and external hardware must be checked. (Apple Support<\/a>)<\/p>\n\n\n\n You may see one or more of these:<\/p>\n\n\n\n Modern MacBook Pros, especially Apple Silicon models, do not instantly go into a full electrical \u201cdead off\u201d state the moment you click shutdown. macOS shuts down in stages:<\/p>\n\n\n\n During this transition, a wake-capable service or device can send a signal. macOS may interpret that as:<\/p>\n\n\n\n \u201cSomething needs the Mac awake.\u201d<\/p>\n<\/blockquote>\n\n\n\n So the flow becomes:<\/p>\n\n\n Apple\u2019s own Battery settings include Wake for network access<\/strong>, which allows the Mac to wake so shared resources can be accessed; Apple documents that this setting can be changed to Never<\/strong> if you do not want remote\/network wake behavior. (Apple Support<\/a>)<\/p>\n\n\n\n In this case, this command was used:<\/p>\n\n\n The important output was:<\/p>\n\n\n This means the Apple Wi-Fi service was involved.<\/p>\n\n\n\n There were also repeated lines like:<\/p>\n\n\n Earlier, So the direct culprit was:<\/p>\n\n\n In simple language:<\/p>\n\n\n\n The Mac was being woken by the Wi-Fi\/network subsystem during or shortly after shutdown.<\/p>\n<\/blockquote>\n\n\n\n The later After the Mac restarts automatically, immediately open Terminal and run:<\/p>\n\n\n Also run:<\/p>\n\n\n If you see If you see panic, crash, or shutdown cause errors, it may be a crash\/restart problem.<\/p>\n\n\n\n Run:<\/p>\n\n\n Look for these:<\/p>\n\n\n Example interpretation:<\/p>\n\n\n\n In our case, the later output showed:<\/p>\n\n\n That was a good sign because it meant there was no ongoing kernel blocker after the restart.<\/p>\n\n\n\n If logs show Example output:<\/p>\n\n\n or:<\/p>\n\n\n Interpretation:<\/p>\n\n\n\n In this real case:<\/p>\n\n\n So the direct culprit was Wi-Fi wake.<\/p>\n\n\n\n Run:<\/p>\n\n\n Then verify:<\/p>\n\n\n Expected output:<\/p>\n\n\n Meaning:<\/p>\n\n\n\n Apple\u2019s Battery settings also expose related options such as Wake for network access<\/strong> and Power Nap<\/strong>, where available. Apple describes Power Nap as allowing checks for mail, calendar, and iCloud updates while sleeping, and Wake for network access as allowing the Mac to wake for shared resources. (Apple Support<\/a>)<\/p>\n\n\n\n Go to:<\/p>\n\n\n Change:<\/p>\n\n\n Also disable Power Nap if shown.<\/p>\n\n\n\nairportd ... systemWokenByWiFi<\/code> and repeated IOSkywalkLegacyEthernet ... en0<\/code>, where en0<\/code> was the Wi-Fi interface.<\/p>\n\n\n\n
\n\n\n\nCommon Symptoms<\/h2>\n\n\n\n
\n
AutoBoot<\/code>.<\/li>\n\n\n\npmset<\/code> logs show terms like:\n\n
MAGICWAKE<\/code><\/li>\n\n\n\nDarkWake<\/code><\/li>\n\n\n\nWake reason<\/code><\/li>\n\n\n\nairportd<\/code><\/li>\n\n\n\nen0<\/code><\/li>\n\n\n\nIOSkywalkNetworkBSDClient<\/code><\/li>\n\n\n\nsystemWokenByWiFi<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
\n\n\n\nWhy This Happens<\/h2>\n\n\n\n
\n
\n
User clicks Shut Down\n\u2193\nmacOS starts shutting down\n\u2193\nWi-Fi \/ USB-C \/ dock \/ network wake event arrives\n\u2193\nMac powers back on\n\u2193\nUser thinks shutdown became restart\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\nReal Case Diagnosis<\/h2>\n\n\n\n
log show --last 10<\/span>m --style compact --predicate 'eventMessage CONTAINS[c] \"MAGICWAKE\" OR eventMessage CONTAINS[c] \"Wake reason\" OR eventMessage CONTAINS[c] \"IOSkywalk\" OR eventMessage CONTAINS[c] \"Previous shutdown cause\"'<\/span> | tail -30<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\nairportd ... systemWokenByWiFi\n<\/code><\/span><\/pre>\n\n\nIOSkywalkLegacyEthernet as<\/span> no other controller was found for<\/span> en0\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\nnetworksetup -listallhardwareports<\/code> confirmed:<\/p>\n\n\nHardware Port: Wi-Fi\nDevice: en0\n<\/code><\/span><\/pre>\n\n\nWi-Fi en0 \u2192 airportd \u2192 IOSkywalk network stack \u2192 wake event\n<\/code><\/span><\/pre>\n\n\n\n
pmset -g assertions<\/code> output showed No kernel assertions<\/strong>, which means there was no persistent kernel-level blocker at that moment. That makes a normal app less likely and points more toward a temporary wake event during shutdown.<\/p>\n\n\n\n
\n\n\n\nStep-by-Step Troubleshooting Guide<\/h1>\n\n\n\n
Step 1: Confirm Whether It Is a True Restart or Wake Event<\/h2>\n\n\n\n
pmset -g log | grep -i \"Wake reason\"<\/span> | tail -20<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\nlog show --last 30<\/span>m | grep -i \"Previous shutdown cause\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\nWake reason<\/code>, DarkWake<\/code>, MAGICWAKE<\/code>, airportd<\/code>, or en0<\/code>, it is likely a wake event.<\/p>\n\n\n\n
\n\n\n\nStep 2: Check Power Assertions<\/h2>\n\n\n\n
pmset -g assertions\n<\/code><\/span><\/pre>\n\n\nPreventSystemSleep\nPreventUserIdleSystemSleep\nExternalMedia\nNetworkClientActive\nKernel Assertions\n<\/code><\/span><\/pre>\n\n\nOutput<\/th> Meaning<\/th><\/tr><\/thead> PreventSystemSleep 1<\/code><\/td>Something is actively preventing sleep\/shutdown behavior<\/td><\/tr> NetworkClientActive 1<\/code><\/td>Network service may be active<\/td><\/tr> ExternalMedia 1<\/code><\/td>External disk\/device may be involved<\/td><\/tr> MAGICWAKE<\/code><\/td>Network\/wake event happened<\/td><\/tr> No kernel assertions<\/code><\/td>No persistent kernel-level blocker now<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n No kernel assertions.\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\nStep 3: Find What
en0<\/code> Means<\/h2>\n\n\n\nen0<\/code>, do not guess. Find the exact interface:<\/p>\n\n\nnetworksetup -listallhardwareports\n<\/code><\/span><\/pre>\n\n\nHardware Port: Wi-Fi\nDevice: en0\n<\/code><\/span><\/pre>\n\n\nHardware Port: USB 10\/100\/1000 LAN\nDevice: en0\n<\/code><\/span><\/pre>\n\n\nDevice<\/th> Culprit<\/th><\/tr><\/thead> en0 = Wi-Fi<\/code><\/td>Wi-Fi network wake<\/td><\/tr> en0 = USB LAN<\/code><\/td>USB-C dock\/monitor Ethernet<\/td><\/tr> en0 = Thunderbolt Ethernet<\/code><\/td>Thunderbolt dock\/network adapter<\/td><\/tr> en0 = Bridge<\/code><\/td>Thunderbolt bridge\/network bridge<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n en0 = Wi-Fi\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\nStep 4: Disable Network Wake Features<\/h2>\n\n\n\n
sudo pmset -a tcpkeepalive 0\nsudo pmset -a womp 0\nsudo pmset -a powernap 0\n<\/code><\/span><\/pre>\n\n\npmset -g | egrep \"tcpkeepalive|womp|powernap\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\npowernap 0\ntcpkeepalive 0\nwomp 0\n<\/code><\/span><\/pre>\n\n\nSetting<\/th> Meaning<\/th><\/tr><\/thead> tcpkeepalive 0<\/code><\/td>Disables TCP keep-alive while sleeping<\/td><\/tr> womp 0<\/code><\/td>Disables Wake on Magic Packet \/ Wake for network access behavior<\/td><\/tr> powernap 0<\/code><\/td>Disables background updates during sleep<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\n\n\n\nStep 5: Disable Wake for Network Access in macOS UI<\/h2>\n\n\n\n
Apple menu \u2192 System Settings \u2192 Battery \u2192 Options\n<\/code><\/span><\/pre>\n\n\nWake for network access \u2192 Never\n<\/code><\/span><\/pre>\n\n\n