Surface Pro 3 LGC Battery Degradation

Anonymous

Split from this thread.

It was suggested that I open a new thread for this issue that I am having.

Since the Win 10 Anniversary update, I was not able to turn on my Surface Pro 3 i7 512GB with LGC LGC Battery without having it plugged in with the power supply or docking (I own a total of Three Surface Pro 3 Docks at home and 2 offices). It always said "82%, Plugged in, Not Charging", and would always instantly turn off once I pulled off the power supply tab.

I had spoke with a Technical Agent online, had my Pro 3 remote accessed, did all the proposed solutions, and even had a call from Bellevue, WA (I live in Hong Kong) before I found out that it was a software issue as stated by Microsoft.

With Auto Update turned on, I was notified that I should restart my Pro 3 this morning while I was on the docking station. I was happy that this issue was going to be resolved, but now I am disappointed that this firmware update did nothing for my Pro 3.

I'm hoping that someone out there has some suggestions.

Thank You.

Attachment

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

301 answers

Anonymous

2016-09-22T19:40:25+00:00

Greg,

First and foremost, thank you Greg for responding with an official recognition of the problem. I hope that you can appreciate from the consumer's end how frustrating the silence was. We all had the same problem, starting at the same time and were basically being told that we were SOL. Again, thanks for the update.

Bilal,

I'm going to agree with you in opposition to Greg's comment. My son was playing Minecraft on my SP3 before bed time on battery. When he shut it down, I had "Updates ready to be installed". I plugged it in and let it go for the night. That was the last time it ran on battery.

So, if Greg is correct, then I think that we are all suffering from one HUGELY annoying and timely coincidence.

Chris
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2016-09-22T19:39:13+00:00

I am not understanding ms stance that the update did not cause the issues we are having. Thousands of people did the updates and now have the problem.
Was this answer helpful?

0 comments No comments
Anonymous

2016-09-22T19:34:58+00:00

Not everyone

I have been reporting this problem since febuary
Was this answer helpful?

0 comments No comments

Anonymous

My LG battery is also showing up signs of degradation after only 30 cycles after the update. The battery wear level is 96.7% which is unacceptable for this very low count. I got my Surface Pro 3 replaced a few months ago with a new one due to heating issues and have not used it much since. Here is the battery report generated today:

Battery report

COMPUTER NAME	DESKTOP-3AKI8FP
SYSTEM PRODUCT NAME	Microsoft Corporation Surface Pro 3
BIOS	3.11.1550 06/30/2016
OS BUILD	14393.187.amd64fre.rs1_release_inmarket.160906-1818
PLATFORM ROLE	Slate
CONNECTED STANDBY	Supported
REPORT TIME	2016-09-2300:44:53

Installed batteries

Information about each currently installed battery

NAME	X883815
MANUFACTURER	LGC-LGC
SERIAL NUMBER	1199448068
CHEMISTRY	LION
DESIGN CAPACITY	42,157 mWh
FULL CHARGE CAPACITY	40,766 mWh
CYCLE COUNT	30

Recent usage

Power states over the last 3 days

2016-09-2001:16:56	Active	AC	20 %	8,254 mWh
01:59:19	Suspended		38 %	15,291 mWh
2016-09-2223:31:36	Active	Battery	41 %	16,667 mWh
23:43:24	Active	AC	32 %	13,064 mWh
23:45:41	Active	Battery	32 %	13,232 mWh
23:45:51	Active	AC	32 %	13,209 mWh
23:56:38	Active	Battery	38 %	15,382 mWh
23:56:43	Active	AC	38 %	15,390 mWh
2016-09-2300:40:26	Suspended		58 %	23,446 mWh
00:40:53	Active	AC	58 %	23,507 mWh
00:42:44	Active	Battery	58 %	23,742 mWh
00:43:02	Active	AC	58 %	23,704 mWh
00:43:02	Report generated	AC	58 %	23,704 mWh

Battery usage

Battery drains over the last 3 days

2016-09-2223:31:36	Active	0:11:48	9 %	3,603 mWh

23:45:41	Active	0:00:09	-	23 mWh

23:56:38	Active	0:00:05	-	-8 mWh

00:42:44	Active	0:00:18	-	38 mWh

Usage history

History of system usage on AC and battery

2016-09-07 - 2016-09-14	1:37:39	0:00:10	0:06:23	-
2016-09-15	-	-	-	-
2016-09-16	-	-	-	-
2016-09-17	-	-	-	-
2016-09-18	-	-	-	-
2016-09-19	-	-	-	-
2016-09-20	0:43:54	-	0:42:22	-
2016-09-21	-	-	-	-
2016-09-22	0:12:02	-	0:16:20	-

Battery capacity history

Charge capacity history of the system's batteries

2016-09-07 - 2016-09-14	40,766 mWh	42,157 mWh
2016-09-15	40,766 mWh	42,157 mWh
2016-09-16	40,766 mWh	42,157 mWh
2016-09-17	40,766 mWh	42,157 mWh
2016-09-18	40,766 mWh	42,157 mWh
2016-09-19	40,766 mWh	42,157 mWh
2016-09-20	40,766 mWh	42,157 mWh
2016-09-21	40,766 mWh	42,157 mWh
2016-09-22	40,766 mWh	42,157 mWh

Battery life estimates

Battery life estimates based on observed drains

2016-09-07 - 2016-09-14	3:53:18	7:32:57<br><br>212 % / 16 h	4:01:16	7:48:24<br><br>205 % / 16 h
2016-09-15	-	-	-	-
2016-09-16	-	-	-	-
2016-09-17	-	-	-	-
2016-09-18	-	-	-	-
2016-09-19	-	-	-	-
2016-09-20	2:35:38	-	2:40:57	-
2016-09-21	-	-	-	-
2016-09-22	2:15:35	-	2:20:12	-

Current estimate of battery life based on all observed drains since OS install

Since OS install	3:14:34	7:32:57<br><br>212 % / 16 h		3:21:12	7:48:24<br><br>205 % / 16 h

0 comments

Anonymous

2016-09-22T19:26:52+00:00

Hello everyone,

We are aware of a battery issue that is affecting a limited number of Surface Pro 3 users. We can confirm that the issue affecting these customers was not caused by the software updates issued on August 29th. Our team is actively looking in to the issue to determine the cause and identify a fix. We will post an update as soon as we have more information to share.

Greg

Thanks Greg for providing the update, but i find it hard to accept that the updates were independent of the issue.

Before the anniversary FW update, my surface was charging and worked fine for the most part. It just can't be a coincidence that a number of user's batteries stopped charging after the updates on the 29th.

If the updates were unrelated, why was everyone here affected by the same issue in the same time frame?
Was this answer helpful?

0 comments No comments