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)
I have a Surface Pro that is a little over 2 years old. About two weeks ago, the battery now reports "Plugged in, not charging" and seems stuck at 60%. I say seemed because if I unplug that AC adapter, it dies instantly. It also will die periodically while on the charger. I have two Microsoft AC adapters and neither of them seem to charge my device.
I've tried all the Microsoft suggestions for this state, but none of them made any difference. Is there a way to diagnose if this is a hardware problem, or is this a new artifact from the latest updates? (My device reports it is up to date.) I never had any battery issues before (lucky, I suppose), and I've treated my surface pretty carefully. I'll be more than disappointed if it's crapped out already.
I'll attach a battery report, but I don't think it tells me anything in particular.
Battery report
| COMPUTER NAME | ORION |
|---|---|
| SYSTEM PRODUCT NAME | Microsoft Corporation Surface Pro 3 |
| BIOS | 3.11.1550 06/30/2016 |
| OS BUILD | 14393.693.amd64fre.rs1_release.161220-1747 |
| PLATFORM ROLE | Slate |
| CONNECTED STANDBY | Supported |
| REPORT TIME | 2017-01-22 19:53:16 |
Installed batteries
Information about each currently installed battery
| NAME | X898289 |
|---|---|
| MANUFACTURER | SIMPLO |
| SERIAL NUMBER | 1164122628 |
| CHEMISTRY | LION |
| DESIGN CAPACITY | 42,157 mWh |
| FULL CHARGE CAPACITY | 33,212 mWh |
| CYCLE COUNT | 310 |
Recent usage
Power states over the last 3 days
| 2017-01-20 09:41:00 | Active | AC | 60 % | 19,851 mWh |
|---|---|---|---|---|
| 09:44:00 | Battery changed | AC | - | - |
| 09:44:00 | Suspended | - | - | |
| 09:45:28 | Battery changed | AC | 60 % | 19,851 mWh |
| 09:45:28 | Active | AC | 60 % | 19,851 mWh |
| 09:45:48 | Connected standby | AC | 60 % | 19,851 mWh |
| 09:45:49 | Suspended | 60 % | 19,851 mWh | |
| 09:46:25 | Connected standby | AC | 59 % | 19,494 mWh |
| 09:46:25 | Active | AC | 59 % | 19,494 mWh |
| 2017-01-22 19:38:00 | Suspended | 59 % | 19,494 mWh | |
| 19:38:45 | Active | AC | 59 % | 19,494 mWh |
| 19:50:00 | Report generated | AC | 59 % | 19,494 mWh |
Battery usage
Battery drains over the last 3 days
| - | - | - | - | - |
|---|
Usage history
History of system usage on AC and battery
| 2017-01-14 | - | - | 4:18:11 | - | |
|---|---|---|---|---|---|
| 2017-01-15 | - | - | 23:59:59 | - | |
| 2017-01-16 | - | - | 23:59:59 | - | |
| 2017-01-17 | - | - | 23:59:59 | - | |
| 2017-01-18 | - | - | 23:59:59 | - | |
| 2017-01-19 | - | - | 23:59:59 | - | |
| 2017-01-20 | - | - | 23:57:53 | - | |
| 2017-01-21 | - | - | 23:59:59 | - |
Battery capacity history
Charge capacity history of the system's batteries
| 2017-01-14 | 33,212 mWh | 42,157 mWh |
|---|---|---|
| 2017-01-15 | 33,212 mWh | 42,157 mWh |
| 2017-01-16 | 33,212 mWh | 42,157 mWh |
| 2017-01-17 | 33,212 mWh | 42,157 mWh |
| 2017-01-18 | 33,212 mWh | 42,157 mWh |
| 2017-01-19 | 33,212 mWh | 42,157 mWh |
| 2017-01-20 | 33,212 mWh | 42,157 mWh |
| 2017-01-21 | 33,212 mWh | 42,157 mWh |
Battery life estimates
Battery life estimates based on observed drains
| 2017-01-14 | - | - | - | - | |
|---|---|---|---|---|---|
| 2017-01-15 | - | - | - | - | |
| 2017-01-16 | - | - | - | - | |
| 2017-01-17 | - | - | - | - | |
| 2017-01-18 | - | - | - | - | |
| 2017-01-19 | - | - | - | - | |
| 2017-01-20 | - | - | - | - | |
| 2017-01-21 | - | - | - | - |
Current estimate of battery life based on all observed drains since OS install
| Since OS install | - | - | - | - |
|---|
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.
Split from this thread.
The recent November 2016 Firmware Update also killed my Surface Pro 3(Windows 10). I receive the message "Plugged in, not charging at 66%", and when I remove A/C power the SP3 instantly shuts down. I have also lost any ability to join a Wireless Connection. The Wi-Fi displays that there are no connections available...But there are. I really hope Microsoft soon releases a fix for the SP3, as these issues have made it unusable.
There are plenty of people reporting this same issue. Microsoft has not really
addressed this other than to suggest an out of warranty exchange. It will cost
$29 to speak to support and $450 for the exchange for a refurb (which may
develop the same issues). You can contact support
https://support.microsoft.com/en-us/help/13948/global-customer-service-phone-numbers
to discuss.
Just so you know, I did pay the 30 dollars, they didn't fix it, but they'll refund the money if they cannot. So at least my experience is the only thing you have to lose there is time.
But yeah, the live tech basically runs through all the things MS suggests and then tells you the 450 refurb is the only option left.
Split from this thread.
Just wanted to add another disappointed voice to the crowd. My Surface Pro 3 (with LGC battery) is just over a year old and I, too, am getting the "plugged in, not charging" problem with none of microsoft's "solutions" working.
It is only a month or so after the warranty expired and now it costs 30 dollars to even chat to someone at Microsoft and likely the only answer is a costly refurbished tablet that may very well have the same problem?
I can't believe I've been praising this wonderful little machine to everyone since purchasing it. I am so very disappointed that MS can't properly own up to their situation and push out a fix.
If they don't? Well, like everybody else says... don't buy another Surface.
Just an update for my SP3 w/ LGC battery. Initially My battery read 87% plugged in, not charging. Today it went to 0% plugged in, not charging. No other changes. Pretty exciting stuff.
