Battery drain with Unregistered device SE?

Anonymous
2014-04-25T07:48:54+00:00

Hi all, 

Lately I've been noticing a large battery drain (at least by my standards) of ~1-2% per hour during connected standby. Based on what's advertised (7-10 days idle) I'm getting ~4 days at best? I ran the sleep study, battery report and energy report and came up with interesting results. I've also calibrated the battery and have no current pending updates. Any ideas as to why the large battery drain during standby? 

Also sorry in advance for the long post. I'm not sure how to post the full reports on this forum. 

Surface | Other

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

72 answers

Sort by: Most helpful
  1. Anonymous
    2014-06-26T00:03:15+00:00

    Mike,

    I ran the prompt above on my surface 2 a while back and it didn't make any noticible change in my standby time. At this point I've accepted that my standby time will not be advertised and have resorted to turning my surface off whenever I'm not planning on using it for a few hours. Not ideal but it works.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-06-25T12:38:49+00:00

    I have just send mine in for replacement, didn't want to wait.. and just as I had UPS pick it up, a techsupport just called me with a possible solution that you guys might find helpful.. since I wont be able to test it!

    So here you go.. this should remove the Unregistered Device SE, according to the techsuppoerter:

    Step   2: In   the search box, enter  command prompt .
    Step   3: Touch   and hold (or right-click)  Command Prompt to   bring up the context menu. Tap or click<br>Run as administrator .
    Step   4: On   the  User Account Control dialog box, tap or   click <br>Yes .
    Step   5: At   the  Administrator: Command Prompt , enter the following:<br> <br><br>  powercfg -setdcvalueindex SCHEME_CURRENT 19cbb8fa-5279-450e-9fac-8a3d5fedd0c1   12bbebe6-58d6-4636-95bb-3217ef867c1a 3
    Step   6: Then enter  <br><br>  powercfg -setactive scheme_current

    Did this work as suggested?  This fix was originally published to address a network adaptor issue for those who updated from 8.1 Preview to 8.1.  Shouldn't be an issue for anyone who updated from a refreshed device.  And haven't we all at this stage!

    Surface RT only: Battery issue when updating from Windows RT 8.1 Preview

    If you updated Surface RT from Windows RT 8.1 Preview to Windows RT 8.1, you may notice a decrease in battery life. During the update, the wireless adapter power policy isn’t migrated. Instead, the power policy is set to a default value that consumes more power both during use and in the connected standby state.

    See also http://blogs.technet.com/b/richardsmith/archive/2007/11/29/powercfg-useful-if-you-know-the-guids.aspx if you're curious about those GUIDs.

    I'm wondering this as well. Still seeing loads of drain by this unregistered device in the logs, sometimes its as much as 16% a hour. Making my reports showing 30-56h of stby time max.

    Here's some images showing it in action:

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-05-21T15:59:06+00:00

    I have just send mine in for replacement, didn't want to wait.. and just as I had UPS pick it up, a techsupport just called me with a possible solution that you guys might find helpful.. since I wont be able to test it!

    So here you go.. this should remove the Unregistered Device SE, according to the techsuppoerter:

    Step   2: In   the search box, enter  command prompt .
    Step   3: Touch   and hold (or right-click)  Command Prompt to   bring up the context menu. Tap or click<br>Run as administrator .
    Step   4: On   the  User Account Control dialog box, tap or   click <br>Yes .
    Step   5: At   the  Administrator: Command Prompt , enter the following:<br> <br><br>  powercfg -setdcvalueindex SCHEME_CURRENT 19cbb8fa-5279-450e-9fac-8a3d5fedd0c1   12bbebe6-58d6-4636-95bb-3217ef867c1a 3
    Step   6: Then enter  <br><br>  powercfg -setactive scheme_current

    Did this work as suggested?  This fix was originally published to address a network adaptor issue for those who updated from 8.1 Preview to 8.1.  Shouldn't be an issue for anyone who updated from a refreshed device.  And haven't we all at this stage!

    Surface RT only: Battery issue when updating from Windows RT 8.1 Preview

    If you updated Surface RT from Windows RT 8.1 Preview to Windows RT 8.1, you may notice a decrease in battery life. During the update, the wireless adapter power policy isn’t migrated. Instead, the power policy is set to a default value that consumes more power both during use and in the connected standby state.

    See also http://blogs.technet.com/b/richardsmith/archive/2007/11/29/powercfg-useful-if-you-know-the-guids.aspx if you're curious about those GUIDs.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-05-16T13:27:03+00:00

    Scott,

    Try to clean your Surface clean as indicated here.  IF you believe that their might be phantom touches happening, I'll suggest contacting support.

    Keep us posted.

    Cheers,

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-05-16T05:01:59+00:00

    Yesterday I had nine updates, installed and rebooted.

    Last night I shut my device down around 11:00pm, and I opened it up this morning around 7:30am.  At 11:00pm I had about 73% battery, when I woke it up in the AM I noticed I had 33%.  So 40% over 8-9 hours with the cover closed.  I did not get any of the display errors over night.

    In the event viewer I see the device sometimes wakes up due to user input.  I'm not sure if this is due to a Bluetooth mouse I did not shut off or something else.  Sometimes when it wakes up due to user input there is a BITS event immediately after this.

    In my next test I will ensure my Bluetooth mouse is off.

    Was this answer helpful?

    0 comments No comments