This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Lately, after I shutdown (full shutdown, not sleep or hibernate) my fully charged Surface Laptop 2 at night, I turn it on in the morning and find that the battery has lost around 25% power overnight! What's going on and how can I fix this?
The laptop is only about 6 months old and the battery seems to be in good health.
I've reported this on the MS Feedback Hub. Please upvote it so that it gains attention: https://aka.ms/AA5w24b
Also be sure to report there as well if you are experiencing this issue.
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.
Please see https://support.microsoft.com/en-us/help/4469839/surface-laptop-2-update-history
This should be available on Windows Update:
October 10 release
The following updates are available for all Surface Laptop 2 devices running Windows 10 April 2018 Update, version 1803 or greater:
| Windows Update History Name | Device Manager Name |
|---|---|
| Surface – Firmware – 145.501.139.0 | Surface System Aggregator– Firmware<br><br><ul><br><li><span>145.501.139.0 helps improve battery life.</span></li></ul> |
You can post as you wish as long as it meets the community code of conduct. I
believe that there are several bugs involved. Hopefully someone from Microsoft
Surface engineering will post something official sooner rather than later to
help clarify things.
Keep posting. Who cares if a moderator disagrees or not. Most of those are volunteers as well and are not "Microsoft". Disagreements are part of the discussion. Sometimes, there are valid arguments with "disagreements" and can bring out something that nobody saw before.
In fact, that is the purpose of having a discussion!
Keep posting.
I don't think we are "off topic" but I also understand that Andrew7783 is concerned: however, it seems to me that we are understanding the reasons for a possible bug and, therefore, I consider the discussion useful. However, if the moderators do not agree, I will not post any more.
You know Andrew7783, it may all sound a bit confusing but you may have started one of the most important threads out there. No matter what generation model of Surface tablet or laptop (even Book) model you have, they all have the exact same power management system. You fix one, you fix all. The only two machines that are different are the Surface Hub and Surface Studio which are A/C powered only.
What may be confusing is the RTM and Windows Insider Builds but this is where the experiment of the builds come in handy. If an experimental firmware update is either built into a build or comes separate in a build and fixes an issue, this is an indicator to Microsoft that they can say "hey, maybe we finally got it" and can test it on an RTM build to see if they get the same result. If it works, then they can release it to those with RTM machines as a firmware update (can also be buried in an Accumulative Update) and fix everybody's problem.
I personally think you started the most important thread on the entire forum because power management has been a thorn in the entire Surface series. This started a discussion and some came up with a 'fix' on their own and got good results but it is actually in Microsoft's court to actually fix the problem.
I have been on my Surface Laptop (1st gen) right now with Build 18990 and had no power drop overnight and also been on battery for over an hour right now and the battery gauge says 87%. I never got a battery life like that before and would have been down in the 60s. This newer firmware update (which was included within the build), seems to be doing the trick.
Good job on you to start this thread! A real good discussion is coming out on this.
