Windows Device Manager can be used to turn off the allowances of turn offs, but it takes a long long time because there are very many devices listed in Device Manager under HUD (human input devices) and USB (dozens of them). It takes me over 20 minutes and in a few weeks I have to do it again because your choices will reset during windows updates. Another way to do it is in a Power Management setting that is supposed to turn them all off. But in my experience, it doesn't work.

This should work and is permanent. You should google around the internet to verify this code. Because using code is dangerous.

1 Right-click the Windows Start Menu button and select Terminal (Admin) or PowerShell (Admin)

2. Copy the following long command:

Set-CimInstance -Query 'SELECT InstanceName FROM MSPower_DeviceEnable WHERE (Enable = True)' -Namespace 'root\WMI' -Property @{Enable = $false}

3. Paste it into the blue/black PowerShell window and press Enter

   The execution completes instantly. When it finishes, it will simply move to a new blank line. No success message will pop up, but the setting will be changed for all your devices instantly. Something went wrong if it does not move to a new blank line. Try again.

   If you reopen Device Manager, you will see that the "Allow the computer to turn off this device" checkboxes have all been unchecked across all of your devices.

This is what I use and is tailored for our hobby for flight sim peripherals, HOTAS/yokes, racing wheels, VR headsets USB disconnects, stuttering, disappearing devices, controller sensitivity changes, intermittent freezes

Open PowerShell as admin, just paste the script:

Get-CimInstance -Namespace root/wmi -ClassName MSPower_DeviceEnable |

Where-Object {

    $_.InstanceName -match 'USB'

} |

ForEach-Object {

    Set-CimInstance $_ -Property @{Enable = $false}

}

And this if you prefer

powercfg /SETACVALUEINDEX SCHEME_CURRENT SUB_USB USBSELECTIVE SUSPEND 0

powercfg /SETDCVALUEINDEX SCHEME_CURRENT SUB_USB USBSELECTIVE SUSPEND 0

powercfg /SETACTIVE SCHEME_CURRENT

Edited May 25May 25 by LRBS

Never had this happen. Are you doing sonneting wrong in your windows settings?

25 minutes ago, Bigmack said:

Never had this happen. Are you doing sonneting wrong in your windows settings?

It’s not the user causing it. It’s Microsoft’s long-standing “power saving” philosophy, pushed heavily since the Gates era, where the system decides on its own which peripherals should be put to sleep by default — and then often resets those settings again after major updates.

Some connected peripherals have well-written drivers, so the problem may go unnoticed. Others don’t, which leads to random disconnects, unstable behavior, changing sensitivities, or devices failing to wake up properly.

For flight simulation and similar hardware-intensive hobbies, this approach is far from ideal.

I believe hardware related stuff is not allowed in this forum group

https://www.avsim.com/forums/topic/567269-please-do-not-post-hardware-topics-in-this-forum/

47 minutes ago, anilcougar said:

I believe hardware related stuff is not allowed in this forum group

https://www.avsim.com/forums/topic/567269-please-do-not-post-hardware-topics-in-this-forum/

Rightly so, we strive to support each other, and this was definitely a mistake. Thank you for taking the time to correct all of us. 

2 hours ago, LRBS said:

It’s not the user causing it. It’s Microsoft’s long-standing “power saving” philosophy, pushed heavily since the Gates era, where the system decides on its own which peripherals should be put to sleep by default — and then often resets those settings again after major updates.

Some connected peripherals have well-written drivers, so the problem may go unnoticed. Others don’t, which leads to random disconnects, unstable behavior, changing sensitivities, or devices failing to wake up properly.

For flight simulation and similar hardware-intensive hobbies, this approach is far from ideal.

I've never lost any of my usb devices connections so far. And believe me I have dozens of them. I leave my system running 24/7.

Edited May 25May 25 by Bigmack

2 hours ago, Bigmack said:

I've never lost any of my usb devices connections so far. And believe me I have dozens of them. I leave my system running 24/7.

Bill, I believe you—no question. However, each system varies: some work flawlessly, while others are so frustrating you'd want to shoot them. 

Thanks OP, saves me having to uncheck all the boxes after a windows update

word not allowed, didnt work

PS C:\Users\miker> Set-CimInstance -Query 'SELECT InstanceName FROM MSPower_DeviceEnable WHERE (Enable = True)' -Namespace 'root\WMI' -Property @{Enable = $false}

Set-CimInstance : Not supported

At line:1 char:1

+ Set-CimInstance -Query 'SELECT InstanceName FROM MSPower_DeviceEnable ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : NotImplemented: (MSPower_DeviceE...OT\NET\0001_0"):CimInstance) [Set-CimInstance], CimEx

ception

+ FullyQualifiedErrorId : HRESULT 0x8004100c,Microsoft.Management.Infrastructure.CimCmdlets.SetCimInstanceCommand

Edited May 26May 26 by miker916

There's no way I'm copying some text from a post into Windows Powershell..... asking for trouble if you make a mistake. Even a rogue space could cause issues.

I just go into Device Manager and set the option off for each device. It takes around 2-3 minutes.

....and personally, it doesn't change this setting when my Windows updates.

Edited May 26May 26 by JYW

Spad next will do it basically automatically also. Realize not everybody has that program or needs it.

1 hour ago, JYW said:

There's no way I'm copying some text from a post into Windows Powershell..... asking for trouble if you make a mistake. Even a rogue space could cause issues.

18 hours ago, LRBS said:

pushed heavily since the Gates era, where the system decides on its own

FS2020 decided to reset many of my settings yesterday. Hmmppphh...

59 minutes ago, The_Flying_Potato said:

FS2020 decided to reset many of my settings yesterday. Hmmppphh...

Yeah, I’m not looking to debate it, but MSFS 2020/2024 has become notorious for these kinds of problems. I don’t experience any of them with Lockheed Martin Prepar3D or X-Plane 12. Unfortunately, a large number of users continue to report persistent issues involving keyboards, flight controls, settings randomly changing, peripherals disconnecting, and other input-related problems. Whatever the root cause may be, this is clearly not an isolated case — it’s an ongoing and well-known issue affecting many customers. Unfortunately, this ASOBO MSFS 2020/2024 is still unfinished software with very fragile, continuous cloud connectivity and synchronization for core functionality such as scenery streaming, authentication, profile syncing, controller profiles, marketplace entitlements, rolling cache, live weather, traffic, etc. 

Edited May 26May 26 by LRBS

Gemini made me two .bat files. One to enable all on Windows startup and one to check it after. Works like a charm as i also has these problems especially when pluggin and plugout for A320 and B737 setup.

Michael Moe

I haven't had this problem in about 6-7 years. I think an older driver for my Saitek pedals would fail to wake up after sleep. That was in P3D days. So far knock on wood it's never happened with the modern driver.