Windows 10 (2004) - Does not sleep with Gamepad

Anonymous
2020-06-02T00:31:12+00:00

Hello,

after upgrading to Windows 10 (2004) my PC dies not go to sleep any more when I plug-in one of my gamepads / controllers. This happens with any of my 4 controllers (all of the same kind).

For the controllers (a USB cable Speedlink SL-650000-BK, XInput / Xbox 360 compatible) the following driver has been installed during the upgrade:

Xbox 360-Controller for Windows (08.12.2019 - 10.0.19041.1)

I do not know which driver has been installed before. Maybe the same? However, with 1909 everything worked perfectly.

I can even narrow down the problem. When the controller is plugged in, GetLastInputInfo (winuser.h) always returns that input has been given some ms ago. So Windows always gets input, but nobody is doing that physically, of course. Therefore, Windows does not sleep.

Windows for home | Windows 10 | Sleep and Power on, off

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

54 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-12-31T19:30:38+00:00

    JR

    JReed49

    Latest version 2004 causes game controllers to prevent PC from sleeping

    Since installing this new version 2004 my PC will no longer enter sleep mode with my controllers plugged into any of the multiple USB ports. If I unplug the controller I have no problem. This problem did not occur until AFTER installing this update, in fact if I uninstall this version 2004 in win.10 the problem goes away. I have looked around and see others are having the same problem. Does anyone have a fix for this problem?

    Still not fixed.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-10-31T21:40:08+00:00

    Yeah, this bug was already present in the past few years ago and they fixes it eventually. With 2004 version they broke it again and here we are waiting again.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-27T21:48:19+00:00

    Yes that I tried first, but I was getting bluescreen on boot with directly replaced sys files.

    I hope they will fix it .. imagine worldwide probably how much more energy is wasted due to this bug :)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-10-27T15:04:42+00:00

    Ok, I see. I did expect that somehow. As said, I am also no INF expert.

    Did you try the "easy way" and replaced these files on disc using the 1909 versions?

    hidusb.sys

    hidclass.sys

    hidparse.sys

    I can imagine that they will be replaced sooner or later as well. However, with a simple script you could revert all the time as well.

    To be honest, I do not expect that Microsoft will ever fix this.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-10-26T17:06:04+00:00

    Actually not :( Later I found out that the driver replacement "fix" only works until next unplug-replug or reboot.

    Here is the inf https://pastebin.com/P4krUtr9 that I did. Based on standard input.inf from windows 1909 using renamed sys files, and put only my device in %HID_DEVICE_SYSTEM_GAME%, This replaces the usual "HID-compliant game controller" with "HID-compliant game controller GGG" in device manager.

    However when I tried to rework it more in order to replace also the related "USB Input Device" it did not work. Devices went to Error 52. I think this could be related because I was creating the .cat file with selfsigned certrificate... I dont know.

    Finally I gave up :( I dont have enough knowledge on inf files and driver development and lost too much time.

    Will wait and hope MS will solve the issue some day...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments