Screensaver will not start...

[Hoggorm]

Hi,

I've asked the screensaver to become active after 10 minutes of inactivity on the computer.

For some reason this does not happen. I've tried to disconnect USB services such as wireless mouse, keyboard and joystick without any luck.

The preview of the screensaver will start perfectly and moving the mouse a bit stops it, however in normal use of the computer the screensaver will not start...

I assume it must be a software that stops the screensaver from starting?

Any help would be appreciated.

 

[Slartybart]

This is also an issue for me. I recently connect wirelss mouse and keyboard. but disconnecting/uninstalling them didn't change things. I also have a ext WD HD.

I re-installed Win7 two days ago for this issue and other reasons. I have no malware per Avast, Malwarebytes, and ESET. I should have paid attention and checked if the screen saver problem existed before hooking up the USB devices and running Windows Update, but........ nooooooooo

Now that I know it isn't me, I'll dig deeper and see if any WU went to the USB controllers. I think there were some, but I could be wrong.

I don't have a clue yet, but will watch this thread and post anything I do find. Maybe someone can provide a solution for the issue on your machine and I can try it on mine.

Keep the faith,

Bill
.

 

[Slartybart]

I noticed that my power plan was set to sleep in 10 minutes, same as the screen saver. I don't think that's the problem though.

Set to sleep 15 minutes - left Screen saver at 10 minutes

Note: moving the mouse during preview ends the preview - it's normal behavior.

back in 10

 

[maxie]

I have had the same problem unable to find a solution though think it may be some thing to do with usb 3.

 

[Slartybart]

Sorry... more than 10

Ok, on my machine, I set the screen saver to 1 minute and waited (a long minute is a long time)
Then I safely removed my ext HD and waited
finally, I pulled the transceiver for the wireless mouse and KB and waited
The screen saver kicked in, so I plugged the ext HD back in and - you guessed it, waited
Everything seems ok, so I set the time back to 10 minutes

Thinkng again....
Tried connecting a wireless mobile mouse, reset timeout to 1 minute and waited
Screen saver ok
disconnected mobile mosue, reconnected previous transceiver, used mouse ok
...... no screen saver

This is what I originally thought was the issue here

Note: I do have USB3 ports, but was using same USB2 port for all tests.

I do know, from a previous attempt to solve this, that the MS Wireless desktop 6000 is not supported on Win7. They do supply drivers and WU tells me that I need to update them, but that just makes the mouse & KB useless, so I'm running them without device specific drivers, just the generic HID drivers.

anyway, I think all I need to do is get a new desktop set. I think I'll go with another mfgr.

Good luck, not sure my experience will help you folks.

Bill
.

 

[MourningStar]

try system restore

 

[Hoggorm]

try system restore

I do not think that will solve the problem...

Usually I leave my desktop on, but today I tried a restart and for some reason the screensaver now actually do start after 10 minutes. I've tried to start all programs I can imagine that I'll be using and every time the screensaver starts after 10 minutes.

Now the problem is that this has happened before. When time passes by the screensaver will not activate anymore before I restart (I guess) and that leads me to think there has to be a software controlling this..?

 

[MourningStar]

Usually I leave my desktop on, but today I tried a restart and for some reason the screensaver now actually do start after 10 minutes. I've tried to start all programs I can imagine that I'll be using and every time the screensaver starts after 10 minutes.

Now the problem is that this has happened before. When time passes by the screensaver will not activate anymore before I restart (I guess) and that leads me to think there has to be a software controlling this..?

I have the exact same problem once in a blue moon and a re-boot always cleared it. Also, once in a blue moon, it fixes itself (I gave up long ago on trying to reason with these machines).

try system restore

I do not think that will solve the problem...

It would, because all 'system restores' involve a re-boot.