Windows 10: Screensaver delay time resets to 1 on boot

My husband, who was an Advisory Programmer with IBM, looked into another forum which
addressed this problem specifically. The consensus was that the Logitech devices connected
to the USB ports were the culprits. One 'solution' which worked was to disable the HID in the
Device Manager of the Control Panel. Rather than do that, we disconnected the Logitech Mouse
and the Logitech Microphone (used for Skype) before booting up. Voila, the delay was not
reset to zero and the screensaver operated normally. We reconnected the Logitech devices
with no ill effect. Whether this is a problem unique to Logitech has not been determined.
Whether Microsoft will look into this is probably very remote......

 

I've got a Logitech HID mouse and I don't have the reset problem. My wife's comp has a Logitech mouse and keyboard and she doesn't have the problem, either.

So, the Logitech theory doesn't look well founded, at least in my household.

 

In my opinion Microsoft has and will continue to fix issues like these ,one of the many reasons win10 insider program is still going on ,and will for many months more ,, your statement has no merit

 

I don't have a Logitech mouse either. For ALL readers, the fix is the fast startup. I did this fix and going on 2 days now with no more problems with the screen saver.

 

Interesting that you mentioned this as I distinctly remember setting the time on the screen saver and I noticed that it wasn't working and reset it yesterday. After viewing this post I re-checked and my screen saver value has been reset to 1 as well but I know that my screen saver was working. I did a bit of investigation and I think that Windows may be reporting it incorrectly on screen. Here's what I found that you can check out on your PC.....

Invoke he registry editor (RegEdit.EXE) and you click on the topmost "Computer" entry
Select Edit from the menu bar, press Find and then enter ScreenSaveTimeOut as the search screen.
Over in the right panel you'll see the value entry and on mine the Data is set to 600 which is 10 minutes.
If the value is not what you expect it to be, you can click on the value entry and change the Value Data to some other, more appropriate value. Not that you should continue to search the registry as on my Windows 10 PC, 600 for the value was found twice. In my case the Control Panel value shows 1 minute however my registry was telling me 10, not 1.

 

on reading this post I set my screen save to 10 min, and when I turned my computer on today I checked and its still on 10min,, I don't use screen saver so I turned it off , I'm using win10 pro insider version ,10532

 

on reading this post I set my screen save to 10 min, and when I turned my computer on today I checked and its still on 10min,, I don't use screen saver so I turned it off , I'm using win10 pro insider version ,10532,and I have a Logitech k360 wireless keyboard and mouse

 

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".