I have a screensaver applied via Group policy. On only one of the machines, it never goes to screensaver. If I look in the display control panel, the timeout is grayed out and set to 8 minutes... so obviously this is not a problem with applying the group policy.\

What could be causing this then? Might it have something to do with the wireless mouse? If not, what else should I look for?

1 Answer 1


There is a delay feature that will increase the timeout period, but if the screensaver is never kicking in, it probably isn't.

It could be a rogue driver/program.

Raymond Chen again:

First of all, there are ways for programs to block the screen saver entirely. Calling SetThreadExecutionState(ES_DISPLAY_REQUIRED), is how a program says, "Even though there is no mouse or keyboard input, the screen is indeed in use, so don't blank it or start the screen saver."

There are a bunch of bug-related reasons in the Microsoft Knowledge Base.

  • Found it in the microsoft knowledgebase. Just in case somebody has this issue in the future the article is support.microsoft.com/kb/911895 . Basically the microsoft wireless mouse was constantly sending signal strength info back to the computer and the computer was considering this as user activity. Installing Microsoft's Intellipoint software for the mouse resolved the issue.
    – Brett
    Aug 24, 2009 at 22:11

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .