Solved Laptop sleeps when lid closed, even with setting disabled.

[green elephant]

I think I made a thread about this a while back to no success. My laptop goes to sleep when I close the lid even with the lid settings modified. I don't want it to sleep. Idk what exactly to do.

 

[gregrocker]

What is the setting in Power Options for what happens when you close the lid?

 

[green elephant]

What is the setting in Power Options for what happens when you close the lid?

 

[gregrocker]

I'd check in BIOS setup to see if there are any settings there. Your laptop may have a default setting for this because of the risk of overheating if the lid is closed.

I personally prefer Hibernate for Closing Lid and Power Button as well as timing out after an hour on a/c power. This is because while I could get it to instantly start lifting the lid if I use sleep, it keeps power to the RAM during sleep which wears it. But Hibernate is perfected in Win7, writes whatever works is open to the hard drive and then powers off, although you get a much faster startup. Many, many users prefer this for these reasons.

 

[green elephant]

I'd check in BIOS setup to see if there are any settings there. Your laptop may have a default setting for this because of the risk of overheating if the lid is closed.

I personally prefer Hibernate for Closing Lid and Power Button as well as timing out after an hour on a/c power. This is because while I could get it to instantly start lifting the lid if I use sleep, it keeps power to the RAM during sleep which wears it. But Hibernate is perfected in Win7, writes whatever works is open to the hard drive and then powers off, although you get a much faster startup. Many, many users prefer this for these reasons.

the thing is my laptop used to not sleep like it should and now it is for some reason.
also i dont know if its sleeping or hibernating,idk the difference.
ALSO could u specify how to check the bios

 

[gregrocker]

Look in your Power OPtions at your Power plan, then Advanced Settings under Sleep.

I suggest default settings but change Hibernate to 30 and 60.

You can also invoke Hibernate from the Start menu Shutdown button choices.

 

[green elephant]

Look in your Power OPtions at your Power plan, then Advanced Settings under Sleep.

I suggest default settings but change Hibernate to 30 and 60.

You can also invoke Hibernate from the Start menu Shutdown button choices.

This doesn't solve the issue? I have trouble following this but I got to the area I think you were talking about, looked and no luck to get it to stop,

 

[gregrocker]

What are the settings? Can you provide a screenshot of Advanced Power options for your Power Plan?

 

[green elephant]

What are the settings? Can you provide a screenshot of Advanced Power options for your Power Plan?

 

[gregrocker]

You don't have Hibernate enabled. Hibernate - Enable or Disable - Windows 7 Forums

What about the lid and power button settings?

 

[green elephant]

You don't have Hibernate enabled. Hibernate - Enable or Disable - Windows 7 Forums

What about the lid and power button settings?

What exactly do you mean? also what does enabling the hibernation do?

 

[gregrocker]

Hibernate is a better option than sleep for longer term, like after an hour. This is because it saves everything you've left out to the hard drive and then powers down the PC completely. But yet it starts up twice as fast. So many users prefer it to Shut Down and since it doesn't need to keep power to the RAM, it doesn't wear the RAM like sleep does.

So if you're stuck with a shutdown behavior I would make it Hibernate for closing the lid and power button, and set Hibernate after 30 and 60 minutes in Advanced Power Options under Sleep. But you need to enable it first by clicking the blue link I gave you.

Perhaps this will also make the Sleep malfunction resolve or become more obvious what the issue is. Try it.

Did you look in BIOS setup to see if there are forced Sleep settings by default on closing the lid perchance, or did I miss your reply to that question?

 

[PRW 82]

Hi - I wondered if a solution was ever found for this problem? I have exactly the same issue.

I have a one year old HP ProBook connected to a Dell monitor. I used to boot up the laptop in the morning, close the lid and the monitor would kick in, switching to a screensaver when the machine wasn't used for a while.

There has been a change and I cannot pinpoint why but now when I close the lid, the laptop goes into sleep mode and I have to wait for 60 seconds before wagling mouse / punching keyboard to enter login info and waking up the machine so it operates with the lid closed and monitor only. The other annoyance is that rather than switching to screensaver after a few minutes of idling, again the monitor drops into "power saving mode" and wakeup process is needed to get it going.

"When I close lid:" is set on both tabs to "do nothing". I've tried changing display settings between dual screen and monitor only, it doesn't seem to have an effect.

Any help that can be offered to resolve this nuiasance would be greatly appreciated.

 

[GokAy]

Try:

Open (Win+R) "gpedit.msc" and browse to Computer Configuration - Administrative Templates - System - Power Management - Button Settings and try setting "Lid Switch Action" (both on battery and plugged in) to Enabled and set Action to "Do nothing"

 

[SVimes]

Old post, but comes up when googling the problem. What worked for me: I had to reboot for the setting to take effect. Which is disappointing because I want to be able to switch back and forth, uninterrupted.

 

[GokAy]

SVimes, since this is a Group Policy setting, try the following command after a change:

gpupdate /force

 

[SVimes]

Oh, thanks! Sorry, I forgot to mention I'm using a script with powercfg.exe instead of the group policy configuration. So, it's like I'm changing the dropdown.

Oddly, the reboot was only required the first time. After that the setting seemed to take effect immediately. Maybe there was a pending reboot interfering, or something like that.

If I run into any more trouble, I'll try scripting the group policy.