No Screensaver after 10 update

ambimom said:

Tried the gpedit ... didn't work for more than 26 hours....however....

Turning off the fast startup solution (above) worked a charm. My screensaver has been going for 10 days now -- ever since I turned off fast startup.

There was another post regarding gpedit that didn't include the enabling of the Screen Saver Timeout policy. My PC didn't work with that proposed fix but with enabling the second group policy I think mine is working as my time out never changes from 15 minutes and I see my screen saver is working and I still have the fast boot option turned on. I was wondering because you said that you had tried this for 26 hours and I just posted this updated solution today.

Possible Resolution ---

I have been dealing with Screen Saver and Power Saver options since updating to Microsoft Windows 10 Pro. Based on suggestion here and on the RealFlight Simulator Forum, I finally determined that it was my RealFlight Simulator Controller connected to a USB 2.0 Hub that was keeping my computer from entering the screensaver and power saver modes.

So far this has resolved my issues. When I get a chance I am going to plug the controller back in and see if the issue return.

ATN256 said:

Same problem here. Screensaver won't come on and monitor will not go off..

I'm having the same problem. I've followed all the tutorials, adjusted all settings over and over again. Never had the problem until I d/l windows 10. I'm really frustrated over it. The only thing that works is manually putting the computer to sleep.

darthclem said:

I'm still working on getting the screen saver to work on my arcade cabinet, but I figured out the culprit on my desktop, which I will share in the hope that it might help others.

Within Device Manager under Human Interface Devices, there are 3 different entries for my Razer Nostromo. One is called "Nostromo Input Device", then there are two labeled "Razer Nostromo". I disabled the second instance of "Razer Nostromo" and the screen saver started working. I rebooted and the delay time for the screen saver stayed the same as I had set it and the screen saver still worked fine. As a bonus, the Nostromo also still works fine.

Also, I found that I had to disable, rather than uninstall, the trouble maker device. If I uninstall it, it reinstalls after a reboot.

So for those of you who haven't tried disabling devices with Human Interface Devices, it might be worth your time...

This was exactly what I've been looking for. I figured out through process of elimination that it was my Razer Nostromo that was causing my computer to not blank the monitors or go into screensaver, and this fixed it for me. I had to test to see which of the two items I had to disable, but once I got the right one disabled my problem went away (without me having to disconnect my Nostromo every night).

Darthclem,
I don't have Razar Nostromo, but under Human Interface Devices, I have many HID Compliant Consumer Control Device and HID Compliant Vendor Control Device entries that all appear to be the same. Would you suggest disabling all but one? I'm hesitant to do it without some confirmation.
Thanks,
Gemster

gemster said:

I'm having the same problem. I've followed all the tutorials, adjusted all settings over and over again. Never had the problem until I d/l windows 10. I'm really frustrated over it. The only thing that works is manually putting the computer to sleep.

Here is a fix! Go here: Power Options - Add

Download and use the the reg file.

Change the settings here to the number of minutes you want.


Do the same for the screensaver settings.



Now screensavers work!

Looks like this only turns off the monitor which can be done from power settings rather than a fix for faulty programming which causes the screensaver to default to 1 minute and not work. I have a nolockscreen setting in the registry having never seen the point of the lock screen and now just reset the screensaver to 3 minutes via a desktop shortcut every time the one user who has this problem logs on. From other threads there appear to be multiple reasons for screensaver errors which have been around a while so it doesn't look like Microsoft will fix this soon.

I have an xbox controller and had the same problem (screensaver not activating); I didn't have this problem when upgrading from windows 7, the problem only appeared after doing a reset. I discovered by Googling this problem, others were having problems with their xbox one drivers, so I checked on my computer in the device manager (choosing update driver, choose driver) and found that there are two sets of drivers for the controller. One set for windows 10 (version 10.0.10240.16384, which were installed), and older drivers (version 2.1.0.1349). I downgraded to the older original controller drivers, and the screensaver problem went away.

I found after much testing and researching that my Power A mini pro ( replacement xbox360 wired controller ) was the blocker. My official Microsoft wired controller is ok. Using the freeware standby monitor utility, time since last user input sticks at zero if the power a controller is plugged in.