How to Fix It When the Windows 10 Screensaver Is Not Working

Why Is the Windows 10 Screensaver Not Working?

A screensaver starts only after Windows detects no keyboard, mouse, touch, controller, or similar input for the selected wait period. It may also be affected by display drivers, background applications, power-management settings, damaged system files, and organization-wide policies.

The most common causes include:

• The screensaver is set to None, or the wait time is longer than expected.
• The display turns off or the computer sleeps before the screensaver can start.
• A mouse, game controller, USB receiver, webcam, or touchpad keeps reporting activity.
• A presentation, media, remote-access, or hardware utility suppresses idle behavior.
• A graphics, mouse, keyboard, or chipset driver is outdated or unstable.
• Group Policy prevents the user from enabling or changing the screensaver.
• A custom .scr file or photo folder is missing, blocked, or corrupted.

Fast Symptom Guide

1. Confirm That the Screensaver Is Enabled

Begin with the setting itself. Open Start > Settings > Personalization > Lock screen, then select Screen saver settings. You can also search the Start menu for “screen saver.”

1. Choose a built-in option such as Blank, Ribbons, or 3D Text.
2. Set Wait to one or two minutes while testing.
3. Select Apply.
4. Click Preview.

If Preview works, the screensaver component can run. The problem is probably that Windows never considers the computer idle. If Preview fails, select a different built-in screensaver. A custom screensaver can malfunction even when Windows itself is fine.

The optional On resume, display logon screen checkbox controls whether Windows asks you to sign in after the screensaver. It does not make the screensaver start, but it can improve privacy on a shared or office computer.

2. Compare the Screensaver, Display, and Sleep Timers

Windows can have three separate clocks ticking: the screensaver wait time, the display-off time, and the sleep time. If the monitor is set to turn off after two minutes while the screensaver waits five minutes, you will see a black display instead of floating ribbons. Windows is not confused; it is following the timer that finishes first.

Go to Settings > System > Power & sleep. Temporarily configure the display and sleep timers to occur later than the screensaver. For example:

• Screensaver: 2 minutes
• Turn off display: 10 minutes
• Put the PC to sleep: 15 minutes

Test while the laptop is both plugged in and running on battery, because Windows can store different values for each state. After the screensaver works, choose practical timings that balance privacy, energy use, and convenience.

3. Restart Windows and Test Without Touching Anything

A proper restart clears temporary processes and reloads drivers. Select Start > Power > Restart; do not merely close the laptop lid. After signing in, avoid launching games, streaming apps, presentation tools, or remote-desktop software. Set the screensaver wait time to one minute, remove your hands from the desk, and observe.

Be careful during the test. A slightly vibrating desk, a cat brushing the mouse, or a controller with a drifting analog stick can reset the idle timer. Yes, your screensaver problem may technically be caused by a cat. Technology remains humbling.

4. Disconnect Input Devices and USB Accessories

Small, repeated input signals are among the most common reasons a Windows 10 screensaver does not start. Disconnect nonessential devices, especially:

• Wireless mouse and keyboard receivers
• Gamepads, steering wheels, joysticks, and drawing tablets
• Webcams, USB audio devices, and docking stations
• External touchpads, fingerprint readers, and specialty controllers

Then test with only the basic keyboard and mouse connected. For a wireless mouse, switch it off completely. Clean the optical sensor and place the mouse on a stable, nonreflective surface. A dirty sensor or unsuitable surface can cause tiny cursor movements that Windows interprets as activity.

If the screensaver starts after one device is removed, reconnect devices individually until the issue returns. Update or reinstall the driver for the identified accessory, try a different USB port, and check the manufacturer’s support utility for firmware updates.

5. Close Apps That Can Keep the PC Active

Some programs intentionally prevent idle actions while they are playing media, presenting slides, recording the screen, maintaining a remote session, or monitoring hardware. Close video players, browser tabs playing media, presentation apps, game launchers, RGB utilities, communication software, remote-access tools, and screen-recording programs.

Open Task Manager with Ctrl + Shift + Esc. Review the Processes and Startup tabs for software installed shortly before the problem began. Do not end unfamiliar Windows processes at random. Instead, close recognizable third-party apps and test again.

Check Power Requests When Display Sleep Also Fails

If the screensaver, display-off timer, and sleep function all refuse to activate, open Command Prompt as administrator and run:

This command lists applications and drivers that are actively requesting Windows to keep the display or system awake. The result may identify a browser, audio driver, media process, or other component. Close or update the named program rather than immediately forcing an override, which could interrupt legitimate playback or recording.

6. Update Windows 10 and Hardware Drivers

Driver problems can interfere with display transitions and idle detection. Open Settings > Update & Security > Windows Update, select Check for updates, install available updates, and restart the computer.

Next, right-click Start and open Device Manager. Focus on these categories:

• Display adapters
• Mice and other pointing devices
• Keyboards
• Human Interface Devices
• Universal Serial Bus controllers

Right-click the relevant device and choose Update driver > Search automatically for drivers. If Windows finds nothing and the issue began after a hardware change, obtain the correct driver from the PC or component manufacturer. Avoid mystery “driver updater” tools; they often create more excitement than accuracy.

Roll Back a Recently Changed Driver

If the screensaver stopped working immediately after a driver update, open the device’s Properties, select the Driver tab, and use Roll Back Driver when available. Restart and test. A newer driver is not automatically a better driver for every hardware combination.

7. Reset the Current Power Plan

A damaged or heavily customized power plan can produce odd idle behavior. Open Control Panel > Hardware and Sound > Power Options. Beside the active plan, select Change plan settings, then choose Restore default settings for this plan.

After restoring the plan, return to Screen Saver Settings and re-enter your preferred wait time. Resetting a plan removes its custom power values, so note any special battery or sleep settings you want to recreate later.

8. Test a Built-In Screensaver Instead of Photos or a Custom File

The Photos screensaver depends on an accessible image folder. A custom screensaver depends on a valid .scr file and may depend on older libraries or graphics behavior. To isolate the issue, choose Blank or Ribbons and select Preview.

If the built-in option works, inspect the custom setup:

• Confirm that the photo folder still exists and contains readable images.
• Avoid network folders or removable drives that may disconnect.
• Reinstall the custom screensaver from a trusted publisher.
• Scan downloaded .scr files before opening them; Windows treats them as executable programs.

For reliability, use a local folder with ordinary JPG or PNG files rather than a cloud-only folder whose contents are not stored on the PC.

9. Check Group Policy on Windows 10 Pro or Managed PCs

If settings are grayed out, keep reverting, or cannot be saved, a local or organizational policy may control them. On Windows 10 Pro, Enterprise, or Education, press Windows + R, enter gpedit.msc, and browse to:

User Configuration > Administrative Templates > Control Panel > Personalization

Review policies such as Enable screen saver, Screen saver timeout, Force specific screen saver, and Prevent changing screen saver. A policy that enables the screensaver without defining a timeout can also produce unexpected behavior.

On a work or school PC, do not bypass company policy. Contact the administrator, especially when the settings return after every sign-in. Windows 10 Home does not include the Local Group Policy Editor by default, so this step usually does not apply there.

10. Repair Windows System Files with DISM and SFC

If built-in screensavers do not preview, Windows features behave strangely, or the problem survives the earlier checks, repair the component store and protected system files.

1. Search for Command Prompt.
2. Right-click it and select Run as administrator.
3. Run the following command and allow it to finish:

Then run:

Do not close the window before the scan reaches 100 percent. Restart Windows afterward and test a built-in screensaver. DISM repairs the Windows component source used for repairs, while System File Checker examines protected files and replaces damaged copies when possible.

11. Use a Clean Boot to Find Software Conflicts

A clean boot starts Windows with Microsoft services and a minimal set of third-party startup items. It is useful when the screensaver works after a fresh restart but fails once normal background software loads.

1. Search for msconfig and open System Configuration.
2. On the Services tab, select Hide all Microsoft services.
3. Select Disable all, then click Apply.
4. Open the Startup tab and select Open Task Manager.
5. Disable enabled third-party startup items, restart, and test.

If the screensaver works in the clean-boot environment, re-enable items in groups until the problem returns. This divide-and-test method is faster than blaming every app one at a time. When finished, restore Normal startup and re-enable the services and startup items you need.

12. Try System Restore if the Problem Started Recently

When the issue began after a driver, utility, or configuration change and you cannot identify the culprit, System Restore may return system settings to an earlier restore point without deleting personal documents.

Search for Create a restore point, open System Protection, select System Restore, and choose a restore point created before the screensaver failed. Review the affected programs before proceeding. Back up important files first, even though System Restore is designed to preserve personal data.

Reinstalling or resetting Windows solely for a screensaver problem is rarely justified. Consider major recovery options only when the PC has broader stability problems and you already have a verified backup.

Practical Troubleshooting Experience: What Usually Solves the Problem

Real-world troubleshooting tends to reward a simple habit: separate “the screensaver cannot run” from “the computer never becomes idle.” The Preview button is the fastest dividing line. When Preview displays the animation correctly, reinstalling Windows or running repair commands is premature. The screensaver engine is functioning; something is resetting the idle timer. At that point, peripherals and background applications deserve attention before system repair.

A common scenario involves a desktop PC with a wireless mouse, a game controller, and a USB headset. The screensaver works immediately after setup, then mysteriously stops several weeks later. Turning off the mouse changes nothing, but unplugging the controller fixes the problem. One analog stick has developed slight drift, sending tiny input values even while nobody touches it. The owner never sees a moving pointer because controller input does not have to move the mouse cursor. Replacing or recalibrating the controller solves both the screensaver and sleep problems.

Another frequent pattern appears after installing conferencing, presentation, or remote-access software. The program continues running in the notification area after its window closes. It may keep the PC awake to avoid interrupting a call or presentation. Exiting the application completely, disabling its “prevent sleep” option, or updating it restores normal idle behavior. This is why testing directly after a restartbefore opening the usual collection of appsis so useful.

Timing conflicts also cause unnecessary confusion. A user chooses a five-minute screensaver but configures the monitor to turn off after three minutes. The expected photos never appear, so the screensaver seems broken. In reality, the display powers down first. Temporarily setting the screensaver to one minute, display-off to ten minutes, and sleep to fifteen minutes creates a clean test. Once the result is confirmed, the timers can be adjusted to sensible values.

On business computers, the clue is often a gray setting or a preference that changes back after sign-in. That behavior usually points to Group Policy or device management rather than a local defect. Registry edits may appear to work briefly, only to be overwritten when policy refreshes. The productive solution is to ask the administrator which security policy applies, not to start an endless tug-of-war with a domain controller.

Finally, advanced repairs are most valuable when several Windows features fail together. If Preview does nothing, built-in personalization tools crash, and other interface components behave oddly, DISM and SFC become reasonable. If the issue began immediately after a driver or utility update, rolling back that change or using System Restore may be more direct. Good troubleshooting is not about using the most powerful tool first. It is about running the smallest test that tells you what to try next.

Keeping a brief change log makes repeated testing easier. Record which device was disconnected, which app was closed, and whether Preview or automatic activation worked afterward. Change only one major variable at a time. Otherwise, the screensaver may return and leave you wondering whether the mouse, driver update, power reset, or ceremonial reboot actually fixed it.

Conclusion

When the Windows 10 screensaver is not working, begin by confirming the selected screensaver and wait time. Next, align the power timers, restart the PC, disconnect input devices, and close software that may keep Windows active. If the problem continues, update drivers, reset the power plan, test a built-in screensaver, inspect applicable policies, and repair system files.

The fastest successful fix is often surprisingly ordinary: a drifting controller, a twitchy mouse sensor, a hidden media process, or a display timer scheduled too early. Troubleshoot in order, test after every change, and let the evidencenot frustrationchoose the next step.