Surface Pro 2017 turning off or hibernating randomly!!!

Anonymous
2017-06-17T13:19:55+00:00

For some reason my new Surface is shutting off randomly. I check the setting and a few other things but it's still randomly turns off without warning. I'm losing some of my school work because of it. Is anyone else having this problem?

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
2017-06-29T00:49:55+00:00

Hey Everyone,

As of 7/14, the fix for this issue has completed testing and is now live, please go update your Surface Pro via Windows Update to get the latest download. You can obtain this fix by checking Settings> Update & security > Windows Update

The Surface Pro Update History page has been updated with the details of this release and the update is also available on the Surface Pro Drivers and Firmware page as part of the MSI installation package available for download.

BryanH [MSFT]

Was this answer helpful?

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

594 additional answers

Sort by: Most helpful
  1. Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
    2017-07-04T15:42:44+00:00

    Microsoft has stated "We are aware of a small group of customers reporting a scenario with their new Surface Pro in which the device inadvertently hibernates. We are investigating this issue."

    Reading between the lines, I interpret this as they could not reproduce this with their in-house new Surface Pro's. (And they have not updated the thread with something like "we were/were not able to reproduce this in our testing.)

    They also say "small group". While there are 200+ me too's in this thread, and 20 pages of posts, the term "small group" may be relative.

    There are a few posts on Reddit:

    https://www.reddit.com/r/Surface/comments/6i292f/suspendpoweroff_at_random_surface_pro_2017_i5/

    https://www.reddit.com/r/Surface/comments/6hxspe/new_surface_pro_2017_randomly_sleeping_windows/

    One trade press mention

    http://www.zdnet.com/article/new-surface-pro-its-prone-to-random-sleep-issues-too-say-some-users/

    So, in my OPINION, based on the fact that it has historically taken Microsoft months and months to identify issues and come out with a fix and since these devices are still eligible for return for full refund, you may want to consider returning for a full refund and repurchasing. If you do that, you get another 30 days of being able to return and repurchase, etc. The reason I say this is that 6 months down the road, Microsoft will exchange for a refurb if they determine it is a hardware issue and the quality of the refurbs has not been consistent.

    Additionally, if it IS a software issue, customers should not need to perform multiple wipe and reimage's and bare metal trouble shooting. These devices should just work properly out of the box.

    I'm not trying to be deliberately negative, but the track record Microsoft has of fixing issues is slow. You've all spent a lot of money. Sure it costs in time to set up a new Surface, but if the advice is to wipe and reload a device that has this issue, in MY opinion, it's best to spend the time doing this with a different, new Surface Pro in case it is a hardware issue.

    Again, this is my opinion. (MVP's and Community Moderators are unpaid volunteers).

    >>Do we need to report a warranty issue in case this problem can't be solved?

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2017-07-05T17:43:05+00:00

    My new suface pro also goes to sleep in the middle of activity.  I have noticed that it happens when I use a mouse, either Bluetooth or USB.  If I use the touch pad instead, it no longer seem to turn off at random.   Try it!

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2017-07-02T20:06:07+00:00

    I chatted to Surface support this afternoon. They're sending a replacement unit as he thought it's a hardware issue. I'm not convinced, but I'll wait to see if the replacement has the same problem.

    I'll post again once I know :)

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2017-06-23T00:35:36+00:00

    I've had 3 of these TODAY! All within about 10 minutes of each other.

    Log Name:      System

    Source:        Microsoft-Windows-DistributedCOM

    Date:          22-Jun-17 20:30:03

    Event ID:      10016

    Task Category: None

    Level:         Error

    Keywords:      Classic

    User:          SYSTEM

    Computer:      Allen-SP5

    Description:

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 

    {D63B10C5-BB46-4990-A94F-E40B9D520160}

     and APPID 

    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}

     to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

        <EventID Qualifiers="0">10016</EventID>

        <Version>0</Version>

        <Level>2</Level>

        <Task>0</Task>

        <Opcode>0</Opcode>

        <Keywords>0x8080000000000000</Keywords>

        <TimeCreated SystemTime="2017-06-23T00:30:03.259038700Z" />

        <EventRecordID>2074</EventRecordID>

        <Correlation />

        <Execution ProcessID="1016" ThreadID="8272" />

        <Channel>System</Channel>

        <Computer>Allen-SP5</Computer>

        <Security UserID="S-1-5-18" />

      </System>

      <EventData>

        <Data Name="param1">application-specific</Data>

        <Data Name="param2">Local</Data>

        <Data Name="param3">Activation</Data>

        <Data Name="param4">{D63B10C5-BB46-4990-A94F-E40B9D520160}</Data>

        <Data Name="param5">{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}</Data>

        <Data Name="param6">NT AUTHORITY</Data>

        <Data Name="param7">SYSTEM</Data>

        <Data Name="param8">S-1-5-18</Data>

        <Data Name="param9">LocalHost (Using LRPC)</Data>

        <Data Name="param10">Unavailable</Data>

        <Data Name="param11">Unavailable</Data>

      </EventData>

    </Event>

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments