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
    2013-12-10T20:49:33+00:00

    can somebody who has successfully updated the firmware confirm the new version numbers post update? (in device manager under firmware).

    I have

    firmware resource

    6.3.9600.16384

    surface pro embedded controller firmware

    23.7.50.0

    surface pro system aggregator firmware

    2.3.650.0

    surface pro UEFI

    2.4.250.0

    I'm trying to reproduce the sleep reboot problem but so far no luck. Yet my firmware update shows as "failed" under windows update so I'm not even sure if I did get the update after all. Strange that it doesn't come up under windows update any more...

    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