It would be a cool feature to have, but unfortunately it does not appear to be possible; Windows can be configured (via the powercfg
command -- powercfg /?
for more detail) to treat input from a given USB HID device as a reason (or not a reason) to wake from sleep, but not to differentiate between types of input. Writing a program to do that sort of differentiation would be relatively trivial, but by the time the machine can run that program to decide whether or not to wake up, it's already awake, and would instead have to decide whether or not to go back to sleep -- which probably doesn't help.
As a workaround, you might consider simply disabling the mouse as a device that can wake the PC; if you don't have a keyboard on the table next to the mouse, then this may not be a useful option, but it looks to be as close as you're going to get to what you're looking to accomplish. To do so, open a command shell and run
powercfg /devicequery wake_armed
You'll see your mouse device named in the list, possibly along with other devices. To disable wake input from the mouse, do
powercfg /devicedisablewake <name of mouse device>
And if you decide to re-enable it later, do so via
powercfg /deviceenablewake <name of mouse device>
Or you could just switch off the wireless mouse when you're not using it, which as a bonus may make its battery last a little bit longer.
1Check your motherboard BIOS if there is such a possibility, Although I have not seen a lot of cooperative models in this respect. – Hashirama Senju – 2013-02-16T01:32:24.837
Can you name a single motherboard that has such feature? Mine does not and I checked the obvious before I posted this question – Matthias Wolf – 2013-02-16T02:15:51.047
I do not recall which motherboard had that option, it was a long time ago so it's a difficult question. But usually it looks something like this: http://img.tomshardware.com/us/2005/09/22/bios_for_beginners/bios-power.jpg
– Hashirama Senju – 2013-02-16T10:58:23.7831@HashiramaSenju, I do not see how your link points to anything that differentiates between mouse click vs mouse movements to awake a PC from sleep. – Matthias Wolf – 2013-02-16T17:07:46.517
+1 because it would be a cool feature to have. It's really easy to bump a mouse or touchpad accidentally. A click is a bit less likely to be accidental. I suppose you could write your own screensaver and have it respond (or not respond) to whatever events you desire, but unless you're a really good coder, it would have to be started manually by you - not just from the system input being idle or another power management event. – Joe – 2013-02-19T09:45:19.693
@Joe, agree its for a HTPC, the mouse is placed on the coffee table and I do not want the HTPC wake up from sleep each time the wireless mouse is moved by a bit. – Matthias Wolf – 2013-02-19T09:47:09.043
I don't think this will be possible (though I've not looked into it in a while), if I remember correctly most implementations deal with activity from the USB input in question - differentiating requiring more processing. – Jeeva – 2013-02-20T10:56:08.413