Share via

Surface Pro doesn't wake up from Standby

Anonymous
2013-02-13T22:14:56+00:00

When I put my Surface Pro into sleep mode (not hibernate, as I disabled that using powercfg -h off  via command line), pressing the power button, Windows button, or pressing keys on the keyboard will NOT wake it up... the screen stays blank, although I can press the Windows key and feel it vibrate as to acknowledge that I've pressed it.

My only solution is to power off the device and then power on, which is not ideal for obvious reasons.

I have not made any changes to power profiles or the device, and I've spent quite a bit of time installing my software and copying files... I really don't want to reset it if I don't have to. I have already installed all available Windows updates.

Any advice?

Surface | Surface Pro | Install and update

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

Answer accepted by question author

Anonymous
2013-03-21T15:28:19+00:00

This from that other thread I referenced appears to have resolved the issue:

  1. Open Device Manager from the Control Panel or however you normally open it
  2. Expand Network Adapters and double click Marvell Avastar 350N
  3. Choose the Power Management tab and make sure the checkbox is checked for Allow the computer to turn off this device to save power

Thanks all!

Leo

Was this answer helpful?

4 people found this answer helpful.
0 comments

Answer accepted by question author

Anonymous
2013-02-14T14:17:29+00:00

Have you altered the wireless network card in Device Manager to not allow the computer to put the device to sleep to save power via the Power Management tab on the card? I had inadvertently done this and it caused my Surface Pro to not wake properly.

To clarify for anyone else running into this:

  1. Open Device Manager from the Control Panel or however you normally open it
  2. Expand Network Adapters and double click Marvell Avastar 350N
  3. Choose the Power Management tab and make sure the checkbox is checked for Allow the computer to turn off this device to save power

Was this answer helpful?

0 comments

64 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2013-03-18T00:55:34+00:00

    I have the 128GB Pro. All up to date as of moments ago.

    The problem is simple: let the device go into sleep/standby. It won't wake up. I can feel a vibrate when I push the Windows button, but that's it. I'm forced to do a hard reboot by holding the power button down for 10 sec to regain access to my machine.

    I have had it work, but it seems to have once again broken.

    Any clues as to what's causing this and what I can do to work around it? Sleep is VERY important to me being able to use this device.

    Thanks,

    Leo

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2013-02-14T12:23:27+00:00

    I have exactly the same issue.

    I picked mine up Saturday morning and have been trying to figure it out since.

    Be careful when it is in this mode too. I believed mine was actually in sleep mode, and put it in my backpack. I pulled it out an hour later, the fan was running and the thing was hot enough to fry an egg on.

    I went through MS surface online support. They gave me the sequence to perform what is essentially a battery disconnect and the issue seemed to be resolved. The surface performed normally, sleeping when the button is pushed or the cover is closed and recovering as it should. The  only problem is, this lasted for 30 minutes and since it's been back to the same behavior.

    I will do some tweaking today to see if there is something I can maybe change in the advanced power options.

    I'll post anything here I find.

    Cheers

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-02-14T04:40:18+00:00

    Hello GoodThings2Life,

    I would go back to the command line and re-enable powercfg -h. See whether that resolves the issue.

    Was this answer helpful?

    0 comments