Surface Go 3 : Activated Wake On Power Doesn't Work Correctly

Anonymous
2022-06-16T01:00:52+00:00

Problem with Wake on Power going back to sleep 4 Seconds after awakening.

I have a consumer Surface Go 3 with Windows 11 home and I need the "Wake on Power" feature, i.e. the computer should wake from sleep as soon as it is connected to power.

I Installed Wake On Power following this article:
https://docs.microsoft.com/en-us/surface/wake-on-power-for-surfaceHowever the Tablet enters sleep again after around 4 seconds after applying AC power and wake up. An extra Event 506 is seen in the event log. Does anyone have an idea why does this occur and how to suppress it?

According to the Event log:

Event 566, Kernel Power: The system session has transitioned from 48 to 49

<manually pressed power button to initiate sleep>

Event 506, Kernel Power: The system is entering modern standby. Reason: Power Button

Event 566, Kernel Power: The system session has transitioned from 49 to 50 Reason: 20

<applied ac power>

Event 105, Kernel Power: Power source change

Event 507, Kernel Power: The system is exiting modern standby. Reason: AC/DC Display burst supressed

Event 566, Kernel Power: The system session has transitioned from 50 to 51 Reason: 20

<upto here everything is fine, the tablet is awakened by ac, however now immediately an event 506 occurs which sets the tablet back to sleep, why?>

>>> Event 506, Kernel Power: The system is entering modern standby. Reason: AC/DC Display burst supressed (WHY??)

Event 12, UserModePowerService Process C:\Windows\System32\DriverStore\FileRepository\surfaceservicenulldriver.inf_amd64_4a9cda22fed7b1ed\SurfaceService.exe (process ID:4936) reset policy scheme from {381b4222-f694-41f0-9685-ff5bb260df2e} to {381b4222-f694-41f0-9685-ff5bb260

Event 12, UserModePowerService Process C:\Windows\System32\DriverStore\FileRepository\surfaceservicenulldriver.inf_amd64_4a9cda22fed7b1ed\SurfaceService.exe (process ID:4936) reset policy scheme from {381b4222-f694-41f0-9685-ff5bb260df2e} to {381b4222-f694-41f0-9685-ff5bb260df2e}

Surface | Surface Go | Power and battery

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. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} vote

3 answers

Sort by: Most helpful
  1. Anonymous
    2022-06-16T09:18:15+00:00

    I have a consumer Surface Go 3 with Windows 11 home and I need the "Wake on Power" feature, i.e. the computer should wake from sleep as soon as it is connected to power.

    From what I see on Wake on Power for Surface devices - Surface | Microsoft Docs unfortunately only commercial SKU's are supported. Sorry for the bad news.

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-06-19T19:07:13+00:00

    I have a consumer Surface Go 3 with Windows 11 home and I need the "Wake on Power" feature, i.e. the computer should wake from sleep as soon as it is connected to power.

    From what I see on Wake on Power for Surface devices - Surface | Microsoft Docs unfortunately only commercial SKU's are supported. Sorry for the bad news.

    Image

    Thanks for your response.

    Yes I'm aware of this restriction which is mentioned in my linked article, however I decided to try it anyway and the "Event 566, Kernel Power" to wake up the Table is indeed sent. The Tablet reliably wakes from Sleep when attaching power.

    -> So the question remains why the 566 Wake event is immediately followed by a 506 Sleep event.

    -> What is the difference between a Commercial SKU and a Home SKU? Would a upgrade to Windows 11 Pro help?

    0 comments No comments
  3. Anonymous
    2022-06-19T20:43:12+00:00

    I'm guessing that the event is a result of unsupported functions. I don't have any resources to check because Wake on Power is not supported on your device.

    The firmware and UEFI are different in Commercial vs Consumer SKU's. The commercial SKU has a TPM 2.0 chip while the Consumer SKU has TPM in firmware (software). I don't have a list of other possible differences. It is unlikely that upgrading to Pro will help. Sorry.

    1 person found this answer helpful.
    0 comments No comments