Screen saver activates every minute independently on how many minutes is configured #Screensaver

Luis Martinez 0 Reputation points
2026-05-12T02:51:44.4333333+00:00

Screen saver activates every minute independently on how many minutes is configured

Windows for home | Windows 11 | Desktop, Start, and personalization | Screen saver
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-05-12T02:51:52.64+00:00

    On Windows 11, the screen saver start time is controlled by the configured idle timeout. If the screen saver is activating every minute regardless of the value set in the Screen Saver Settings dialog, check whether a policy or MDM configuration is overriding the local setting.

    In managed environments (for example, when the device is joined to Azure AD or managed by Intune), the screen saver timeout can be enforced by the ADMX-backed policy CPL_Personalization_ScreenSaverTimeOut:

    • This policy specifies how much user idle time must elapse before the screen saver is launched.
    • When configured, it can be set from 1 to 86,400 seconds. If set to 60, the screen saver will start after 1 minute of inactivity, even if a different timeout is chosen in the local Screen Saver Settings UI.
    • When this policy is active, the local UI value is effectively ignored.

    To resolve the “always 1 minute” behavior, an administrator must:

    1. Check whether CPL_Personalization_ScreenSaverTimeOut is configured via MDM or Group Policy.
    2. If it is set to 60 seconds, change it to the desired number of seconds (for example, 600 for 10 minutes) or set it to 0 to prevent the screen saver from starting.
    3. Ensure the “Enable Screen Saver” policy is not forcing a conflicting configuration, because the timeout policy has no effect if “Enable Screen Saver” is disabled.

    If the device is not managed, verify that no MDM or policy configuration is applied and then adjust the timeout directly from Settings:

    1. Open Settings → Personalization → Lock screen.
    2. Select Screen saver.
    3. In Screen Saver Settings, set the desired Wait time in minutes and apply.

    If a policy is present, the UI value will not change the effective timeout until the policy is removed or updated.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Thomas4-N 22,380 Reputation points Microsoft External Staff Moderator
    2026-05-12T07:46:22.4266667+00:00

    Hello Luis Martinez,

    The behavior you're describing — screen saver triggering after roughly a minute no matter what Wait time you set — is almost always caused by a second idle timer overriding the screen saver, not by the screen saver setting itself. On a home Windows 11 device the usual suspects, in order, are:

    1. The "after I've been away, sign me in again" timer. Open Settings > Accounts > Sign-in options > expand Additional settings > look at "If you've been away, when should Windows require you to sign in again?". If this is set to "1 minute" or "Every Time", Windows will lock the screen after that interval, which looks identical to the screen saver firing. Change it to a longer value (or Never) and test.
    2. Dynamic Lock Same page (Sign-in options) > Dynamic lock. If "Allow Windows to automatically lock your device when you're away" is on and you have a Bluetooth phone paired, Windows locks the screen whenever the phone wanders out of range. Turn it off and test.
    3. "On resume, display logon screen" in Screen Saver Settings. Settings > Personalization > Lock screen > Screen saver. Either set the screen saver to None, or uncheck On resume, display logon screen, then Apply.
    4. Stale registry value. Press Win + R, type regedit, go to HKEY_CURRENT_USER\Control Panel\Desktop, and confirm ScreenSaveTimeOut matches your intended value in seconds (e.g. 2700 for 45 minutes). If it shows 60, that's your culprit — fix it there.
    5. Leftover policy from a previous setup. If this PC was ever joined to a work account or had a security/management agent on it, run gpresult /h gpreport.html from an elevated Command Prompt and search the report for "Screen saver" / "Personalization" entries. If there's a policy still applied, that's overriding the UI value.

    If you can share whether the device has ever been joined to a work or school account, and whether a phone is paired by Bluetooth, I can narrow it down further.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.