{"id":75892,"date":"2026-05-14T16:22:49","date_gmt":"2026-05-14T16:22:49","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=75892"},"modified":"2026-05-14T16:22:52","modified_gmt":"2026-05-14T16:22:52","slug":"macos-super-master-guide-troubleshooting-macbook-auto-reboot-after-shutdown","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/macos-super-master-guide-troubleshooting-macbook-auto-reboot-after-shutdown\/","title":{"rendered":"MacOS – Super Master Guide: Troubleshooting MacBook Auto-Reboot After Shutdown"},"content":{"rendered":"\n

This guide is for this exact problem:<\/p>\n\n\n

You run: sudo shutdown -h now\nMac shuts down\nThen Mac automatically powers on \/ reboots again\n<\/code><\/span><\/pre>\n\n\n
Your real case data shows:<\/p>\n\n\n
MacBook Pro Apple M4 Pro\nInternal display not visible\nExternal monitor used as<\/span> primary display\nmacOS detects internal display as<\/span> Online\nNo scheduled reboot\nNo new<\/span> May 15<\/span> panic file\nOld Jan 27<\/span> panic was GPU\/display firmware related: AGXk \/ GFX FW\nShutdown still reboots even after removing HDMI\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
So your current strongest conclusion is:<\/p>\n\n\n
Not VS Code\nNot normal pmset schedule\nNot normal app restart\nMost likely hardware \/ firmware \/ display-power path issue\n<\/code><\/span><\/pre>\n\n\n
Your old panic strongly points to Apple GPU\/display firmware: AGXk ... Failed to stop GFX FW for GPU recovery<\/code>.<\/p>\n\n\n\n
\n\n\n\n
1. Understand the Problem Clearly<\/h1>\n\n\n\n
There are different issues people confuse:<\/p>\n\n\n\n
Symptom<\/th>Meaning<\/th><\/tr><\/thead>
Mac wakes from sleep<\/td>Sleep\/wake setting, Bluetooth, network, Power Nap, monitor, USB<\/td><\/tr>
Mac restarts after crash<\/td>Kernel panic, watchdog, GPU, driver, hardware<\/td><\/tr>
Mac starts after shutdown<\/td>AutoBoot, power-on event, lid sensor, charger, power button, firmware, hardware<\/td><\/tr>
Mac shuts down but immediately boots<\/td>Firmware\/hardware power path, top case, lid sensor, board, display\/power issue<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Your problem is specifically:<\/p>\n\n\n
shutdown \u2192 power off \u2192 automatic power on again\n<\/code><\/span><\/pre>\n\n\n
That is different from normal sleep\/wake.<\/p>\n\n\n\n
\n\n\n\n
2. First Command: Confirm Reboot History<\/h1>\n\n\n\n
Run:<\/p>\n\n\n
last reboot | head -20\n<\/code><\/span><\/pre>\n\n\n
Example from your Mac:<\/p>\n\n\n
reboot<\/span> time<\/span> Fri<\/span> May<\/span> 15 00:39<\/span>\nreboot<\/span> time<\/span> Fri<\/span> May<\/span> 15 00:17<\/span>\nshutdown<\/span> time<\/span> Fri<\/span> May<\/span> 15 00:16<\/span>\nreboot<\/span> time<\/span> Thu<\/span> May<\/span> 14 23:58<\/span>\nshutdown<\/span> time<\/span> Thu<\/span> May<\/span> 14 23:58<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
Meaning:<\/p>\n\n\n
The Mac really rebooted multiple times.\nThis is not just display wake.\n<\/code><\/span><\/pre>\n\n\n
Your logs showed repeated reboot\/shutdown entries around May 14\u201315.<\/p>\n\n\n\n
\n\n\n\n
3. Check Scheduled Startup \/ Restart<\/h1>\n\n\n\n
Run:<\/p>\n\n\n
pmset -g sched\n<\/code><\/span><\/pre>\n\n\n
If output is empty, there is no scheduled startup\/reboot.<\/p>\n\n\n\n
In your case:<\/p>\n\n\n
pmset -g sched\n# empty<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Conclusion:<\/p>\n\n\n
Scheduled reboot is NOT the cause.\n<\/code><\/span><\/pre>\n\n\n
Apple confirms pmset<\/code> is the command-line utility used to schedule Mac startup, sleep, restart, or shutdown. (Apple Support<\/a>)<\/p>\n\n\n\n
\n\n\n\n
4. Check Power Settings<\/h1>\n\n\n\n
Run:<\/p>\n\n\n
pmset -g custom\n<\/code><\/span><\/pre>\n\n\n
Or shorter:<\/p>\n\n\n
pmset -g custom | egrep -i \"autorestart|womp|powernap|tcpkeepalive|sleep|disksleep|displaysleep\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Important settings:<\/p>\n\n\n\n
Setting<\/th>Meaning<\/th><\/tr><\/thead>
autorestart<\/code><\/td>Restart after power failure<\/td><\/tr>
womp<\/code><\/td>Wake on network access<\/td><\/tr>
powernap<\/code><\/td>Background wake tasks<\/td><\/tr>
tcpkeepalive<\/code><\/td>Network keepalive during sleep<\/td><\/tr>
sleep<\/code><\/td>System sleep timer<\/td><\/tr>
displaysleep<\/code><\/td>Display sleep timer<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Your output showed:<\/p>\n\n\n
womp 0<\/span>\npowernap 0<\/span>\ntcpkeepalive 0<\/span>\npmset -g sched empty\nautorestart not set<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Conclusion:<\/p>\n\n\n
Normal power schedule \/ network wake \/ Power Nap is not the reason.\n<\/code><\/span><\/pre>\n\n\n
Your latest log confirms no scheduled reboot and wake\/network-related options were already disabled.<\/p>\n\n\n\n
\n\n\n\n
5. Disable Auto Restart After Power Failure<\/h1>\n\n\n\n
Run:<\/p>\n\n\n
sudo pmset -a autorestart 0\n<\/code><\/span><\/pre>\n\n\n
Check:<\/p>\n\n\n
pmset -g custom | grep -i autorestart || echo<\/span> \"autorestart not set\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
If you get:<\/p>\n\n\n
autorestart not set<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
or no active autorestart<\/code>, then this is not the cause.<\/p>\n\n\n\n
Your result:<\/p>\n\n\n
autorestart not set<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Conclusion:<\/p>\n\n\n
pmset autorestart is not causing the reboot.\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\n
6. Apple Silicon: Disable Auto Startup on Lid Open \/ Power Connect<\/h1>\n\n\n\n
For newer Mac laptops, Apple documents BootPreference<\/code>, not just the older AutoBoot<\/code>. Use this on Apple silicon MacBook models.<\/p>\n\n\n\n
To prevent startup when opening lid or connecting to power:<\/p>\n\n\n
sudo nvram BootPreference=%00\n<\/code><\/span><\/pre>\n\n\n
Check:<\/p>\n\n\n
nvram -p | grep -i BootPreference\n<\/code><\/span><\/pre>\n\n\n
Expected:<\/p>\n\n\n
BootPreference\t%00\n<\/code><\/span><\/pre>\n\n\n
Undo later:<\/p>\n\n\n
sudo nvram -d BootPreference\n<\/code><\/span><\/pre>\n\n\n
Apple says sudo nvram BootPreference=%00<\/code> prevents startup when opening the lid or connecting to power, and sudo nvram -d BootPreference<\/code> re-enables automatic startup. (Apple Support<\/a>)<\/p>\n\n\n\n
Older\/legacy command sometimes used:<\/p>\n\n\n
sudo nvram AutoBoot=%00\n<\/code><\/span><\/pre>\n\n\n
Check:<\/p>\n\n\n
nvram -p | grep -i AutoBoot\n<\/code><\/span><\/pre>\n\n\n
But for modern Apple silicon MacBooks, prefer:<\/p>\n\n\n
sudo nvram BootPreference=%00\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\n
7. Best Shutdown Test Command<\/h1>\n\n\n\n
Use this:<\/p>\n\n\n
sudo shutdown -h now\n<\/code><\/span><\/pre>\n\n\n
Meaning:<\/p>\n\n\n
-h = halt \/ power off\nnow = immediately\n<\/code><\/span><\/pre>\n\n\n
If Mac still powers on again after this, it is not a normal user restart.<\/p>\n\n\n\n
\n\n\n\n
8. Correct Test Order<\/h1>\n\n\n\n
Do not remove HDMI after shutdown command. Test cleanly.<\/p>\n\n\n\n
Test A: With all devices connected<\/h2>\n\n\n
sudo shutdown -h now\n<\/code><\/span><\/pre>\n\n\n
If it reboots, continue.<\/p>\n\n\n\n
Test B: Remove external monitor \/ HDMI \/ USB-C first<\/h2>\n\n\n\n
Disconnect:<\/p>\n\n\n
HDMI\nUSB-C dock\nUSB hub\nexternal keyboard\nexternal mouse\nexternal SSD\ncharger, if battery has enough charge\n<\/code><\/span><\/pre>\n\n\n
Then run:<\/p>\n\n\n
sudo shutdown -h now\n<\/code><\/span><\/pre>\n\n\n
If it still reboots, external monitor alone is not the only cause.<\/p>\n\n\n\n
In your case, you already tested this and it still rebooted.<\/p>\n\n\n\n
Conclusion:<\/p>\n\n\n
External monitor alone is not the full cause.\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\n
9. Check Whether macOS Logged a Panic<\/h1>\n\n\n\n
Run:<\/p>\n\n\n
sudo find \/Library\/Logs\/DiagnosticReports \/var<\/span>\/db\/PanicReporter -type f -iname \"*panic*\"<\/span> -exec ls -lah {} \\; | tail -20<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Then check for today\u2019s panic:<\/p>\n\n\n
sudo find \/Library\/Logs\/DiagnosticReports \/var<\/span>\/db\/PanicReporter -type f \\( -iname \"*panic*\"<\/span> -o -iname \"*shutdown*\"<\/span> -o -iname \"*reset*\"<\/span> \\) -newermt \"2026-05-15 00:00\"<\/span> -exec ls -lah {} \\;\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Your result:<\/p>\n\n\n
Only<\/span> old<\/span> file<\/span>:\n.contents<\/span>.panic<\/span> Jan<\/span> 27\n\nNo<\/span> May<\/span> 15 panic<\/span> file<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
Conclusion:<\/p>\n\n\n
Today\u2019s reboot was not recorded as<\/span> a new<\/span> kernel panic.\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
But your old panic was important:<\/p>\n\n\n
AGXk ... Failed to stop GFX FW for GPU recovery\n<\/code><\/span><\/pre>\n\n\n
That points to:<\/p>\n\n\n
GPU \/ display firmware \/ graphics path\n<\/code><\/span><\/pre>\n\n\n
Your panic file showed Apple GPU-related kernel extensions such as IOGPUFamily<\/code> and AGXG16X<\/code>.<\/p>\n\n\n\n
\n\n\n\n
10. Read Panic File<\/h1>\n\n\n\n
Run:<\/p>\n\n\n
sudo sed -n '1,120p'<\/span> \/Library\/Logs\/DiagnosticReports\/.contents.panic\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
If unreadable:<\/p>\n\n\n
sudo strings \/Library\/Logs\/DiagnosticReports\/.contents.panic | head -120\n<\/code><\/span><\/pre>\n\n\n
Important panic keywords:<\/p>\n\n\n\n
Keyword<\/th>Meaning<\/th><\/tr><\/thead>
AGXk<\/code><\/td>Apple GPU driver\/firmware<\/td><\/tr>
GFX FW<\/code><\/td>Graphics firmware<\/td><\/tr>
IOGPUFamily<\/code><\/td>Apple GPU framework<\/td><\/tr>
AGXG16X<\/code><\/td>Apple GPU kext<\/td><\/tr>
watchdog<\/code><\/td>System\/hardware timed out<\/td><\/tr>
Sleep Wake Failure<\/code><\/td>Sleep\/wake firmware failure<\/td><\/tr>
SOCD<\/code><\/td>Apple silicon system controller crash<\/td><\/tr>
thermal<\/code><\/td>overheating \/ thermal shutdown<\/td><\/tr>
bridgeOS<\/code><\/td>older Intel T2-related issue<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Your old panic:<\/p>\n\n\n
AGXk ... Failed to stop GFX FW for GPU recovery\n<\/code><\/span><\/pre>\n\n\n
Conclusion:<\/p>\n\n\n
Old crash was GPU\/display firmware related.\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\n
11. Check Who Requested Shutdown or Restart<\/h1>\n\n\n\n
Run:<\/p>\n\n\n
log show --last 20<\/span>m --style compact --predicate 'eventMessage CONTAINS[c] \"power button\" OR eventMessage CONTAINS[c] \"lid\" OR eventMessage CONTAINS[c] \"clamshell\" OR eventMessage CONTAINS[c] \"wake\" OR eventMessage CONTAINS[c] \"shutdown\" OR eventMessage CONTAINS[c] \"restart\"'<\/span> | tail -80<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
What to look for:<\/p>\n\n\n\n
Log phrase<\/th>Meaning<\/th><\/tr><\/thead>
power button<\/code><\/td>Power button event<\/td><\/tr>
lid<\/code> \/ clamshell<\/code><\/td>Lid sensor event<\/td><\/tr>
wake<\/code><\/td>System woke from sleep\/off-like state<\/td><\/tr>
shutdown<\/code><\/td>Shutdown sequence<\/td><\/tr>
restart<\/code><\/td>Restart command<\/td><\/tr>
Previous shutdown cause<\/code><\/td>Shutdown reason<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Your log showed mostly:<\/p>\n\n\n
BT not yet ready\nShutdown sockets\nNo wake work scheduled\nbackground boot tasks\n<\/code><\/span><\/pre>\n\n\n
Conclusion:<\/p>\n\n\n
No clear app restart request\nNo power button evidence\nNo scheduled restart evidence\n<\/code><\/span><\/pre>\n\n\n
Your log mainly showed services shutting down\/restarting sockets and background tasks, not a user\/app-requested restart cause.<\/p>\n\n\n\n
\n\n\n\n
12. Check Previous Shutdown Cause<\/h1>\n\n\n\n
Run:<\/p>\n\n\n
log show --last 3<\/span>h --style compact --predicate 'eventMessage CONTAINS[c] \"Previous shutdown cause\"'<\/span> | tail -20<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
If empty:<\/p>\n\n\n
macOS did not expose a useful shutdown cause.\n<\/code><\/span><\/pre>\n\n\n
Your command returned no useful shutdown cause.<\/p>\n\n\n\n
\n\n\n\n
13. Check Exact Reboot Window<\/h1>\n\n\n\n
Replace the time with your real reboot time.<\/p>\n\n\n\n
Example:<\/p>\n\n\n
log show --start \"2026-05-15 00:35:00\"<\/span> --end \"2026-05-15 00:42:00\"<\/span> --style compact --predicate 'eventMessage CONTAINS[c] \"shutdown\" OR eventMessage CONTAINS[c] \"panic\" OR eventMessage CONTAINS[c] \"watchdog\" OR eventMessage CONTAINS[c] \"SOCD\" OR eventMessage CONTAINS[c] \"thermal\" OR eventMessage CONTAINS[c] \"restart\"'<\/span> | tail -100<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
If it shows no panic\/watchdog\/thermal:<\/p>\n\n\n
No recorded software crash reason found.\n<\/code><\/span><\/pre>\n\n\n
Your exact-window search did not show a new panic or useful shutdown reason for May 15.<\/p>\n\n\n\n
\n\n\n\n
14. Check Sleep\/Wake Log<\/h1>\n\n\n\n
Run:<\/p>\n\n\n
pmset -g log | egrep -i \"Wake reason|Sleep Wake Failure|DarkWake|Shutdown|Restart|panic\"<\/span> | tail -80<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Exact window:<\/p>\n\n\n
pmset -g log | awk '\/2026-05-15 00:35\/,\/2026-05-15 00:42\/'<\/span> | egrep -i \"sleep|wake|darkwake|panic|shutdown|restart|failure\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
If exact window gives nothing useful:<\/p>\n\n\n
It was probably not a normal sleep\/wake event.\n<\/code><\/span><\/pre>\n\n\n
Your exact sleep\/wake window produced no useful entries.<\/p>\n\n\n\n
\n\n\n\n
15. Check Display Status<\/h1>\n\n\n\n
Run:<\/p>\n\n\n
system_profiler SPDisplaysDataType | egrep -i \"Chipset|Display|Resolution|Main Display|Online|Connection|Display Type\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Your output:<\/p>\n\n\n
Chipset Model: Apple M4 Pro\nExternal display: 1920 x 1080, Main Display: Yes, Online: Yes\nBuilt-in Liquid Retina XDR Display\nResolution: 3456 x 2234 Retina\nOnline: Yes\nConnection Type: Internal\n<\/code><\/span><\/pre>\n\n\n
Meaning:<\/p>\n\n\n
macOS thinks internal display is online.\nBut physically you cannot see it.\n<\/code><\/span><\/pre>\n\n\n
This is very important.<\/p>\n\n\n\n
Conclusion:<\/p>\n\n\n
Internal display panel \/ cable \/ backlight \/ display path issue is very likely.\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\n
16. Check Lid Sensor<\/h1>\n\n\n\n
Run:<\/p>\n\n\n
ioreg -r -k AppleClamshellState -d 4 | grep AppleClamshellState\n<\/code><\/span><\/pre>\n\n\n
Expected:<\/p>\n\n\n
Open lid   = No\nClosed lid = Yes\n<\/code><\/span><\/pre>\n\n\n
To test live:<\/p>\n\n\n
while<\/span> true<\/span>; do<\/span> ioreg -r -k AppleClamshellState -d 4<\/span> | grep AppleClamshellState; sleep 2<\/span>; done\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Then slowly close\/open lid.<\/p>\n\n\n\n
Stop:<\/p>\n\n\n
Control + C\n<\/code><\/span><\/pre>\n\n\n
Meaning:<\/p>\n\n\n\n
Result<\/th>Meaning<\/th><\/tr><\/thead>
Changes No \u2192 Yes<\/code><\/td>Lid sensor likely works<\/td><\/tr>
Always No<\/code><\/td>Lid sensor\/top-case issue<\/td><\/tr>
Always Yes<\/code><\/td>Lid sensor thinks lid closed<\/td><\/tr>
Random changes<\/td>Lid sensor\/cable\/magnet issue<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Your current result:<\/p>\n\n\n
AppleClamshellState = No\n<\/code><\/span><\/pre>\n\n\n
That means lid is currently detected open. You still need close\/open test to confirm sensor changes.<\/p>\n\n\n\n
\n\n\n\n
17. Reset Power Settings<\/h1>\n\n\n\n
Run:<\/p>\n\n\n
sudo pmset restoredefaults\n<\/code><\/span><\/pre>\n\n\n
Then test:<\/p>\n\n\n
sudo shutdown -h now\n<\/code><\/span><\/pre>\n\n\n
This resets custom power settings.<\/p>\n\n\n\n
Use when:<\/p>\n\n\n
power settings are messy\nsleep\/disksleep warnings appear\nmany pmset changes were tested\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\n
18. Strong Test: Disable Sleep Temporarily<\/h1>\n\n\n\n
This is for testing only.<\/p>\n\n\n
sudo pmset -a sleep 0 displaysleep 0 disksleep 0 autorestart 0 womp 0 powernap 0 tcpkeepalive 0\n<\/code><\/span><\/pre>\n\n\n
Then:<\/p>\n\n\n
sudo shutdown -h now\n<\/code><\/span><\/pre>\n\n\n
If still reboots:<\/p>\n\n\n
Not normal sleep setting.\n<\/code><\/span><\/pre>\n\n\n
Restore later:<\/p>\n\n\n
sudo pmset restoredefaults\n<\/code><\/span><\/pre>\n\n\n
or:<\/p>\n\n\n
sudo pmset -a sleep 30 displaysleep 10 disksleep 10\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\n
19. Safe Mode Test<\/h1>\n\n\n\n
For Apple silicon Mac:<\/p>\n\n\n\n
    \n
  1. Shut down.<\/li>\n\n\n\n
  2. Press and hold power button until startup options appear.<\/li>\n\n\n\n
  3. Select your disk.<\/li>\n\n\n\n
  4. Hold Shift.<\/li>\n\n\n\n
  5. Click Continue in Safe Mode<\/strong>.<\/li>\n<\/ol>\n\n\n\n
    Apple says Apple silicon Safe Mode is started from startup options by holding Shift while choosing the startup volume. (Apple Support<\/a>)<\/p>\n\n\n\n
    Then run:<\/p>\n\n\n
    sudo shutdown -h now\n<\/code><\/span><\/pre>\n\n\n
    Result:<\/p>\n\n\n\n
    Safe Mode result<\/th>Meaning<\/th><\/tr><\/thead>
    Shutdown works<\/td>third-party software\/driver\/login item may be involved<\/td><\/tr>
    Still reboots<\/td>hardware\/firmware\/power path likely<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    \n\n\n\n
    20. Apple Diagnostics<\/h1>\n\n\n\n
    For Apple silicon Mac:<\/p>\n\n\n\n
      \n
    1. Shut down.<\/li>\n\n\n\n
    2. Press and hold power button until startup options appear.<\/li>\n\n\n\n
    3. Press:<\/li>\n<\/ol>\n\n\n
      Command + D\n<\/code><\/span><\/pre>\n\n\n
      Apple\u2019s startup options screen supports opening Apple Diagnostics using Command-D. (Apple Support<\/a>)<\/p>\n\n\n\n
      If you get an error code, save it.<\/p>\n\n\n\n
      Common useful codes may point to:<\/p>\n\n\n
      display\nbattery\nlogic board\nmemory\nstorage\npower\nsensor\n<\/code><\/span><\/pre>\n\n\n
      If Diagnostics says no issue but problem continues, that does not fully clear hardware. Intermittent display\/power issues may not always appear.<\/p>\n\n\n\n
      \n\n\n\n
      21. Recovery Mode Test<\/h1>\n\n\n\n
      For Apple silicon:<\/p>\n\n\n\n
        \n
      1. Shut down.<\/li>\n\n\n\n
      2. Hold power button until startup options.<\/li>\n\n\n\n
      3. Choose Options<\/strong>.<\/li>\n\n\n\n
      4. Continue into Recovery.<\/li>\n<\/ol>\n\n\n\n
        Apple documents Recovery on Apple silicon as holding the power button until volumes and Options appear. (Apple Support<\/a>)<\/p>\n\n\n\n
        From Recovery, use Terminal:<\/p>\n\n\n
        shutdown -h now\n<\/code><\/span><\/pre>\n\n\n
        Result:<\/p>\n\n\n\n
        Recovery shutdown result<\/th>Meaning<\/th><\/tr><\/thead>
        Stays off<\/td>installed macOS\/userspace may be involved<\/td><\/tr>
        Reboots again<\/td>firmware\/hardware more likely<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        \n\n\n\n
        22. Reinstall macOS Test<\/h1>\n\n\n\n
        Do this only after backup.<\/p>\n\n\n\n
        Apple recommends software updates, Safe Mode, reinstalling macOS, and checking hardware when a Mac restarts because of a problem. (Apple Support<\/a>)<\/p>\n\n\n\n
        Use this when:<\/p>\n\n\n
        No clear panic\nNo schedule\nNo third-party cause\nSafe Mode changes behavior\nSystem files may be broken\n<\/code><\/span><\/pre>\n\n\n
        But in your case, because internal display is already physically not visible, reinstall may not solve the root issue.<\/p>\n\n\n\n
        \n\n\n\n
        23. Hardware Scenario Matrix<\/h1>\n\n\n\n
        Scenario A: Scheduled reboot<\/h2>\n\n\n\n
        Commands:<\/p>\n\n\n
        pmset -g sched\n<\/code><\/span><\/pre>\n\n\n
        If output has schedule:<\/p>\n\n\n
        sudo pmset repeat cancel\n<\/code><\/span><\/pre>\n\n\n
        Conclusion:<\/p>\n\n\n
        Scheduled startup\/restart caused issue.\n<\/code><\/span><\/pre>\n\n\n
        Your case:<\/p>\n\n\n
        No schedule.\n<\/code><\/span><\/pre>\n\n\n
        \n\n\n\n
        Scenario B: Wake on network \/ Power Nap<\/h2>\n\n\n\n
        Commands:<\/p>\n\n\n
        pmset -g custom | egrep -i \"womp|powernap|tcpkeepalive\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Fix:<\/p>\n\n\n
        sudo pmset -a womp 0 powernap 0 tcpkeepalive 0\n<\/code><\/span><\/pre>\n\n\n
        Your case:<\/p>\n\n\n
        Already disabled.\n<\/code><\/span><\/pre>\n\n\n
        \n\n\n\n
        Scenario C: Auto restart after power failure<\/h2>\n\n\n\n
        Command:<\/p>\n\n\n
        pmset -g custom | grep -i autorestart || echo<\/span> \"autorestart not set\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Fix:<\/p>\n\n\n
        sudo pmset -a autorestart 0\n<\/code><\/span><\/pre>\n\n\n
        Your case:<\/p>\n\n\n
        autorestart not set<\/span>.\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        \n\n\n\n
        Scenario D: Auto startup when lid opens \/ charger connects<\/h2>\n\n\n\n
        Modern Apple silicon fix:<\/p>\n\n\n
        sudo nvram BootPreference=%00\n<\/code><\/span><\/pre>\n\n\n
        Check:<\/p>\n\n\n
        nvram -p | grep -i BootPreference\n<\/code><\/span><\/pre>\n\n\n
        Undo:<\/p>\n\n\n
        sudo nvram -d BootPreference\n<\/code><\/span><\/pre>\n\n\n
        Apple documents BootPreference=%00<\/code> for preventing startup when lid opens or power connects. (Apple Support<\/a>)<\/p>\n\n\n\n
        \n\n\n\n
        Scenario E: App requests restart<\/h2>\n\n\n\n
        Command:<\/p>\n\n\n
        log show --last 30<\/span>m --style compact --predicate 'eventMessage CONTAINS[c] \"restart\" OR eventMessage CONTAINS[c] \"reboot\" OR eventMessage CONTAINS[c] \"logout\" OR eventMessage CONTAINS[c] \"shutdown\"'<\/span> | tail -100<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        If you see app\/updater:<\/p>\n\n\n
        Disable that app auto update\nQuit app fully\nRemove login item\nReinstall app\n<\/code><\/span><\/pre>\n\n\n
        Your earlier VS Code ShipIt<\/code> updater was noisy, but later shutdown still rebooted after VS Code isolation, so it is not final root cause.<\/p>\n\n\n\n
        \n\n\n\n
        Scenario F: Kernel panic<\/h2>\n\n\n\n
        Commands:<\/p>\n\n\n
        sudo find \/Library\/Logs\/DiagnosticReports \/var<\/span>\/db\/PanicReporter -type f -iname \"*panic*\"<\/span> -exec ls -lah {} \\; | tail -20<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Read latest:<\/p>\n\n\n
        sudo strings \/path\/to\/latest.panic | head -120\n<\/code><\/span><\/pre>\n\n\n
        If panic contains GPU:<\/p>\n\n\n
        AGXk\nIOGPUFamily\nAGXG16X\nGFX FW\n<\/code><\/span><\/pre>\n\n\n
        Suspect:<\/p>\n\n\n
        GPU\/display firmware\ninternal display path\nexternal monitor\/dock\nmacOS graphics bug\nlogic board\/display hardware\n<\/code><\/span><\/pre>\n\n\n
        Your old panic was GPU\/display related.<\/p>\n\n\n\n
        \n\n\n\n
        Scenario G: Sleep Wake Failure<\/h2>\n\n\n\n
        Command:<\/p>\n\n\n
        sudo find \/Library\/Logs\/DiagnosticReports \/var<\/span>\/db\/PanicReporter -type f -iname \"*Sleep Wake Failure*\"<\/span> -exec ls -lah {} \\; | tail -20<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Fix attempts:<\/p>\n\n\n
        sudo pmset restoredefaults\nsudo pmset -a powernap 0 tcpkeepalive 0 womp 0\n<\/code><\/span><\/pre>\n\n\n
        Also remove:<\/p>\n\n\n
        USB-C dock\nexternal display\nexternal SSD\nBluetooth devices\n<\/code><\/span><\/pre>\n\n\n
        \n\n\n\n
        Scenario H: Display detected but black<\/h2>\n\n\n\n
        Command:<\/p>\n\n\n
        system_profiler SPDisplaysDataType | egrep -i \"Display Type|Main Display|Online|Connection|Resolution\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        If internal display says:<\/p>\n\n\n
        Online: Yes\nConnection Type: Internal\n<\/code><\/span><\/pre>\n\n\n
        but screen is black:<\/p>\n\n\n
        Display assembly \/ display cable \/ backlight \/ display power path issue\n<\/code><\/span><\/pre>\n\n\n
        Your case exactly matches this.<\/p>\n\n\n\n
        \n\n\n\n
        Scenario I: Lid sensor issue<\/h2>\n\n\n\n
        Command:<\/p>\n\n\n
        while<\/span> true<\/span>; do<\/span> ioreg -r -k AppleClamshellState -d 4<\/span> | grep AppleClamshellState; sleep 2<\/span>; done\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Expected:<\/p>\n\n\n
        Open lid   = No\nClosed lid = Yes\n<\/code><\/span><\/pre>\n\n\n
        If it does not change:<\/p>\n\n\n
        lid sensor \/ magnet \/ top case<\/span> \/ display assembly issue\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        \n\n\n\n
        Scenario J: Power button \/ top case issue<\/h2>\n\n\n\n
        Symptoms:<\/p>\n\n\n
        Mac powers on immediately after shutdown\nNo schedule\nNo panic\nNo AutoBoot reason\nNo app restart\n<\/code><\/span><\/pre>\n\n\n
        Possible cause:<\/p>\n\n\n
        Power button signal stuck\/intermittent\nKeyboard\/top case<\/span> issue\nTouch ID\/power button hardware issue\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Test:<\/p>\n\n\n
        log show --last 20<\/span>m --style compact --predicate 'eventMessage CONTAINS[c] \"power button\"'<\/span> | tail -50<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        If logs show power button events without pressing it:<\/p>\n\n\n
        top case<\/span> \/ power button issue likely\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        If no logs show it, hardware can still be faulty at low firmware level.<\/p>\n\n\n\n
        \n\n\n\n
        Scenario K: Logic board power-management issue<\/h2>\n\n\n\n
        Symptoms:<\/p>\n\n\n
        Mac reboots after real halt\nNo panic\nNo schedule\nNo app restart\nNo peripheral cause\nAuto-start disabled\nInternal display already faulty\n<\/code><\/span><\/pre>\n\n\n
        Likely service items:<\/p>\n\n\n
        logic board\npower management circuit\ndisplay power rail\nUSB-C\/power controller\nsensor path\n<\/code><\/span><\/pre>\n\n\n
        This is not command-fixable.<\/p>\n\n\n\n
        \n\n\n\n
        24. Your Case: Final Diagnosis Based on Evidence<\/h1>\n\n\n\n
        Evidence 1: No scheduled reboot<\/h2>\n\n\n
        pmset -g sched empty<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Conclusion:<\/p>\n\n\n
        Not scheduled startup\/restart.\n<\/code><\/span><\/pre>\n\n\n
        Evidence 2: Wake\/network options off<\/h2>\n\n\n
        womp 0\npowernap 0\ntcpkeepalive 0\n<\/code><\/span><\/pre>\n\n\n
        Conclusion:<\/p>\n\n\n
        Not normal network wake \/ Power Nap.\n<\/code><\/span><\/pre>\n\n\n
        Evidence 3: No new May 15 panic<\/h2>\n\n\n
        Only<\/span> old<\/span> .contents<\/span>.panic<\/span> from<\/span> Jan<\/span> 27\nNo<\/span> May<\/span> 15 panic<\/span> found<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        Conclusion:<\/p>\n\n\n
        Current shutdown\u2192reboot is not recorded as<\/span> a new<\/span> kernel panic.\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Evidence 4: Old panic is GPU\/display firmware<\/h2>\n\n\n
        AGXk ... Failed to stop GFX FW for GPU recovery\n<\/code><\/span><\/pre>\n\n\n
        Conclusion:<\/p>\n\n\n
        There is history of GPU\/display firmware crash.\n<\/code><\/span><\/pre>\n\n\n
        Evidence 5: Internal display is detected online but not visible<\/h2>\n\n\n
        Built-in Liquid Retina XDR Display\nOnline: Yes\nConnection Type: Internal\n<\/code><\/span><\/pre>\n\n\n
        Conclusion:<\/p>\n\n\n
        Internal display panel\/cable\/backlight\/display path issue is very likely.\n<\/code><\/span><\/pre>\n\n\n
        Evidence 6: Shutdown still reboots without HDMI<\/h2>\n\n\n\n
        Conclusion:<\/p>\n\n\n
        External monitor alone is not the full cause.\n<\/code><\/span><\/pre>\n\n\n
        Final likely root cause<\/h2>\n\n\n
        Hardware \/ firmware power-on issue connected to internal display path, lid\/top-case<\/span> sensor path, or logic board power management.\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Most likely order:<\/p>\n\n\n
        1.<\/span> Internal display assembly \/ display cable \/ backlight\n2.<\/span> Lid sensor \/ display-lid sensor path\n3.<\/span> Power button \/ top case<\/span>\n4.<\/span> Logic board power-management circuit\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        \n\n\n\n
        25. Direct Fix Commands to Try Before Service<\/h1>\n\n\n\n
        Run this full software-side reset:<\/p>\n\n\n
        sudo pmset restoredefaults\nsudo pmset -a autorestart 0 womp 0 powernap 0 tcpkeepalive 0\nsudo nvram BootPreference=%00\n<\/code><\/span><\/pre>\n\n\n
        Check:<\/p>\n\n\n
        pmset -g sched\npmset -g custom | egrep -i \"autorestart|womp|powernap|tcpkeepalive|sleep\"<\/span>\nnvram -p | grep -i BootPreference\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Then shut down:<\/p>\n\n\n
        sudo shutdown -h now\n<\/code><\/span><\/pre>\n\n\n
        If still reboots:<\/p>\n\n\n
        Stop software debugging.\nMove to hardware\/service.\n<\/code><\/span><\/pre>\n\n\n
        \n\n\n\n
        26. What to Tell Apple Service<\/h1>\n\n\n\n
        Use this exact message:<\/p>\n\n\n
        My MacBook Pro shuts down but automatically powers on\/reboots again after shutdown.\n\nI tested:\n- sudo shutdown -h now\n- pmset schedule is empty<\/span>\n- autorestart is not set\n- womp, powernap, tcpkeepalive are disabled\n- no new<\/span> panic file was generated for<\/span> the latest reboot\n- external monitor\/HDMI was removed before shutdown, but issue still happens\n\nImportant display symptom:\n- Built-in display is physically not visible\/working\n- macOS still detects the built-in Liquid Retina XDR display as<\/span> Online and<\/span> Internal\n- External monitor is used as<\/span> the main display\n\nOld panic report shows:\nAGXk ... Failed to stop GFX FW for<\/span> GPU recovery\n\nPlease check:\n- internal display panel\/cable\/backlight path\n- lid sensor \/ clamshell sensor\n- power button\/top case<\/span>\n- logic board power-management\/display power path\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Before service, Apple recommends backing up the Mac because service may require erasing or replacing the startup disk. (Apple Support<\/a>)<\/p>\n\n\n\n
        \n\n\n\n
        27. One-Page Quick Command Sheet<\/h1>\n\n\n\n
        Reboot history<\/h2>\n\n\n
        last reboot | head -20\n<\/code><\/span><\/pre>\n\n\n
        Scheduled startup\/reboot<\/h2>\n\n\n
        pmset -g sched\n<\/code><\/span><\/pre>\n\n\n
        Power settings<\/h2>\n\n\n
        pmset -g custom | egrep -i \"autorestart|womp|powernap|tcpkeepalive|sleep|disksleep|displaysleep\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Disable power wake options<\/h2>\n\n\n
        sudo pmset -a autorestart 0 womp 0 powernap 0 tcpkeepalive 0\n<\/code><\/span><\/pre>\n\n\n
        Disable Apple silicon auto startup on lid\/power<\/h2>\n\n\n
        sudo nvram BootPreference=%00\n<\/code><\/span><\/pre>\n\n\n
        Undo BootPreference<\/h2>\n\n\n
        sudo nvram -d BootPreference\n<\/code><\/span><\/pre>\n\n\n
        Real shutdown test<\/h2>\n\n\n
        sudo shutdown -h now\n<\/code><\/span><\/pre>\n\n\n
        Find panic files<\/h2>\n\n\n
        sudo find \/Library\/Logs\/DiagnosticReports \/var<\/span>\/db\/PanicReporter -type f -iname \"*panic*\"<\/span> -exec ls -lah {} \\; | tail -20<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Find today\u2019s panic\/shutdown\/reset files<\/h2>\n\n\n
        sudo find \/Library\/Logs\/DiagnosticReports \/var<\/span>\/db\/PanicReporter -type f \\( -iname \"*panic*\"<\/span> -o -iname \"*shutdown*\"<\/span> -o -iname \"*reset*\"<\/span> \\) -newermt \"2026-05-15 00:00\"<\/span> -exec ls -lah {} \\;\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Read panic<\/h2>\n\n\n
        sudo strings \/Library\/Logs\/DiagnosticReports\/.contents.panic | head -120\n<\/code><\/span><\/pre>\n\n\n
        Display detection<\/h2>\n\n\n
        system_profiler SPDisplaysDataType | egrep -i \"Display Type|Main Display|Online|Connection|Resolution\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Lid sensor<\/h2>\n\n\n
        ioreg -r -k AppleClamshellState -d 4 | grep AppleClamshellState\n<\/code><\/span><\/pre>\n\n\n
        Live lid sensor test<\/h2>\n\n\n
        while<\/span> true<\/span>; do<\/span> ioreg -r -k AppleClamshellState -d 4<\/span> | grep AppleClamshellState; sleep 2<\/span>; done\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Logs for shutdown\/restart\/power button<\/h2>\n\n\n
        log show --last 20<\/span>m --style compact --predicate 'eventMessage CONTAINS[c] \"power button\" OR eventMessage CONTAINS[c] \"lid\" OR eventMessage CONTAINS[c] \"clamshell\" OR eventMessage CONTAINS[c] \"wake\" OR eventMessage CONTAINS[c] \"shutdown\" OR eventMessage CONTAINS[c] \"restart\"'<\/span> | tail -80<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Reset power settings<\/h2>\n\n\n
        sudo pmset restoredefaults\n<\/code><\/span><\/pre>\n\n\n
        \n\n\n\n
        28. Final Practical Conclusion<\/h1>\n\n\n\n
        For your Mac, based on all collected evidence:<\/p>\n\n\n
        The reboot-after-shutdown issue is very unlikely to be caused by VS Code, app updater, Power Nap, scheduled reboot, Wake-on-LAN, or a normal macOS sleep setting.\n<\/code><\/span><\/pre>\n\n\n
        The strongest diagnosis is:<\/p>\n\n\n
        Hardware\/firmware power issue related to the internal display path, lid\/top-case<\/span> sensor path, or logic board power management.\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        The biggest red flag is:<\/p>\n\n\n
        Internal display is detected Online by macOS, but physically it does not work.\n<\/code><\/span><\/pre>\n\n\n
        Combined with your old GPU panic:<\/p>\n\n\n
        AGXk ... Failed to stop GFX FW for GPU recovery\n<\/code><\/span><\/pre>\n\n\n
        the repair priority should be:<\/p>\n\n\n
        1.<\/span> Internal display assembly \/ display cable \/ backlight path\n2.<\/span> Lid sensor \/ clamshell sensor\n3.<\/span> Power button \/ top case<\/span>\n4.<\/span> Logic board power-management\/display power circuit\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Commands can confirm and reduce false causes, but if sudo shutdown -h now<\/code> still reboots after BootPreference=%00<\/code>, autorestart 0<\/code>, no schedule, no peripherals, and no new panic, then this is no longer a normal software fix.<\/p>\n","protected":false},"excerpt":{"rendered":"
        This guide is for this exact problem: Your real case data shows: So your current strongest conclusion is: Your old panic strongly points to Apple GPU\/display firmware:… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[11138],"tags":[],"class_list":["post-75892","post","type-post","status-publish","format-standard","hentry","category-best-tools"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75892","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=75892"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75892\/revisions"}],"predecessor-version":[{"id":75893,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75892\/revisions\/75893"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=75892"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=75892"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=75892"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}