New software update currently in the works, engineer says

Sep 23, 2016 07:47 GMT  ·  By

Microsoft has recently released a firmware update for the Surface Pro 3 in order to correct a battery issue that was experienced by a big number of customers, but it turns out that some devices are affected by a similar problem due to a different cause.

According to complaints posted by Surface Pro 3 owners themselves on Microsoft’s support forums, devices featuring LGC batteries are now suffering from fast discharge cycles, while others can’t even recharge the device to full capacity.

Microsoft has finally posted a statement to acknowledge the bug and to confirm that a fix is indeed being worked on as we speak, but for the moment, no information can be provided on when exactly users are supposed to receive it.

“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,” a Microsoft engineer explained.

Right now, it’s very clear that this isn’t a hardware problem, and Microsoft is supposed to correct it with a new firmware update.

Users claim the August 29 update is at fault

Users, on the other hand, claim that their battery issues started after the August 29 software update, so they believe the fix that Microsoft released for models with a Simplo battery actually broke down the ones with LGC units.

“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?” one user asked.

As you can see, the amount of information that Microsoft provides is quite limited, so users’ only option for the time being is to wait until the fix is released.