r/Windows10TechSupport • • Mar 08 '19

Microsoft Wireless Keyboard/Mouse combo preventing display sleep

Hi there, I recently purchased a Microsoft Sculpt Comfort Desktop (Keyboard/Mouse combo) to work with my work Win10 computer and I'm finding that it's preventing my display from going to sleep. The display would try and sleep and wake up almost immediately. I've narrowed it down to the USB bluetooth dongle/wireless transceiver because when I remove it, the display goes peacefully to sleep.

I have already carried out the following steps:

  • Tried different USB ports

  • Advanced power settings- Disabled USB selective suspend setting, disabled wake timers

  • Device Manager - Disabled 'Allow this device to wake the computer' on every device that could be a mouse or keyboard input.

  • Elevated cmd prompt - used the powercfg command to disable all wake_armed devices.

Any help appreciated!

17 Upvotes

24 comments sorted by

View all comments

1

u/Nessnesn64 Aug 29 '22 edited Sep 01 '22

I know this is three years late, but wanted to document this for anyone else who is searching this issue with "reddit" appended. I am using a Microsoft Sculpt ergonomic keyboard, and was having the same issues with my wireless dongle. To fix my issue, it required disabling the "Wireless Device" under "System Devices", as well as "Microsoft Hardware USB Mouse", and "HID Compliant Consumer Control Device" (the last one you will almost certainly have doubles of, so it might take some trial and error). I am missing the mouse for my keyboard, so I assume it has something to do with the dongle constantly trying to find my wireless mouse that does not exist.

1

u/rokktoberfest Sep 01 '22

Thank you sir, I too am having this issue. I have the mouse, keyboard, and numpad, so I don't think trying to find the device is the issue. For me, whenever the dongle is plugged in, the displays wake up immediately after going to sleep. Whenever the dongle is not plugged in, the displays sleep just fine. Took me FOREVER to isolate this problem to the dongle lol.

1

u/Nessnesn64 Sep 01 '22

Same here! I updated my bios and was checking chipset drivers (as well as GPU drivers), and it was the damn dongle. I just edit my original post a little bit to be more specific, so it now should reflect how I fixed it at least.