Windows 10: Windows 11 cannot enter sleep while setting "Screen: turn off after 15 minutes"default and...

Hi Guys, I am meeting an unexpected behavior: Windows 11 cannot enter sleep while setting "Screen: turn off after 15 minutes"default and "Sleep: PC goes to sleep after 1 minute" then idle 1 minute. Ideally, Windows would follow the power option setting, while the system idle 1 minute, the system will go to sleep, but fail, and Windows keeps working. Then, I change the power settings: "Screen: turn off after 1minute" and "Sleep: PC goes to sleep after 1 minute", setting done, idle 1 minute, system goes to sleep. and wakeup by KB normally. Once setting the same time value of "Sleep:

:)

 

Screens Sleeping after 5 minutes?

Hello all. I am stuck. We have a user at my place of work who we upgraded from Windows 7 to Windows 10. After the upgrade she noticed that now if she is inactive for 5 minutes her screens will go to sleep. The problem with this is that when the screens sleep, the computer is locked. This forces her to log back in every time. Not MAJOR but rather annoying to say the least.

We have a group policy that says after 15 minutes of activity the screens should go to sleep. For everyone else including myself, this works. Most others as well as myself are also running Windows 10. We have checked to make sure she is getting the group policies and she most definitely is.

Other things I have tried:

Restoring defaults to the power options
Checked the timeout settings in the registry, they were set at 900 seconds. (15 minutes)

Not sure what else to try. I am sure I am missing a couple of things I have tried.

 

Windows 10 (sometimes) goes to sleep after only 2 minutes of inactivity

Hello Michelle,

Unfortunately, steps you suggested did not fix the issue. I do not use a screen saver, so setting the option you mentioned is not available to me. Also, I doubt messing with the registry should be necessary. The current (default) Windows power plan that
I'm using has screen timeout set to 5 minutes when on battery, and 15 minutes when plugged in. Sleep timeout is set to 15, and 30 minutes, respectively. Therefore, the computer should not go to sleep before 15 or 30 minutes have elapsed.

 

Sleep settings are ignored, defaults to 2 minutes.

My Windows 10 laptop continues to sleep after 2 minutes regardless of the power settings. Many people have mentioned this exact same issue and are given multiple things to try. Then the issue gets marked as answered without any real solution.

My PC Setup:

• Dell Latitude E7440 (Windows 10, Upgraded from 8.1 more than 6 months ago.)
• Docked using a Dell E-Series Dock
• Dual AOC e2343FX monitors

Issue:

PC goes to sleep after 2 minutes regardless of the power settings. It is not just turning the monitors off, it's actually going to Sleep. Today I was working on a resume and cover letter. I would write the cover letter and then read it back to myself to
check the grammar and language, The PC would go into sleep mode during this process. It drives my nuts that I have to login to my PC every 2 minutes even though I'm actively using it.

Troubleshooting:

I ran the Control Panel "Troubleshoot problems" feature (Control Panel\All Control Panel Items\Troubleshooting\System and Security: Power). The troubleshooter runs and displays:





Then:





What actually happened:

• Power plan was changed from "High performance" to "Balanced (recommended)" *Troubleshooter message says the opposite.
  • On Battery:
    • Sleep after 30 minutes changed to 15 minutes.
  • Plugged in:
    • Sleep after 1 hour changed to 30 minutes.

The troubleshooter stated "Time before computer goes to sleep is too long" so why do the dropdowns allow for up to 5 hours? Why, when I make any allowable change does the sleep settings default to 2 minutes regardless of the setting? Also, why does Microsoft
offer multiple power plans and configuration options when they are just going to force you to "Use a more efficient plan"?

I have had Windows 10 for 6+ months now. This issue just started happening a couple of weeks ago. Nothing but Windows updates have been installed since before this started happening.