Windows 10: Screen Saver settings acting weird

Have win10 home installed since its release and it has run fine except for a screen saver issue I am having.

Heres what happens.I do a fresh boot in the morning and the SS never will come on until I goto personalize and glick on a new screen saver and select one then I can can go back and select my original.I only need to do this so I can hit the "apply" button.I also have to reset the amount of time before the SS will come on.
I normally haveit set to 3 minutes but every reboot it sets itself to 1 minute.

I have to do this after every reboot and cant figure out why.
Everything else is working great with no other issues.
Any ideas or thoughts on this issue?

:)

 

photos

How much phone memory do you have? And do you have a backup of your contacts and messages and calendar? Your phone is acting all weird.



And what do you mean by "screen saver" active all the time?

 

Windows 10 goes to sleep

Thanks for the suggestion, but I don't have a screen saver set on any of my systems, and I'm seeing sleep weirdness on 100% of them under 10.

BTW, you can get to screen saver by just hitting start and starting to type 'screen saver' until it pops up.

 

I have Win 10 Pro x64. No matter what I do, after a couple minutes, the console locks up and requires a cntl-alt-del to unlock it with my user ID/Password. I have checked local policies, screen saver (set to NONE) timeout setting, power options settings. I have tried the Win 8 workaround to reset power plan to the defaults. I don't have time to stand, stretch, and scratch my behind before the console locks up.

An exception is if I have one (of four) screens full screen running Hauppauge WinTV v8, or a browser watching streamed video at full screen.

 

I'd like to suggest another option that seems to work for me and I'd like some feedback as to whether it work for others. Here's what I did:

Start/Search and type gpedit.msc, Right click the gpedit results and Run As Administrator. In the Elevated Group Policy Editor, on the Left Panel, go to User Configuration/Administrative Templates/Control Panel/Personalization/Enable Screen Saver and enable the Policy. Once you have enabled that policy, go down and also enable Screen Saver Timeout. Note that in the Screen Saver Timeout policy there's an option to set the number of second for the timeout with the default being 900 seconds or 15 minutes.
Once you've enabled both policies and set the timeout if different from the default, exit the group policy editor. If you now go the screen saver settings in Control Panel you will notice that the wait period will match the minutes you entered in the group policy editor but it will be grayed out preventing you from changing the value unless you go back into the group policy editor and change it there.
Many were complaining that the wait value reverts to 1 and that is why they turned off fast booting but I have fast booting turned on and with the group policy changes I made my wait time is no longer reverting to 1 minute and remains at 15 minutes.

Will someone please give this a try to see of this solves the problem of the wait time reverting to 1 if you have fast booting turned on? If it doesn't work all you need to go is go back into the group policy editor and set both policies to "Not Configured".

 

Hello moondoggy and thank you for your suggestion!
My problem was slightly different, as upon new boot, the screensaver was disabled completely and never started. I would have to "fix" it in Personalize every time I turned on the computer. However, using the method you illustrated, it now begins regularly after the 600 seconds I set on the group policy editor.
Thank you again!

 

Thank you for getting back to me with your results. I've posted this work around on another forum and the people that have resoled this issue via turning off the fast boot up seem to be reluctant to try this fix for some reason or can't because you have to be running Windows 10 Pro in order to do group policy editing which is a requirement I failed to state when I posted my suggested work around. Anyway, I'm happy it's working for you and perhaps others will try it and report back as well.