What if a computer is inaccessible via Teamviewer during its sleep cycle?

Jefflevin · 2024-01-08T20:22:13+00:00

There was an error rendering this rich post.

I recently got Wake-on-Lan to work with my Windows 11 PC. Now I can’t seem to access it when it’s in its sleep state – it seems that it’s too deep for Teamviewer to connect. Has anyone ever encountered this and been able to find a way for the PC to sleep while remaining accessible? Windows 11 doesn’t have the same advanced power options as Windows 10, but there’s still the powercfg command with its many options.

This is what I’m dealing with:

The following sleep states are available on this system:

Standby (S0 Low Power Idle) Network Connected

The following sleep states are not available on this system:

Standby (S1)

The system firmware does not support this standby state.

This standby state is disabled when S0 low power idle is supported.

Standby (S2)

The system firmware does not support this standby state.

This standby state is disabled when S0 low power idle is supported.

Standby (S3)

The system firmware does not support this standby state.

This standby state is disabled when S0 low power idle is supported.

Hibernate

The system firmware does not support hibernation.

Unable to retrieve verbose reasons why sleep states are unavailable on this system.

I have the powercfg query results attached. Also the ACPI settings of the BIOS. Can anyone see a way that I can have access to the computer during sleep? Or can anyone conjecture why a machine that can be woken from shutdown can't be woken from sleep? (The wake-up button doesn't even appear when it's asleep, btw.)

[removed per Community Guidelines]

Find more posts tagged with

Accepted answers

Jefflevin

It seems like I've lucked into the answer myself. I deactivated fast startup in my power configuration, and now the sleep issue seems to be gone. I have access to my computer as long as it has AC and an internet connection. The solution was this command:

powercfg -h off

All comments

Jefflevin

Further details: The “Enable ACPI Auto Configuration” setting in the BIOS seems to be the issue. With it enabled, you can always connect to the computer in its sleep state – the icon is blue -- but WOL doesn’t work. With it disabled, WOL works perfectly, but you cannot connect during the sleep cycle – the icon is black. The wake-up button now appears, but it doesn’t do anything.

The sleep cycles are different in the system log. With the ACPI setting enabled, there is no activity between when the system enters sleep state and when it’s woken up. Disabled, there is still some activity before between when the sleep cycle begins and ends, but not as much as there is during a non-sleep span.

Does anyone have a configuration where both kinds of wakeup work? Did you have to do anything special?

Jefflevin

powercfg -h off