Microsoft Surface Pro refusing to wake up from sleep mode due to power setting

surfacecebit_0 Microsoft Surface Pro refusing to wake up from sleep mode due to power setting

For those of you who own a Microsoft Surface Pro, another issue has been going around regarding the device not being able to wake up after it enters sleep mode. Fortunately, the fix is pretty easy and involves making a minor adjustment to your power settings.

“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,” a Surface owner stated on the official Microsoft support forums.

So how do you fix this issue? Simple! Head over to the Device Manager and expand Network Adapters. Double click on Marvell Avastar 350N and select the Power Management tab. Checkmark “Allow the computer to turn off this device to save power.” And there you go, the device will no longer refuse to wake up after entering sleep mode.

The Surface Pro has had its fair share of issues as of late, so its great to see that this sleep mode issue can be fixed quickly and easily without the help of Microsoft. Recently, we learned that the WiFi connectivity issue was still present on the Surface Pro after applying the March 2013 firmware update. No word on when that will get fixed.

  • Din Jao

    I never had this problem happen to me, but however I think the wifi problem applys to me when I am at school, but then again, internet at our school is really shitty, the chances are everyone at the school is having the same problem.

  • ctitanic

    The WiFi connectivity issue is proven that is not a Surface issue. It’s present in almost all the Windows 8 devices in one grade or another. At this point many including me believe its a Windows 8 driver issue.

  • NoClipMode

    One guy had this problem and you write an article on it??!

    • BogenDorpher

      actually more than one person has had this issue if you browse the Microsoft Answers forum… the source link only shows the most recent issue.