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.
return it and repurchase. if you are in the US, go to a physical retail
Microsoft store and exchange it. check which battery it has before you leave the
store. Otherwise you will need to wait and see if/when Microsoft comes up with a
software fix. Greg from MS posted a few days ago that MS is aware of the issue.
No timeline for a fix was provided.
>> I bought surface pro 3 few weeks ago.
Split from this thread.
Got a reply from MS:
'
That’s definitely a different problem from what we saw with the Simplo batteries. I’ll send it back up to the engineering team.
'
I have the same issue. I bought surface pro 3 few weeks ago. It was working fine until I updated to firmware 29/08/2016. Since the update my device would not turn on until I plug in the charger and would turn off immediately after I disconnect charger. Battery was stuck at 70% not charging initially which has decreased to 67% not charging now. I have reset my device twice from recovery drive and from within settings as advised by MS support but still no luck. I knew nothing bout SIMPLO/LGC batteries issue. I just came to know about it after reading this thread. Kindly help me out. I have tried almost all the tips advised in threads online. No luck so far.
Split from this thread.
Hello Everyone,
But I guess particularly Jeremy, BelalK & similar.
I can probably support Greg's assertion that the battery problem does not relate to the updates. My Surface pro 3 (LGC battery) was struck by the 'not charging issue a short while ago. I am currently reviewing the update history and it has repeatedly failed to install (due to the low [laugh] battery charge):
- > System firmware update - 29/08/2016
- > Feature update to windows 10, version 1607
This Surface pro went as far as I can tell straight from the working fine / long battery life to 'not charging'
As soon as it switched to the not charging, even dislodging the power connector caused power down.
There is literally no battery support.
To Microsoft, if you are listening. This is what makes the problem so debilitating. The Surface pro simply cannot be used / trusted due to the now frail nature of the power connector. With a battery it is fantastic / clever / simple. Without a battery it is an intolerable liability. PC's with no battery have to have a power connector with some level of physical resistance to disconnection. With the batteryless pro.... move your kick stand & POW!! ... all gone.
To those old enough to remember it reminds me of the Sinclair ZX81 16k RAM pack - that same stunning immediacy ... POW!! Raise your palms outward now and smile..... All gone :-)
Split from this thread.
I also have a Surface Pro 3 with the LGC Battery. Took it to the Microsoft Store this afternoon and was told that the battery was bad. However, the battery report shows that it should still be able to take nearly the full charge. When plugged in, it now says 47%, not charging; last night it quit completely, then re-booted later. After charging all night, the indicator showed 69% charge (confirmed by the battery report), it did work through the school day today.
Is there a fix in process? Problem seems to have begun after the 8/29 update......
AndyD311, Please update your post with a battery report so that MS can verify to extent of our issue. I would really like to see progress on this issue and the more detail the better. Thanks!
To create a battery report:
Windows Key + X (or right-click on the Windows start Icon)
Select "Command Prompt (Admin)" or press the "A" key.
At the prompt "C:\Windows\system32>" type: cd\ <Enter> (This will change directory to the drive root)
At the prompt "C:" type: cd %USERPROFILE% (Assuming your profile is located on the C drive)
At the prompt type: cd Desktop
At the prompt type: powercfg.exe /BATTERYREPORT
On your desktop you will find a battery report that will open in your default browser. Copy and paste that page into your post.
There is no need to use an elevated command prompt.
Simply use Command Prompt by Windows , and then type
powercfg /batteryreport
Then the report will appear in your user profile folder. The exact location of the file will be outputted in the command window.
