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.
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.
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 220.127.116.119). 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.
thanks, Moodoggy, I give a try of your method with success , after trying the others one on this forum ...to be precise , i keep the "fast booting" on and i have a Saitek joystick plugged .Thanks a lot for for this help , but i hope a fix from Microsoft because it is a pity to cannot change the time in configuration panel .....
Sorry, go back after few days and reboots , the gepedit "trick" doesn't work any more !!! Finally , i revert back the settings and after trying again others advice , it is my Saitek joystick who seems the problem : plugged , no screen saver , unplugged , screen saver OK .In fact , i deduct that , on this peripheral , Windows detect some sort of activity that block the starting of the screen saver ...For now, it is not a big problem to plug and unplug this gaming device , but only boring to think at that before to play ...
Last edited by acehole; 05 Nov 2015 at 09:47.