For Microsoft, creating the Surface and jumping head-first into PC hardware territory was about solving a problem: the need for a flagship Windows device that could truly compete with the iPad and Nexus Android devices at a design, hype, marketing and performance level.
The Surface RT and Surface PRO might have been introduced as a solution to that problem, but as Microsoft is quickly finding out, getting involved in this hardware game creates new problems as well. Namely, new hardware products are always bound to have some kind of early issue or issues.
For Microsoft’s Xbox it was freezing and blue screen of death. For the 360 it was thd dreaded Red Ring of Death. For the Surface RT and Surface Pro, it has been numerous little issues including Wi-Fi problems and more. Now here is new one to the least- specifically for the Surface Pro: some users are reporting the Pro refuses to wake up.
The problem is put pretty simply by one Pro user:
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.
The poor little tablet just wants some well-deserved rest, right? Jokes aside, this is a real problem and can certainly be frustrating. It becomes even worse when you realize that Microsoft has yet to officially recognize or list this as an issue.
In time Microsoft will likely get this sorted out, and at least the sleep issue doesn’t completely stop you from using the tablet, but it is still annoying. Goods news is that a fix has been found by a Neowin forum member by the username of LeoNot.
To stop yourself from running into the sleep issue with the Pro, go into device manager and network adapters. From there you are supposed to double press on the Marvell Avastar 350N and select power management. From there, check the box that says “Allow the computer to turn off this device to save power”.
That supposedly will do the job and stop the problem from occurring. Have you run into this issue with your Surface Pro, if so did LeoNot’s suggested fix take care of the issue or not? Share your thoughts below.
[ source ]