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 No comments

54 answers

Sort by: Most helpful
  1. Anonymous
    2021-05-29T13:19:43+00:00

    Hello folks,

    I have the same problem, since I got my Thrustmaster T16000M FCS package.

    Disabling Geforce Experience or the overlay did not help. (This seemed to be a problem back in 2018)

    So I went to the Device manager and checked all my devices if they affect the sleep mode. (be careful, do not de-activate mouse AND keyboard ;) )

    I concentrated on the game controller as they seem to be the troublemaker in 99% of the cases (as in mine...)

    Disabling both devices (throttle and stick) makes PC sleep normally.

    Both devices do not have a power management tab and i could not change power settings or wake setting using the command line.

    What is strange in my case:
    If I do a clean re-start of my system sleep mode of the monitor won't work.

    If I then just shortly de-activate and re-activate both the throttle and the stick in the device manager sleep mode will work like a charm again.

    So I do not have to keep my devices plugged out, I just need to have them shortly disabled once.

    So option A) for me is:

    I ordered a switchable USB-port. But to be honest... I will hate fiddling with that thing everytime.

    Option B is:
    I created a small batch-file that de- and re-activates the game devices. If I run this as Admin it works just like my manual workaround.

    I now have to make it run on start-up as Admin and i should be fine for the time being.

    Maybe this also helps for you?!

    Short how-to:
    I opened notepad and typed the following (without the dashes)


    pnputil /disable-device "HID\VID_044F&PID_B10A\6&1D8AD952&0&0000"
    pnputil /disable-device "HID\VID_044F&PID_B687\7&2808F29F&0&0000"
    sleep 1
    pnputil /enable-device "HID\VID_044F&PID_B10A\6&1D8AD952&0&0000"
    pnputil /enable-device "HID\VID_044F&PID_B687\7&2808F29F&0&0000"


    In the " " brackets is the ID for my HID-compliant game controllers. This can be found in the device manager.

    Right click on the device --> Properties --> Details --> Device Instance Path (or similar, translated by me from German "Geräteinstanzpfad")

    If you have mor or less devices causing this problem, then change the code accordingly.

    Save the file as YOURFILENAMEHERE.bat

    Run it by right-clicking and select "Start as Admin" (or similar)

    Hope that I can set it to be started automatically as Admin

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-10-21T14:52:08+00:00

    As a workaround, I tried to get the driver from windows 1909 into 2004. In my case HID-complaint game controller (input.inf). It was not so easy, but after editing inf, generating and singing cat file, I was able to use the win 1909 driver on win 2004.

    And after this operation I have a success - the pc is able to turn off screen when idle.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-06-02T06:06:14+00:00

    And I can "disable" the issue by unplugging the device! This is less work than rolling back and postponing updates.

    However, the issue is not solved by that!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-06-02T06:03:37+00:00

    I know what is causing it already (see above). Rather than rolling back, I want to help that things get "matured".

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-06-05T01:20:07+00:00

    For me ...in gaming , this is ridiculous and useless update . and nothing changed  for gaming performance .

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments