I'm desperately trying to figure out how to get my 2019 iMac running macOS Ventura to stay asleep when I put it to sleep. (Each time it wakes up on its own, various lights blink on and hard drives spin up, causing enough light and sound to disturb my sleep.) I've turned off Power Nap, Wi-Fi, Bluetooth, Wake for network access, Wake for Notifications, Keep network connections alive, Stay awake for networking, Stay awake if remote users are active, and a few other settings recommended by the app Sleep Aid. However, the computer still periodically wakes up, and looking at the output in pmset -g log, I see the following:

2025-05-01 01:42:52 -0400 Assertions          	PID 119(powerd) Created InternalPreventSleep "PM configd - Wait for Device enumeration" 00:00:00  id:0x0xd00008623 [System: DeclUser SRPrevSleep kCPU kDisp]
2025-05-01 01:42:52 -0400 DarkWake            	DarkWake from Normal Sleep [CDN] : due to XHC2 XHC1/ Using AC (Charge:0%) 45 secs
2025-05-01 01:42:52 -0400 WakeDetails         	DriverReason:XHC1 - DriverDetails:
2025-05-01 01:42:52 -0400 HibernateStats      	hibmode=3 standbydelaylow=86400 standbydelayhigh=86400                     	          42
2025-05-01 01:42:52 -0400 WakeTime            	WakeTime: 12.265 sec

2025-05-01 07:08:24 -0400 Assertions          	PID 119(powerd) Created InternalPreventSleep "com.apple.powermanagement.wakeschedule" 00:00:00  id:0x0xd00009024 [System: DeclUser SRPrevSleep kCPU kDisp]
2025-05-01 07:08:29 -0400 Assertions          	PID 119(powerd) TimedOut InternalPreventSleep "com.apple.powermanagement.wakeschedule" 00:00:05  id:0x0xd00009024 [System: DeclUser BGTask SRPrevSleep kCPU kDisp]
2025-05-01 07:08:34 -0400 DarkWake            	DarkWake from Normal Sleep [CDN] : due to RTC/Maintenance Using AC (Charge:0%) 0 secs
2025-05-01 07:08:34 -0400 WakeDetails         	DriverReason:XHC1 - DriverDetails:
2025-05-01 07:08:34 -0400 HibernateStats      	hibmode=3 standbydelaylow=86400 standbydelayhigh=86400                     	          44
2025-05-01 07:08:34 -0400 WakeTime            	WakeTime: 11.226 sec

2025-05-01 09:00:11 -0400 Assertions          	PID 119(powerd) TimedOut InternalPreventSleep "com.apple.powermanagement.acwakelinger" 01:51:36  id:0x0xd00009037 [System: DeclUser BGTask SRPrevSleep kCPU kDisp]
2025-05-01 09:00:11 -0400 Assertions          	Summary- [System: DeclUser BGTask kDisp] Using AC
2025-05-01 09:00:11 -0400 DarkWake            	DarkWake from Normal Sleep [CDN] : due to RTC/Maintenance Using AC (Charge:0%) 0 secs
2025-05-01 09:00:11 -0400 WakeDetails         	DriverReason:XHC1 - DriverDetails:
2025-05-01 09:00:11 -0400 HibernateStats      	hibmode=3 standbydelaylow=86400 standbydelayhigh=86400                     	          45
2025-05-01 09:00:11 -0400 WakeTime            	WakeTime: 11.221 sec

As near as I can tell, the only real clue from these log entries is XHC1, which points to a USB device connected to that USB controller. This include a variety of different devices, including the built-in FaceTime camera, a keyboard and mouse, and external hard drives. Is there any way to tell precisely which device it is that triggered the wake up? Update: I found out that if I disconnect every device from my iMac, so that it has nothing connected to it other than its power cord, then it doesn't go to sleep at all. Apparently a mac refuses to sleep without an input device. If I disconnect everything except my keyboard and mouse, I still get the wakeups. So this may be a problem with my keyboard and mouse, and I'm not sure if there's anything I can do about it.

When I check my power management assertions (MacBook Pro running macOS Sierra), I see the following line: $ sudo pmset -g assertions ... Idle sleep preventers: IODisplayWrangler What is IODisplayWrangler and what does it mean that it is listed as an "idle sleep preventer"?

I ran the following sequence of commands as root: Check output of pmset -g:

pmset -g
System-wide power settings:
Currently in use:
 standby              1
 Sleep On Power Button 1
 hibernatefile        /var/vm/sleepimage
 powernap             1
 networkoversleep     0
 disksleep            10
 sleep                0 (sleep prevented by Python, powerd)
 hibernatemode        3
 ttyskeepawake        1
 displaysleep         0
 tcpkeepalive         1
 powermode            2
 womp                 1

Disable sleep using pmset disablesleep 1 and then run pmset -g again:

pmset disablesleep 1
pmset -g
System-wide power settings:
 SleepDisabled          1
Currently in use:
 standby              1
 Sleep On Power Button 1
 hibernatefile        /var/vm/sleepimage
 powernap             1
 networkoversleep     0
 disksleep            10
 sleep                1 (sleep prevented by powerd)
 hibernatemode        3
 ttyskeepawake        1
 displaysleep         3
 tcpkeepalive         1
 powermode            2
 womp                 0

Observe the extra line SleepDisabled 1 that appears in the output above. I then tried to remove the line by running pmset disablesleep 0:

pmset disablesleep 0
System-wide power settings:
 SleepDisabled          0
Currently in use:
 standby              1
 Sleep On Power Button 1
 hibernatefile        /var/vm/sleepimage
 powernap             1
 networkoversleep     0
 disksleep            10
 sleep                1 (sleep prevented by powerd)
 hibernatemode        3
 ttyskeepawake        1
 displaysleep         3
 tcpkeepalive         1
 powermode            2
 womp                 0

Now I have a line that says SleepDisabled 0. **What command can I run to get back to a state where the line does not appear at all in the output of pmset -g?** Also, is SleepDisabled 0 equivalent in the state where the line does not appear at all? --- **Update**: pmset restoredefaults does something but it does not remove the scars left by using disablesleep.

$ pmset -g
System-wide power settings:
 SleepDisabled          0
Currently in use:
 standby              1
 Sleep On Power Button 1
 hibernatefile        /var/vm/sleepimage
 powernap             1
 networkoversleep     0
 disksleep            10
 sleep                0 (sleep prevented by powerd)
 hibernatemode        3
 ttyskeepawake        1
 displaysleep         0
 tcpkeepalive         1
 powermode            2
 womp                 1

$ pmset restoredefaults
Restored Default settings.

$ pmset -g
System-wide power settings:
 SleepDisabled          0
Currently in use:
 standby              1
 Sleep On Power Button 1
 hibernatefile        /var/vm/sleepimage
 powernap             1
 networkoversleep     0
 disksleep            10
 sleep                1 (sleep prevented by powerd)
 hibernatemode        3
 ttyskeepawake        1
 displaysleep         10
 tcpkeepalive         1
 powermode            0
 womp                 1

I want my Mac to be remotely accessible even after rebooting. This is prevented by FileVault and one needs to physically login first after the reboot. One can solve this by the command line fdesetup authrestart. However, this is only useful for an immediate restart. I want instead the restart pmset scheduled. For instance, I set pmset relative poweron 25000 and then remotely shut down the machine. 25000s later, it restarts but runs back to the FileVault problem. Any workaround besides turning FileVault off?

After some time searching, I found this answer: [How do I remove 'pmset' auto-wakeup command for my Mac?](https://apple.stackexchange.com/a/457025/432220) But the solution is not working for me. I originally had my laptop scheduled to restart at midnight, every day. That schedule is now missing but has been replaced by two wake events:

user@COMPUTER / % pmset -g sched          
Scheduled power events:
   wake at 12/28/2023 11:51:49 by 'com.apple.alarm.user-visible-com.apple.calaccessd.travelEngine.periodicRefreshTimer'
   wake at 12/29/2023 04:04:04 by 'com.apple.alarm.user-visible-com.apple.acmd.alarm'
user@COMPUTER / %

No amount of running

repeat cancel

removes them. Does anyone have any insight on this? UPDATE: Well, I just got back to this and the events are no longer even showing up. I've saved the question so if they come back up, I'll walk through the potential solutions provided. UPDATE 1: The problem suddenly resolved itself. I am not sure what I did differently that might have caused it to resolved. But It's over now. Thank you for all the help

I was messing around with [pmset](https://www.dssw.co.uk/reference/pmset/) and I added this setting: sudo pmset -a disablesleep 1 in my terminal. I have got [Amphetamine](https://iffy.freshdesk.com/support/home) for my Mac, so I want to take off this pmset setting. How could I?

After updating to macOS Sonoma my MacBook Pro 16" 2019 doesn't enter standby mode even at night after more than 10 hours of being closed. pmset -g assertions shows the following:

2023-10-01 09:28:52 +0300 
Assertion status system-wide:
   BackgroundTask                 0
   ApplePushServiceTask           0
   UserIsActive                   1
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   ExternalMedia                  0
   PreventUserIdleSystemSleep     0
   NetworkClientActive            0
Listed by owning process:
   pid 171(WindowServer): [0x000006ec000988b8] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle serviceID:100001e59 service:AppleHIDKeyboardEventDriverV2 product:Apple Internal Keyboard / Trackpad eventType:3"  
	Timeout will fire in 120 secs Action=TimeoutActionRelease
No kernel assertions.
Idle sleep preventers: IODisplayWrangler

Google says, that there is nothing abnormal. I've set the following settings in pmset long time ago, and before update everything was fine:

System-wide power settings:
Currently in use:
 lidwake              0
 lowpowermode         1
 standbydelayhigh     18000
 proximitywake        0
 standby              1
 standbydelaylow      3600
 ttyskeepawake        0
 hibernatemode        3
 powernap             0
 gpuswitch            2
 hibernatefile        /var/vm/sleepimage
 highstandbythreshold 35
 displaysleep         2
 womp                 0
 networkoversleep     0
 sleep                2
 halfdim              1
 tcpkeepalive         0
 acwake               0
 disksleep            7

One can see standbydelayhigh to be equal to 5 hours, hence, the laptop is expected to enter standby mode after 5 hours of sleeping, but it doesn't: The picture shows a battery statistic for a whole period of time. Before update this statistic had a gap, because it was not collected during standby. One more evidence is that there is a catastrophic battery drain of 5 or 6 percents, i.e. the laptop consumes power while being closed. Before update the battery percentage decreases by the same 5 or 6 percents during a several days (compare with one night after update). Furthermore, before update I have to press a power button after opening a lid, because the laptop was in standby mode. Now the screen needs a very few time to show lockscreen without pressing the power button. Hence, the laptop doesn't enter standby. I looked at activity monitor, nothing prevents sleep there. pmset shows the same, i.e. nothing prevents sleep. I've tried to reset SMC and PRAM, but it didn't help. Bluetooth, Wi-Fi and Airdrop were disabled, when I closed the lid. I can't figure out, what else I can do to resolve the problem.

Here is the issue in a nutshell: My machine has taken to giving me an error dialog that begins with the following on every restart or shutdown and restart, manual or otherwise: > You shut down your computer because of > a problem. If you want to open the applications that were > open when > you shut down, click Open. The research I've done can be found [here](https://apple.stackexchange.com/questions/467835/pmset-repeat-cancel-does-not-remove-scheduled-events/467855#467855) I figured it was related to the automated wake up operations that keep getting made but, after digging around more, it apparently doesn't. I did find some information on the machine potentially being stuck in a kernel panic mode, but haven't been able to really pin down a potential fix. Any help here would be appreciated

I have been running a macOS Ventura virtual machine using both UTM and Parallels on a Ventura host and have been trying to put the VM to sleep so I can monitor what happens with the logs. However, it seems that the virtual machine is unable to go to sleep. Pressing Sleep from the menu bar has no effect and pmset sleepnow returns Unable to sleep system: error 0xe00002e2. I have tried setting sudo pmset -a disablesleep 0 but that doesn't work. Additionally, when I type pmset -g some settings appear to be missing even though I have set them and they are present in com.apple.PowerManagement.plist - namely hibernatemode and hibernatefile. I have also noticed that pmset -g uuid returns (NULL)`. Would anyone know how I could get the virtual machine to sleep? Maybe I need to change some boot arguments?

How do I programmatically access the "Screen On Usage" data shown in Settings->Battery?

I'm trying to schedule my Mac Mini to automatically turn off at the end of the day and then turn back on the next morning, login, and then run an AppleScript. This was all working fine in Monterey using power-saving options in the Control Panel. Unfortunately, I stupidly upgraded to Ventura and that option is now gone. I tried to reproduce the behavior using pmset, but it won't automatically log in anymore. I do still have auto login set in the System Settings. Is there something else I might be missing or some other workaround?

I've recently started getting this error when running any of these commands on my iMac (macOS Ventura 13.5.2 (22G91)):

sudo pmset sched cancelall
pmset: Error 0xe00002bc scheduling repeating events

sudo pmset repeat shutdown MTWRFSU 01:00:00
pmset: Error 0xe00002bc cancelling all scheduled events

Interestingly, I've noticed that I can switch between sleep/shutdown but I can't cancel:

sudo pmset repeat shutdown MTWRFSU 01:00:00
pmset: Error 0xe00002bc scheduling repeating events

pmset -g sched
Repeating power events:
  shutdown at 1:00AM every day
# error, but shutdown is set 🤔

sudo pmset repeat sleep MTWRFSU 01:00:00
pmset: Error 0xe00002bc scheduling repeating events

pmset -g sched
Repeating power events:
  sleep at 1:00AM every day
# error, but it switched to sleep 🤔

sudo pmset sched cancelall
pmset: Error 0xe00002bc cancelling all scheduled events
pmset -g sched
Repeating power events:
  sleep at 1:00AM every day

# cancelling doesn't work 🤔

I've searched everywhere without luck. I don't see any relevant info on my /var/log/system.log and I've tried resetting the SMC, but the issue remains. Any ideas? Here's the output of my pmset -g assertions in case it's useful:

pmset -g assertions
2023-09-09 10:30:37 +0200
Assertion status system-wide:
   BackgroundTask                 1
   ApplePushServiceTask           0
   UserIsActive                   1
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   ExternalMedia                  1
   PreventUserIdleSystemSleep     1
   NetworkClientActive            0
Listed by owning process:
   pid 156(bluetoothd): [0x0000081e0001885b] 00:00:20 PreventUserIdleSystemSleep named: "com.apple.BTStack"
   pid 745(sharingd): [0x0000061c000187e3] 00:08:54 PreventUserIdleSystemSleep named: "Handoff"
   pid 300(backupd): [0x00000188000185cd] 00:28:25 PreventUserIdleSystemSleep named: "Backup Job"
   pid 448(mdsync): [0x000005ab000b87d8] 00:10:46 BackgroundTask named: "com.apple.metadata.mds.scan"
   pid 106(powerd): [0x0000002b0008812b] 00:34:15 ExternalMedia named: "com.apple.powermanagement.externalmediamounted"
   pid 162(WindowServer): [0x00000065000981a8] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle serviceID:100000b78 service:AppleUserHIDEventService product:Karabiner DriverKit VirtualHIDKeyboard 1.6.0 eventType:3"
	Timeout will fire in 300 secs Action=TimeoutActionRelease
   pid 349(mds_stores): [0x00000039000b816a] 00:34:01 BackgroundTask named: "com.apple.metadata.mds_stores.power"
   pid 121(mds): [0x0000003f000b816b] 00:33:55 BackgroundTask named: "com.apple.metadata.mds.power"
Kernel Assertions: 0x4=USB
   id=503  level=255 0x4=USB creat=2023-09-09, 10:03 description=com.apple.usb.externaldevice.00100000 owner=USB3.0 Hub
   id=505  level=255 0x4=USB creat=2023-09-09, 10:03 description=com.apple.usb.externaldevice.00200000 owner=USB3.0 Hub
   id=506  level=255 0x4=USB creat=2023-09-09, 10:03 description=com.apple.usb.externaldevice.14400000 owner=USB 2.0 Hub [MTT]
   id=509  level=255 0x4=USB creat=2023-09-09, 10:03 description=com.apple.usb.externaldevice.14a00000 owner=Fast SSD
   id=510  level=255 0x4=USB creat=2023-09-09, 10:03 description=com.apple.usb.externaldevice.14900000 owner=Expansion Desk
   id=511  level=255 0x4=USB creat=2023-09-09, 10:04 description=com.apple.usb.externaldevice.14500000 owner=USB2.0 Hub
   id=512  level=255 0x4=USB creat=2023-09-09, 10:04 description=com.apple.usb.externaldevice.14b00000 owner=USB to PCIE Bridge
   id=514  level=255 0x4=USB creat=2023-09-09, 10:06 description=com.apple.usb.externaldevice.14200000 owner=USB2.0 Hub
   id=516  level=255 0x4=USB creat=2023-09-09, 10:07 description=com.apple.usb.externaldevice.14410000 owner=USB Advanced Audio Device
   id=517  level=255 0x4=USB creat=2023-09-09, 10:08 description=com.apple.usb.externaldevice.14470000 owner=USB 2.0 Hub
   id=519  level=255 0x4=USB creat=2023-09-09, 10:10 description=com.apple.usb.externaldevice.14420000 owner=Expansion Desk
   id=520  level=255 0x4=USB creat=2023-09-09, 09:55 description=com.apple.usb.externaldevice.14473000 owner=HD Pro Webcam C920
   id=521  level=255 0x4=USB creat=2023-09-09, 09:56 description=com.apple.usb.externaldevice.00110000 owner=USB3.0 Card Reader
   id=522  level=255 0x4=USB creat=2023-09-09, 09:56 description=com.apple.usb.externaldevice.00210000 owner=USB3.0 Card Reader
   id=523  level=255 0x4=USB creat=2023-09-09, 10:00 description=com.apple.usb.externaldevice.14240000 owner=USB 2.0 BILLBOARD
   id=524  level=255 0x4=USB creat=2023-09-09, 10:04 description=com.apple.usb.externaldevice.14540000 owner=USB 2.0 BILLBOARD
Idle sleep preventers: IODisplayWrangler

My current pmset -g is the following:

System-wide power settings:
Currently in use:
 lidwake              1
 autopoweroff         1
 standbydelayhigh     86400
 autopoweroffdelay    259200
 proximitywake        1
 standby              1
 standbydelaylow      10800
 ttyskeepawake        1
 hibernatemode        3
 powernap             0
 gpuswitch            2
 hibernatefile        /var/vm/sleepimage
 highstandbythreshold 50
 displaysleep         1
 sleep                10
 acwake               0
 halfdim              1
 tcpkeepalive         1
 disksleep            10

I've set the following:

displaysleep         1
sleep                10

Based on the man page for pmset:

displaysleep - display sleep timer; replaces 'dim' argument in 10.4 (value in minutes, or
     0 to disable)

and

sleep - system sleep timer (value in minutes, or 0 to disable)

One would think they're both separated (ie: Sleep the display first, then the computer); however this is the behaviour when set as described above (video) Basically, the screen dims at around 60 secs, sometimes over 100 secs, and then a few seconds later the computer goes to sleep, despite both being set far apart (screen: 1min --- Computer: 10 mins) None of the pmset -g log(s) spits out any useful output when this even occurs (at least none that I can identify). But in case anything helps: - Output for pmset -g log (pastebin) from the time the display dimmed and computer slept If anyone can lead me from here to my goal of being able to set the screen to dim after x mins and then the computer to sleep after x*2 mins. Thank you!

I am trying use my macbook with an external device in Clamshell Mode without the power adapter. Hence, I am following this tutorial . The author gives, first, a GUI approach. Then, he suggests the following commands on terminal:

pmset -g | grep hibernatemode

sudo pmset -a sleep 0
sudo pmset -a hibernatemode 0
sudo pmset -a disablesleep 1

sudo pmset -a sleep 1
sudo pmset -a hibernatemode 
sudo pmset -a disablesleep 0

The point that intrigues me the most is that before giving the instructions, he says: > Note: I have not tested these commands because Apple recommends not changing the hibernatemode using the pmset command, and these commands do just that. However, these commands will disable your laptop’s sleep on lid-close trigger, so they should also solve the problem of being unable to use your laptop in clamshell mode without the power adapter. That said, use them at your own risk. Hence, my doubts are: 1. Why does Apple not recommend tweaking hibernate-mode with the pmset command? 2. What could go wrong? Why is it dangerous? 3. If something bad happens, is it possible to revert the problem? And how to do it?

I am trying to schedule a Crontab job for, say, Monday at 12:59, even when my Mac is sleeping. To achieve this I use pmset repeat wake M 12:58:55 to wake up my Mac 5 seconds before the job. The first problem I encounter is that it is awakened (at the login screen) at 12:58:00 instead of 12:58:55. Since the login screen time before is goes to sleep again is 30 seconds, by 12:59:00 my Mac is already sleeping again, so my job never runs. Is there a way to start the job at the desired time and/or extend the time before my Mac goes back to sleep at the login screen? Currently is set to 30 seconds.

Unfortunately, Ventura doesn't support the GUI for poweron/poweroff. I want my Mac to startup on Sunday 04:00. So I enter sudo pmset repeat wakeorpoweron U 04:00:00 Then sudo pmset sched -g shows Sunday as expected, but also: Repeating power events: wakepoweron at 4:00 AM Sunday Scheduled power events: wake at 01/12/2023 09:42:46 by 'com.apple.alarm.user-visible-com.apple.acmd.alarm' It seems to me, that repeat and scheduled are not the same and handled differently. Accordingly, entering sudo pmset repeat cancel deletes the expected start on Sunday, but the scheduled 9:42 event remains active. A command like sudo pmset sched cancel is not accepted. What is the difference between repeat and scheduled?

I created a user called dummy. I login using Terminal into dummy and try to put Mac to sleep using pmset sleepnow. It does NOT work: Sleep error 0xe00002c1; You must run this as root.. I log into dummy using Fast User Switching in MacOS GUI. I switch back to my main user [keeping dummy logged in thanks to the Fast User Switching GUI]. I login again to dummy using Terminal and try pmset sleepnow. It's working now! 1. Why is that? 2. How does it work that the command requires sudo, unless I'm logged in the GUI [then it doesn't]? 3. What are other commands that magically start working if logged in using the MacOS GUI? EDIT: Previously I have thought it was like that because of the dummy being a "standard" account – I've just tested that it is the same issue for "administrator" accounts as well. Still, the questions remain: why/how does it matter, being logged in the GUI, for some commands to work.

I executed pmset hibernatemode 25 on my Macbook Pro 16" (Intel) running MacOS Monterey but it didn't seem to work. Searching here revealed several similar questions for High Sierra Catalina Mojave – and none of them had a satisfactory answer (or any answer at all). What is the current state of this feature? Broken? Is there anyone who can confirm that it works for them in Monterey (or any other version of MacOS)? How did you do it? Can you post your configuration? In case you have the same problem, you can report it to Apple at https://feedbackassistant.apple.com/ if you have a developers account (they are free).

I'm trying to create some monitoring for the thermal throttling during some build operations. For that I'd wanted to make use of pmset -g thermlog, which works great when used directly in the console, but seems to behave weirdly when piped to tee for example. What I can observe is that these 3 lines are printed immediately, but the actual values are only emitted if another update is emitted, and for that update only the timestamp is printed immediately and the data only when another event is emitted. (For illustration purposes I only included the first "partial" event).

$ pmset -g thermlog | tee foo.txt
Note: No thermal warning level has been recorded
Note: No performance warning level has been recorded
2022-06-02 14:52:03 +0200

This doesn't happen when used without the piping.

$pmset -g thermlog
Note: No thermal warning level has been recorded
Note: No performance warning level has been recorded
2022-06-02 14:51:34 +0200 CPU Power notify
	CPU_Scheduler_Limit 	= 100
	CPU_Available_CPUs 	= 16
	CPU_Speed_Limit 	= 100

And it works fine if I use therm instead of thermlog, altough that only ever prints the one event obviously.

$ pmset -g therm | tee foo.txt
Note: No thermal warning level has been recorded
Note: No performance warning level has been recorded
2022-06-02 14:51:55 +0200 CPU Power notify
	CPU_Scheduler_Limit 	= 100
	CPU_Available_CPUs 	= 16
	CPU_Speed_Limit 	= 100

I actually want to consume the process output via Java's java.lang.Process, but there I see the same issue with the event data not being written immediately to the out stream. Can somebody explain what is wrong here and ideally provide a fix for using thermlog. I know that I could just query therm repeatedly, but that has a lower resolution and is not what I'm looking for.

**Question Details:** Is it possible to make your macbookpro retina (2015) to hibernate (hibernate mode 25 i.e. fully powered off) via a shortcut? I still want it to go to sleep (the usual default safesleep) when closing the lid. Put differently: I would like to achieve the same settings that I had on Windows. **Windows setting:** On my Windows (7) laptop, besides shutdown and restart, I have the option of 2 settings: sleep or hibernate. Either pressing the sleep button on my keyboard or hibernating via the start menu (by pressing the start menu, clicking the right direction button and then clicking the "Hibernate" button). Neither method requires me to close the laptop lid. **Apple Mac OS Assumption:** I am under the impression that Mac OS has the ability to hibernate just like a Windows PC - i.e. totally powered off. In order to trigger this, I must first enable this feature [sudo pmset -a hibernatemode 25] and then trigger it by closing the lid. Please correct me if I'm mistaken about this. If I'm not mistaken, please see below: **Situation:** I've just started using a Macbookpro (V10.10). I like how it goes to sleep when closing the lid. However, I would like the option to hibernate via a button/keybaord shortcut. I understand I can change the hibernate mode to hibernate 25 via pmset. However, this makes the macbook go to hibernate whenever I close the lid - I don't want it to hibernate when closing the lid, rather just hibernate via a button/shortcut.