How to disable boot on lid opening on my MacBook Pro?

There is no "AutoBoot". It was added by the command the OP used to try to set it. However, the OP did not realize the "AutoBoot" option is only for Intel Macs. You can delete that firmware variable using the following command:

sudo  nvram  -d  AutoBoot

Or you can just clear the NVRAM (it won't clear the computer name and possibly some other similar items)....this will work on an Apple Silicon M-series Mac as well as an Intel Mac and requires a reboot afterwards so the OS can use the updated settings:

sudo  nvram  -c

I've never tried it, but theoretically it should be possible to set the Apple Silicon M-series Macs' "auto-boot" variable to false by using, but I don't know if it will actually change the behavior since I have not seen any reference to disabling auto boot on an Apple Silicon M-series Mac:

sudo  nvram auto-boot=%00

Can someone that has NOT previously run `sudo nvram AutoBoot=%00` tell us what the default value is?

Please run `nvram -p | grep "AutoBoot"` (NOT auto-boot) in Terminal to see the default value. If it doesn't show anything, then I'd like to know that as well. NOTE that this command will NOT make any changes -- it only shows information to the user.

This might also help future users that visit this post.

Thank you!

Tried “sudo nvram auto-boot=false” with brand new MacBook Pro Sonoma 14.4.1. Computer refused to start after shut down and opening lid. Had to hold down power key and select hard drive to make it start up. Would not recommend using this command in terminal.

Is Apple trying to micromanage the behavior of the user? I would prefer to not have my computer start every time I open the lid. Apple needs to remove this behavior from their OS. Thinking about returning this laptop for a full refund…

faheemkodi wrote:

WARNING: Please don't `sudo nvram auto-boot=false`

I tried and it bricked my Macbook Air M1. Had to revive it using Configurator with another Macbook.

Good to know. Thanks for the update.

FYI, you may have been able to recover by booting into Recovery Mode and clearing the NVRAM by using the following command in the Terminal app located on the Utilities menu on the menu bar:

nvram  -c

This command to clear the NVRAM is safe as I have used it on Apple Silicon M-series Macs and can sometimes allow a M-series Mac to boot normally again. You may see it report an error being unable to delete the computer name (may be several related errors) which is normal & can be ignored. If the Mac boots normally again, then make sure to remember to update the default Startup Disk System Settings to point to the internal boot drive since the default startup disk was cleared when clearing the NVRAM.

A bit late, but the auto-boot=false doesn't brick it, it can be fixed.

Power down

Hold the power button for ~10 seconds

Select Options

Open Terminal from the menu

Type EITHER:

"nvram -c" to reset ALL NVRAM options OR

"nvram auto-boot=true"

Restart and fixed.

BenT wrote:

A bit late, but the auto-boot=false doesn't brick it, it can be fixed.

"nvram auto-boot=true"

Restart and fixed.

FYI, a better option would be to delete that variable name used such as:

nvram  -d  auto-boot

Leaving the variable in the NVRAM is not ideal. This delete option is actually better than my original suggestion of clearing all of the NVRAM, but I decided against it to keep things simpler for people not familiar with the command line since they may have also inadvertently used some other variable name or mis-spelled it (either when setting it or when trying to delete the variable).

Hi

It doesn't look good when some of the solutions have caused issues. I've sent a feedback to Apple, hopefully the more of us send a complaint the more likely they will to change it.

"If you need to stop this behavior--to clean the keyboard, for example--you can force a shutdown once.

Press and hold the left Control and Command buttons with the right Shift button for a total of 7 seconds. Without releasing them, press the Power button and hold them all together for an additional 7 seconds. Your Mac can only be powered on by using the Power button.

Unfortunately, there is no way to disable this permanently."

https://apple.stackexchange.com/questions/395453/how-to-prevent-macbook-pro-from-powering-up-by-pressing-any-key#:~:text=Your%20Mac%20can%20only%20be,way%20to%20disable%20this%20permanently.

simontompkins wrote:

Hi

It doesn't look good when some of the solutions have caused issues.

Apple is not here on this forum. All suggestions come from other regular users such as yourself. It doesn't help that Apple does not always provide detailed documentation of their systems. On my M1 & M2 laptops, there is an NVRAM variable called "auto-boot" which is set to "true". I have no clue what this actually does or why it is there since I have not configured it. If something is configured as "true", it should also be configurable to "false", but it is Apple after all, so all bets are off these days.

The only "nvram" command I know that works and is safe for both Intel & Apple Silicon M-series Macs is the one to clear all of the NVRAM settings/variables which I listed (nvram -c) since I have used it on multiple M-series Macs to successfully fix issues (usually boot related issues). Any other "nvram" options to configure NVRAM variables/settings that are found online are only meant for Intel based Macs.

I've sent a feedback to Apple, hopefully the more of us send a complaint the more likely they will to change it.

We can only hope. I'm convinced no one approving these ridiculous configurations are actually using their own creations day to day.

Ran the disk utility after my previous issue with “sudo nvram auto-boot=false” (please read my previous post) and it returned there was a disk error which was repaired. I suspect it was a boot block error. Still not sure if the boot sequence is ok but keeping an eye on it.

Readers here are other Users like you. To let Apple know what you think, use the feedback page:

Apple Product Feedback

.

What is the output of:

nvram -p | grep -i boot

?

It seems you can set ‘auto-boot’ as false.

‘AutoBoot’ is the variable name you added or introduced.