go to desktop mode, go to screen saver, if it says blank, 1 minute, change it to none. it fixed mine SP3, Same issue.
Surface Pro keeps going to sleep every 1-2 minutes of being idle
Love the idea behind the Surface Pro, but been having software and hardware issues lately. One of the software issues I've been experiencing is that when my Surface Pro first goes to sleep after a restart and I wake it up, it then begins going into sleep mode every like 1-2 minutes of being idle. I noticed this when reading some news on the internet.
I double checked my power options I have my current power plan (based off Balanced) set to put my Surface Pro to sleep (while plugged in) after 30 minutes of being idle!
Anyone know what's causing this problem? Is this another OS bug in Windows Ei8ht? I've avoided contacting the Surface support team cause every time I've contacted them about technical problems like this, their only solution is to perform a system refresh.
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.
66 additional answers
Sort by: Newest
-
Anonymous
2013-09-09T05:09:34+00:00 Maybe try this - not sure if it will fix it but worth a try.
This is to change system-unattended-sleep-timeout registry setting
Open REGEDIT
GO TO
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\238C9FA8-0AAD-41ED-83F4-97BE242C8F20\7bc4a2f9-d8fc-4469-b07b-33eb785aaca0]
CHANGE
"Attributes"=dword:00000001
Also CHANGE default value to something like 1800 (seconds) so 30 min
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2013-08-27T13:22:06+00:00 反映给微软有这个问题,可恨的客服居然说,我是第一个提出问题的,建议我重装系统。
-
Anonymous
2013-08-26T13:43:33+00:00 That is actually a report lifted from this thread and states specifically that resetting security policy can fix it. And that it is caused by Exchange accounts being synced.