I have had the battery % changing from 0% not charging to 100% charged for the last 6 months
has not worked without being plugged in to the wall for 14 months now
and when I start it up I still get the attempted firmware update that fails every time
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
I have had the battery % changing from 0% not charging to 100% charged for the last 6 months
has not worked without being plugged in to the wall for 14 months now
and when I start it up I still get the attempted firmware update that fails every time
My Surface Pro 3 brick has slightly changed....
It now only reads 0% not charging for some of the time.
Most of the time it says '100% charged'.
Either way it dies immediately the plug is removed & will not boot without it.
Anyone else found this?
The update list now only includes those for office which is odd.
I did the downloadable catch-up update but this still does not appear on the update list.
Can anyone tell me where to find the version of Firmware I am on?
In case it helps, I currently have a large external battery from Amazon (£100 ish) sellotaped to the kick stand.
Not pretty but better than a wall plug & lasts for ages!
Just like all other SP3 users with LGC battery, I have the same issue and I tried all the probable solutions like install windows 10 update, factory reset(to windows 8.1), reset(in windows 10) but the problem is still remained.
here is my battery report:
Information about each currently installed battery
| NAME | X883815 |
|---|---|
| MANUFACTURER | LGC-LGC |
| SERIAL NUMBER | 1150883844 |
| CHEMISTRY | LION |
| DESIGN CAPACITY | 42,157 mWh |
| FULL CHARGE CAPACITY | 32,300 mWh |
| CYCLE COUNT | 332 |
Recent usage
Power states over the last 3 days
| 2017-03-0205:36:18 | Active | AC | 84 % | 27,064 mWh |
|---|---|---|---|---|
| 05:36:18 | Suspended | 84 % | 27,064 mWh | |
| 05:39:49 | Active | AC | 84 % | 27,064 mWh |
| 10:25:50 | Connected standby | AC | 84 % | 27,071 mWh |
| 10:25:50 | Suspended | 84 % | 27,071 mWh | |
| 12:58:57 | Connected standby | AC | 84 % | 27,079 mWh |
| 12:58:57 | Active | AC | 84 % | 27,079 mWh |
| 13:21:00 | Suspended | 84 % | 27,079 mWh | |
| 13:25:21 | Active | AC | 84 % | 27,086 mWh |
| 14:11:18 | Connected standby | AC | 84 % | 27,086 mWh |
| 14:11:19 | Suspended | 84 % | 27,086 mWh | |
| 14:11:56 | Connected standby | AC | 84 % | 27,094 mWh |
| 14:11:56 | Active | AC | 84 % | 27,094 mWh |
| 16:55:23 | Connected standby | AC | 84 % | 27,094 mWh |
| 16:55:24 | Suspended | 84 % | 27,094 mWh | |
| 16:56:02 | Connected standby | AC | 84 % | 27,109 mWh |
| 16:56:02 | Active | AC | 84 % | 27,109 mWh |
| 22:28:17 | Connected standby | AC | 84 % | 27,109 mWh |
| 2017-03-0301:09:14 | Active | AC | 84 % | 27,117 mWh |
| 01:14:00 | Battery changed | AC | - | - |
| 01:14:00 | Active | AC | - | - |
| 01:21:20 | Battery changed | AC | 84 % | 27,117 mWh |
| 01:21:20 | Active | AC | 84 % | 27,117 mWh |
| 02:09:00 | Battery changed | AC | - | - |
| 02:09:00 | Active | AC | - | - |
| 02:11:00 | Battery changed | AC | 84 % | 27,117 mWh |
| 02:11:00 | Active | AC | 84 % | 27,117 mWh |
| 02:32:00 | Suspended | 84 % | 27,117 mWh | |
| 02:36:14 | Battery changed | AC | 84 % | 27,124 mWh |
| 02:36:14 | Active | AC | 84 % | 27,124 mWh |
| 02:38:00 | Battery changed | AC | - | - |
| 02:38:00 | Active | AC | - | - |
| 02:54:00 | Suspended | - | - | |
| 03:00:03 | Battery changed | AC | 84 % | 27,124 mWh |
| 03:00:03 | Active | AC | 84 % | 27,124 mWh |
| 03:00:03 | Suspended | 84 % | 27,124 mWh | |
| 03:04:57 | Active | AC | 84 % | 27,124 mWh |
| 03:04:57 | Report generated | AC | 84 % | 27,124 mWh |
Battery usage
Battery drains over the last 3 days
| - | - | - | - | - |
|---|
Usage history
History of system usage on AC and battery
| 2017-03-02 | - | - | 14:09:34 | 1:31:43 |
|---|
Battery capacity history
Charge capacity history of the system's batteries
| 2017-03-02 | 32,300 mWh | 42,157 mWh |
|---|
Battery life estimates
Battery life estimates based on observed drains
| 2017-03-02 | - | - | - | - |
|---|
Current estimate of battery life based on all observed drains since OS install
| Since OS install | - | - | - | - |
|---|
Join the party.. most of us have it worse and have no battery.. well the firmware wont find the battery anyway..Time to start fighting back since MS thinks it is a joke to them
Hmm... this seems to be US only. I'm in canada experiencing the same issue. Was one of the earlier ones seeing this issue since August...