i5/256 Surface Pro 4 overheats and battery drains while 'sleeping'

Anonymous
2015-11-04T01:55:47+00:00

Split from this thread.

My SP4 gets very hot and drains the battery very fast even though it is asleep. I found it very hot in its sleeve and down to 28% earlier today. Found it dead later in the afternoon. This is one of MANY issues this device has.

(My SP4 is not part of the insider program)

Surface | Surface Pro | Power and battery

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
2016-02-17T23:04:09+00:00

Hi All,

We released an update on 2/17/2016 that addresses this issue.

We recommend that you install this update to keep your Surface performing its best. You can get updates now by checking Settings> Update & security> Windows Update.

To confirm the updates are installed, check Settings> Update & security> Windows Update> Advanced options> View your update history.

Thanks,

Josh

Was this answer helpful?

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

434 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-02-13T18:44:46+00:00

    Well I thought I had a reasonable work around but this is quite frustrating.  I think MSFT isn't getting sufficient negative feedback and they just keep on selling these units with flaws.  I have used hibernate if sleeping more than 2 hours for over a month with no problem.  It seems the heat issue gets worse in sleep over the duration it is in sleep.  So I just have it move to hibernate.  Well waking from hibernate is not such a joy.  Today, it woke from hibernate and Carbonite didn't work, so I had to restart.  Later, the external monitor was not detected, had to restart.  Using an I5 8/256.

    Shutting the unit off is almost the best solution when not using for a while.  And that is not right to have to do for $1500.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-02-12T01:03:31+00:00

    Yeah. I spent hours yesterday on MS support call with the technician just doing standard System file scans, windows update checks and review my power settings.

    They also ran some type of Power Efficiency Diagnostics Report and some remote tools.

    I tried explaining its not just an issue with my SP4 with type covers but all SP4 with type covers.

    I also sent them a link to this post 

    http://answers.microsoft.com/en-us/surface/forum/surfpro4-surfdrivers/battery-drain-when-type-cover-4-is-connected-and/c63eed00-fbc0-4258-ac11-5be8e36f6230

    The phone support techs don't get it. They just have to run through their diagnostic scripts and their procedure.

    How about MS Support actually test it on a device in their support team.

    I provided step by step instructions. They should see if they can reproduce it on their device. Then they could troubleshoot it all they like without having to waste my time. Then get back to me on what the actual problem and when it will be fixed.

    Frustrated!!!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-02-12T00:26:50+00:00

    Who knows whether they are actually working on a fix for this or not. At the moment there are various issues with power management which need sorting, and only the vague 'we're working on it' comment on this forum. That, and the fact that several updates for the devices have come out recently which aren't fixes for it says to me that they are making little progress or simply don't care. It could be days, weeks, months before we see an actual fix.

    You are correct in that the solution for this is to wait for the device to fully power off before closing the cover. It's an odd bug, that's for sure.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-02-11T23:37:30+00:00

    Is there a fix for the battery drain during hibernation or power off bug?

    I discovered others have the issue here

    https://www.reddit.com/r/Surface/comments/3vy4k1/surface\_pro\_4\_battery\_drain\_while\_completely/

    Below are 3 scenario's which demonstrate the issue with the 3rd scenario a work around to the bug.

    How to recreate.

    You need a Surface Pro 4 and the Type Cover.

    Go to your power options and select "Choose what power buttons do"

    Set the following for both on battery and plugged in

    When I press the power button: Hibernate

    When I press the sleep button: Hibernate

    When I close the lid: Hibernate

    Scenario 1

    1. Charge the device to 100%
    2. Unplug the charger.
    3. Make sure the surface is running and logged in.
    4. Close the Type Cover
    5. Leave overnight

    Expectation: The surface pro should go into hibernation and there should be no power drain from the battery

    Result: There was power drained from the battery.

    Scenario 2

    1. Charge the device to 100%
    2. Unplug the charger.
    3. Make sure the surface is running and logged in.
    4. Press the power button and immediately (with in 2 seconds) close the type cover
    5. Leave overnight

    Expectation: The surface pro should go into hibernation and there should be no power drain from the battery

    Result: There was power drained from the battery.

    Scenario 3

    1. Charge the device to 100%
    2. Unplug the charger.
    3. Make sure the surface is running and logged in.
    4. Press the power button and Wait until all illumination from the type cover is off (about 5 to 10 seconds). To test swipe the trackpad or press the brightness on the illumination key(F2). You know the surface has completed hibernation because the keyboard will no longer illuminate.
    5. Leave overnight

    Expectation: The surface pro should go into hibernation and there should be no power drain from the battery

    Result: Success!!! No batter drain. The device is has successfully been put into hibernate with no battery drain.

    Anyone have any idea if this will be fixed or if MS are working on this bug.

    Was this answer helpful?

    0 comments No comments