Display Turn Off in Power Options Causing USB Disconnection

In both experiments, I got the same result. The monitor turns off in one minute, and after 20 minutes, the USB device disconnects. In both cases, If I wake the monitor before 20 minutes, I get no lon-on screen. After 20 minutes, I do.

That, at least, makes sense. So the loss of USB ports is definitely related to sleep, as one might expect.

In your first post you say

Wake-Up Login Requirement: When I wake up the monitor with a mouse movement, I'm prompted to log back into Windows, as if the system had entered seep mode or logged off.

If your USB hubs/ports are disabled, how is it that your mouse works?

[20th Feb 204 - Event viewer definition renamed & first diagram replaced to suit]

WorkPermit said:

Whenever Windows automatically turns off my display, it seems to inadvertently cause the devices connected to my USB hub to disconnect.

Have you checked whether or not there is a change of power state to S3 Sleep?

You can check transitions between power-sleep states using the built-in utility Event viewer [eventvwr.msc] by setting up an Event viewer, Custom view that lists them.
You can import the Power - S0ix-S3Sleep-Hibernate transitions Custom view I use to monitor transitions between S0 Modern standby [S0ix], S3 Sleep & Hibernate.
This Custom view definition works in both Win10 & Win11 and in both S3 Sleep computers & S0 Modern standby computers.

Here is the [zipped] definition for an Event viewer, Custom view that captures power-sleep state transitions.
Event viewer, Custom view definitions are exported as & hence imported from xml files.
Power - S0ix-S3Sleep-Hibernate transitions.zip
You can unzip it then, before importing it, read the Power - S0ix-S3Sleep-Hibernate transitions.xml file in Notepad or, for a better presentation of its contents, by right-clicking and opening in a browser.

To import it:
1 Unzip the file
2 Open Event viewer, click on Import Custom view [on the right-hand side],
3 Browse to and select the xml file then Open,
4 Change the name if you want to then OK,
5 You can see the records, in Event viewer's left-hand pane, within the group Custom views. It often takes a few seconds to populate the results.
6 Whenever I investigate something using Event viewer, I always write down the time shown by the computer's clock when I see that something happen [before even looking at Event viewer] so I can always be sure what it is that I'm looking at in Event viewer later on. This becomes increasingly important the more test runs are involved in whatever it is that I'm investigating.



Note 1 Distinguishing between resuming from S3 Sleep & Hibernation
When reviewing power state transitions, note that S3 Sleep & Hibernation events can only be distinguished, in a computer that has both, by looking at the Details tab of the resume EventID 1 for Hiber* entries that are greater than 0; resuming from S3 Sleep would show Hiber* entries that have the value 0
Resume from Hibernate, Details tab

Resume from S3 Sleep, Details tab



Note 2 Incorrectly labelled S0 Modern standby events
On a similarly confusing note, S0 Modern standby event records are misleadingly labelled as relating to S0 Connected standby whichever state is in force - Connected/Disconnected standby.
I appreciate that you are working on an S3 Sleep computer at the moment.


Note 3 Sharing Event viewer, Custom view definitions between computers
You can generally export an Event viewer, Custom view definition on one computer and import it on another.
The only exception I know of is that Administrative events Custom view you can see at the top of my first diagram. If I deliberately created a Custom view that included hardware-specific properties then that would also be an exception.
- That Administrative events view definition lists all events so can be useful if I want to see everything in chronological order.
- That Administrative events view definition contains hardware-specific properties that differ between computers. They can also differ if hardware is swapped on a single computer.
- That Administrative events view definition is not filterable. If you try filtering it, the filter options are all greyed out. This really hinders investigations.
When I want to set up a filterable version of it on a new computer and again when I change hardware, I create a filterable version of it by:-
3.1 Deleting any previous filterable version I had created.
3.2 Right-clicking on the Administrative events Custom view then Exporting it.
3.3 Renaming the xml file to something like Administrative events - Filterable.
3.4 Importing the Administrative events - Filterable xml file and using the xml file name as the Custom view name.
That imported version enables Event viewer's Filter Current Custom View control on the right-hand side of its window.
I last changed mine when I changed WiFi adapter and started using a USB LAN adapter at about the same time. I do not know if either of them makes any difference to the results shown in that view but there would have been nothing to warn me of potentially significant events being missing during an investigation if I had not re-created the filterable view.



Best of luck,
Denis

Ah.. that's entirely different... nothing to do with USB devices then.