System Firmware Update - 12/10/13 fails to install

Anonymous
2013-12-10T19:14:53+00:00

Got the updates on todays patch Tuesday, but the firmware update failed to load.  Rechecking for an update does not give the opportunity to try and reinstall.

Anyone else having this problem?  I do notice that my telemetry driver is now loaded. so not sure what is going on here.

Surface | Surface Pro | Install and update

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 No comments
Answer accepted by question author
Anonymous
2013-12-19T06:53:02+00:00

Josh,

We are working through the holidays to deliver a fix for the small number of customers that have experience decreased battery life and booting/sleeping problems as a result of the December update.  We took the update down to prevent additional customers from ending up in this state. All hardware failures, none of which are known to be caused by the December update, are being handled promptly through our warranty exchange policy.

The UEFI firmware that we released in the December update prevents some devices from entering sleep mode (and other low power states) properly during periods of inactivity. In order to release an updated version of the UEFI firmware we need to test the new version with the other drivers in the set to make sure we are not releasing yet another unknown state to customer machines. We certainly feel your pain and assure you that we are doing everything possible to make this right, as quickly as we can.

Thank you,

Tim

Was this answer helpful?

7 people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2014-02-15T00:49:31+00:00

Greetings all,

We understand that the February Firmware Update has fixed the Battery gauge issue and the Firmware showing as failed. However we can see that there are some customers who are still experiencing issues with their Surface Pro 2 going into Sleep mode and Hibernate.

So we can better track those particular issues, we have decided to close this thread off. We encourage you to create a thread related to your Surface Pro 2 not going to sleep or not going into Hibernate. Please give as much detail as possible to your scenario.

We understand that the February Firmware update did not resolve the issue with waking from Sleep or Hibernate, as it was not intended to fix that particular issue. We are continuing to work to deliver a high quality solution. More updates will become available as this effort progresses.

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2014-02-13T22:35:08+00:00

The February update has resolved all issues for me.  The firmware installed with no issues.  Prior to this, I had all sorts of problems with the December firmware.  Sleep and hibernate issues were rampant.  The January update helped a bit, but the battery meter was always getting off calibration. 

With the February update, all issues have been resolved and my Surface 2 128gb is working as it was prior to the December updates.  Very solid and all is back to normal.

Was this answer helpful?

0 comments No comments

997 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-01-29T12:47:35+00:00

    after all firmware updates applied:

    after reset (power up + volume up hold x seconds until surface logo flash twice)

    4% loss. Before the December update, this machine was reporting no loss. I'm convinced the firmware update in December permanently damaged people's batteries. I'm not sure how users can organize around here to have MSFT own up to this and replace people's surfaces. I think the only way will be for NEW surface owners to watch their batteries and if after 10-20 cycles they haven't lost 4%, it would indicate MSFT basically damaged our new hardware....

    That or there is a bug in the tools they have provided and the perceived losses aren't correct. I'd hate to think my device was damaged by a firmware upgrade. But I do vividly recall wild variations on battery behavior just after the update. I suspect the December firmware may have caused over-charging based on reports of overheated devices, and I myself experienced one such incident, or a month of under-charging finally took its toll. I almost feel tempted to buy another surface just to confirm, was it not for the fact I may never buy a surface again after this experience... 

    I had a tech help me yesterday to reset my battery. My battery life seems to be better.

    No guarantees but worth a try:

    Make sure to Plug your surface in-must be running on ac power

    Open device manager and locate batteries

    Click on Microsoft ACPI-compliant control method battery

    Right click and select uninstall

    restart the surface

    This is supposed to mimic installation of a new battery to the surface firmware

    Did any of your battery statistics (like wear, etc.) change in a positive manner?

    Yes.  my battery went from showing a wear level of 3% to 1% and I have been using my surface for about 4 hours today on battery only and still have 68% showing on the battery level indicator

    I have done the complete drain of my battery to 0% because I noticed some sudden drops on battery meter when it comes to 50% and below. It could suddenly drop from 43% to 40% in just 10 s. So this was just to recalibrate the battery. After a complete charge to 100% I uninstalled the Microsoft ACPI-compliant control method battery and restarted my SP2 with AC-Power. I haven't noticed any changes after this procedure. Battery wear is still 4.5% after 21 cycles and my battery life is 6 hours normal use and it can still drop suddenly 3-4% in just 10 s at some point under 50% battery charge. I assume this is not normal. Does it require additional complete drain of battery before it recalibrates correctly? It feels like it can get additional 1-1,5 hour because the discharge is much faster below 50% battery charge... is my battery defect?

    Was this answer helpful?

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more