ThisCalculator

Everyday

Prevent Users From Changing Screen Saver

Updated · Standard formula, shown below

Prevent Users From Changing Screen Saver

To prevent users from changing the screen saver on a Windows computer, you can enforce a policy via the Local Group Policy Editor (gpedit.msc) or the Windows Registry. This article explains how to lock the screen saver settings for standard users and provides context on why and when you might need to do this.

Why Lock the Screen Saver?

Screen saver settings are often locked in managed environments—schools, libraries, corporate offices, or shared kiosks—to maintain a consistent look, enforce security policies (like requiring a password on wake), or prevent users from disabling the screen saver entirely. If a screen saver is part of an organization’s security policy (e.g., it locks the workstation after inactivity), letting users change it could create a security gap. For home users, locking the setting can prevent children or other family members from accidentally changing the timeout or selecting a screen saver that interferes with work.

How Windows Screen Saver Settings Work

The screen saver settings are stored in the Windows Registry under HKEY_CURRENT_USER\Control Panel\Desktop. The relevant values are:

  • ScreenSaveActive – 1 (enabled) or 0 (disabled)
  • ScreenSaveTimeOut – seconds of inactivity before the screen saver starts
  • SCRNSAVE.EXE – the path to the screen saver executable
  • ScreenSaverIsSecure – 1 (require password on resume) or 0 (no password)

When a user changes the screen saver through the Settings app or Control Panel, these registry values are updated. The Local Group Policy Editor provides a more user-friendly way to enforce the same settings without editing the registry manually.

Method 1: Using Local Group Policy Editor

The Local Group Policy Editor is available in Windows Pro, Enterprise, and Education editions. It is not included in Windows Home. To use it:

  1. Press Win + R, type gpedit.msc, and press Enter.
  2. Navigate to User Configuration > Administrative Templates > Control Panel > Personalization.
  3. Double-click the policy named Enable screen saver.
  4. Select Enabled to force the screen saver on, then click OK.
  5. Double-click Screen saver timeout to set the number of seconds (e.g., 600 for 10 minutes).
  6. Double-click Password protect the screen saver to enforce the “On resume, display logon screen” option.

Once these policies are set, the corresponding options in the Settings app and Control Panel become grayed out for all users on that computer. To revert, set each policy back to Not Configured.

Method 2: Using the Windows Registry

If you are on Windows Home, or you prefer a registry approach, you can set the same values manually. The registry keys are under HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Control Panel\Desktop. This is a policy key, which takes precedence over the user’s own settings.

  1. Press Win + R, type regedit, and press Enter.
  2. Navigate to HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Control Panel\Desktop. If the Desktop key does not exist, right-click on Control Panel and create a new key named Desktop.
  3. Create the following DWORD (32-bit) values:
    • ScreenSaveActive = 1
    • ScreenSaveTimeOut = 600 (or your desired seconds)
    • ScreenSaverIsSecure = 1
  4. Close the Registry Editor and restart the computer or log off and on for the changes to take effect.

Note that these policy keys override the user’s personal settings. If you want to set the screen saver itself (the executable), create a string value named SCRNSAVE.EXE and set its value to the full path of the .scr file, e.g., C:\Windows\System32\Mystify.scr.

What About Windows Home? Alternative Tools

Windows Home does not include gpedit.msc, but the registry method works exactly the same. If you prefer a graphical tool, you can use the Settings app to set the screen saver, but that does not prevent users from changing it. For a more robust solution on Home, you could create a batch file or PowerShell script that applies the registry changes at logon, but that requires some scripting knowledge. Another option is to use the netplwiz or User Accounts settings to make the user a standard user (not an administrator), which limits their ability to change system-wide policies, but the screen saver settings are per-user, so a standard user can still change their own settings unless the policy key is in place.

Common Problems and Troubleshooting

If the policy does not seem to take effect, check the following:

  • Policy not applied – Group Policy refreshes periodically, but you can force it by running gpupdate /force in Command Prompt (as admin).
  • Wrong registry hive – The policy key must be under HKEY_CURRENT_USER, not HKEY_LOCAL_MACHINE, unless you want to apply it to all users. For all users, use HKEY_LOCAL_MACHINE\Software\Policies\...\Desktop but note that per-user policies take precedence.
  • User has admin rights – An administrator can manually edit the registry or change the policy back. If you need to prevent even admins from changing it, you would need to restrict access to the registry keys or use a more advanced security policy.
  • Screen saver settings are grayed out but still changeable via registry – The policy only grays out the UI; a savvy user could still edit the registry directly if they have write access to that key. To prevent that, you would need to set NTFS permissions on the registry key, which is beyond the scope of this article.

Frequently Asked Questions

Can I prevent users from changing the screen saver on Windows 10 Home?

Yes, the registry method works on Windows 10 Home. You don’t need gpedit.msc; just create the policy keys under HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Control Panel\Desktop as described above.

Will the policy affect the lock screen or just the screen saver?

The policy affects the screen saver settings specifically. The lock screen (the one that appears when you press Win+L) is a separate feature and is not changed by these policies.

How do I set the screen saver to a specific one (e.g., Photos) via policy?

You can set the SCRNSAVE.EXE value to the path of the screen saver file. For the Photos screen saver, the file is usually C:\Windows\System32\PhotoScreensaver.scr. You can also set the ScreenSaveTimeOut to control the delay.

What if I want to prevent users from changing the screen saver but allow them to change other personalization settings?

The policies under Personalization only affect the screen saver. Other settings like wallpaper, accent colors, and lock screen remain unchanged unless you configure separate policies for them.

Can I apply this policy to all users at once?

Yes, you can use the Local Group Policy Editor under Computer Configuration > Administrative Templates > Control Panel > Personalization for a computer-wide policy. Alternatively, you can edit the registry under HKEY_LOCAL_MACHINE instead of HKEY_CURRENT_USER, but note that per-user policies override local machine policies.

Why is the screen saver setting grayed out even though I didn’t set a policy?

This can happen if a third-party security software or an IT administrator has applied a policy remotely. Check the registry keys listed above to see if they exist; if they do, that’s the cause. You can also run gpresult /r to see which policies are applied.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.