Windows 10: No Screensaver after 10 update

Well, if you make a shortcut for Control Panel on the desktop you can change some of the settings in there under "System and Security"->"Power Options" - The Screen Saver can be selected from "Appearance and Personalization" as usual. Try making the changes via control panel instead of the Settings tile.

 

I am also having this exact problem. This is the first thing I find on the web about it.

I upgraded from Win 7 pro to Win 10 pro. I have 2 screens one that is 1080p and the other 1280x1024. I have upgraded my radeon 6950 to the latest drivers. I don't use a screensaver just screen time outs but neither work. My screen will time out if I am logged out. I also tried creating another profile and it also doesn't work when logged into that new profile. I do use a password for my PC and it is set to prompt for it after return from screen timeout or screen saver.

 

Nope no password here and mine works as it should.

 

Hi Guys, I updated to Win10 fm Win7 on 1st Aug. The screensaver worked initially, then after 7/8 days it stopped being activated, but I could still run it from Settings/ Personalization/lock screen/screen saver settings/ preview . I ran it via this method on the morning of 10th Aug. Later in the day all Screen Saver options(except photos) caused the following text "The screen can't run because it requires a newer video card or one that is compatible with Direct 3D" . Unless somebody came in and changed my MBO the above text is incorrect. I was very impressed with Windows 10 initially, the screen saver is not important. BUT this morning I attempted to update one of my own Word files and it stopped me because "I needed permission" I hope they correct these problems soon !! Maybe they might consider employing programmers who know the system in detail. Not as appears to be happening in IT, where people know very little about a great many computer programs/systems !!*sarc

 

After doing a lot of google searching I came across 2 potential fixes. I used both of them and they have solved my problem. The screensaver stays at whatever time I set it for and it works (with or without passwords).
Power Options - Add "Console lock display off timeout";

http://www.eightforums.com/tutorials...f-timeout.html
(I think the "Add Console Lock" was what did the trick but I also did....)

Local Group Policy - Reset to Default

http://www.sevenforums.com/tutorials/214461-local-group-policy-reset-default.html

 

You LEGEND. That fixed the screensaver issue for me, but I need to wait to see if the power saving has also worked. I'll report back and if it doesn't work I'll reset my local GPO's as they will have been changed when I was using 8.1 Pro and have been ported across.

 

I can also confirm that the 'Add Console Lock' registry change has made my screensaver AND my power saving options both start working properly. Massive thanks to @Emb for that. Just in case it helps anyone:

windows 10 screensaver, windows 10 power options, windows 10 monitor standby, windows 10 monitor wont go on standby,

 

Does this only work if you manually lock your console first?

 

No. It just works now; directly from the desktop or from a locked screen.

 

So far neither of these changes have fixed my screen saver coming on or my monitors getting turned off. *Sad It was a good find though.

 

As I search for solutions to this problem, I notice that there are many references to similar problems on Windows 8/7. Although I upgraded to 10 from 8.1, I never had the screensaver problem before the upgrade.

I'm not really comfortable with just run this and it'll work approach. I like detailed explanations of what's wrong and how the fix works. I'm trying the "Console lock display off timeout" setting first.

Here's the setting from the article:
Code: HKLM/SYSTEM/CurrentControlSet/Control/Power/PowerSettings/7516b95f-f776-4464-8c53-06167f40cc99/8EC4B3A5-6868-48c2-BE75-4F3044BE88A7[/quote] I found that the Attributes key already existed on my system, but it was set to '1' by default. I changed the value to '2' as would've happened if I had imported the registry file. I'm hoping it'll work.

Microsoft sure doesn't make it easy to get there...

Settings > System > Power & sleep > Additional power settings (completely different UI here > Change plan settings > Change advanced power settings > Display

The Console lock display off timeout setting didn't appear after I made the change. I don't think it'll fix the screensaver, but I'll wait before I change it back.

Update 20150812_201721-0500: Yesterday, it seemed that my screensaver was working, but I wasn't sure that it was because of the changes I made to the registry. When I go into the screen saver settings and save them again, it often starts working. So, I was going to wait a day and see if the screen saver kicked in during a normal day, but an update was automatically applied this morning (KB3081436) that has apparently reverted my change. I'll make the change again and see what happens.

What the heck is up with those registry keys?! Couldn't they have created a key named ShowConsoleLockDisplayOffTimeout instead of those long strings of hex characters?! </rant>

There is an updated video driver available for my system (HP laptop, Intel 4600 graphics), but when I install it performance is negatively impacted and whenever I run any games I get an error message that says access was denied to the graphics hardware. I had to rollback the driver update and use PowerShell to prevent the system from automatically re-applying it (ref: touchpad - Prevent Windows 10 from installing/updating a specific driver? - Super User). I don't know if the video driver update would've fixed the screensaver problem, but that's an unrelated issue.

 

The fix did not work for me either. Starting to get very frustrated.

 

It is really frustrating. You don't realise how essential the functionality is until you discover your screen has been on for 2 days and that's really not good for the screen or your electricity bill!

 

Well, it work on 2 of the 3 computers I am having this issue with but did not work on the 3rd computer. Go figure, I am completely lost for now. At least 2 of the 3 are fix...

 

Someone will get it figured out....just be patient and keep trying suggestions. I haven't had the time to really mess with this much the last day and a half but hopefully tomorrow I can make some time.