Surface Pro keeps going to sleep every 1-2 minutes of being idle

Anonymous
2013-04-14T03:29:09+00:00

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.

0 comments No comments
Answer accepted by question author
Anonymous
2014-09-12T04:37:53+00:00

go to desktop mode, go to screen saver, if it says blank, 1 minute, change it to none. it fixed mine SP3, Same issue.

Was this answer helpful?

50+ people found this answer helpful.
0 comments No comments

66 additional answers

Sort by: Newest
  1. Anonymous
    2013-05-07T18:15:38+00:00

    We should probably unmark this thread as "answered" as it is clearly not answered.  I do thank everyone for their help thus far, unfortunately a solution has not been found.

    I really hope Microsoft steps in and provides a fix.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-05-03T23:01:46+00:00

    Sorry for the late follow up, been busy with finals over the past week, and didn't want to bother creating a new user account until my Surface Pro was all setup as my old Laptop  and backed up.

    Thank you Bettelkeda! That seems to have fixed it, for now. I too didn't have the "Reset Security Policies" option under user accounts in the classic control panel, and after I had removed all my non-microsoft accounts from the Mail app, the bug still persisted.

    I have my customized power plan (based off the Balanced power plan) set to put the Surface Pro to sleep after 30 minutes when plugged in, and after 15 minutes when on battery. Just tried as Bettelkeda stated then I put my Surface Pro to sleep (to ensure it wasn't just cause it recently booted up), woke it up and it didn't go to sleep after over 15 minutes (while plugged in) :D On battery, I timed it, and it went to sleep right after 15 minutes :)

    Thanks again Bettelkeda AND daov! Really appreciate it! Hopefully Microsoft stops thinking its the users fault, accepts it is 1 of several bugs in Windows 8 and fixes it with a Windows update.

    --EDIT--

    Appears I kinda spoke too early, lol

    After the second sleep cycle following the change in the Group Policy (when it went to sleep at the right time), it appears that the bug has overpowered the power plan again....I rechecked the group policy and the timing is still set to 99999 minutes. So, I double clicked on it, simply clicked the "OK" button, and the computer still went to sleep after ~2 minutes....

    Will create a new user account soon tonight.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-05-03T21:42:08+00:00

    Thank you daov for the gpedit.msc suggestion.  I changed the value to 99999 to prevent logoff completely and set the timer.  It now lasts 15 minutes.  Better than 2, but not acceptable for areas on the floor that require quick access to the device.

    This is with custom power settings set to never and device removed from domain GPO bucket.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-05-03T18:10:24+00:00

    Yes, my surface is added to a domain and using a wireless network within that domain...as far as I know, group policy isnt the culprit

    Was this answer helpful?

    0 comments No comments