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: Newest
  1. Anonymous
    2013-12-19T21:30:46+00:00

    What's frustrating is my company, around 500 employees develops and maintains its own software for our CRM, our dialer software, our everything, many many products. When something goes wrong, be it a small release or a wide release, we sit someone in a seat on their ****, and have them fix it.

    This pertains to 4 models of product, the Surface Pro 2 64G, 128G, 256G, and 512G. That isn't a wide range or products that needs to be targeted. They all have IDENTICAL hardware, just larger ssd's. So I really really hope MS is sitting their Devs on their asses in a chair, creating a patch to roll us back to the previous Firmware which, by all accounts was at least working. I cannot imagine, they couldn't do this in a matter of a day or two to come up with an Alpha, test, beta, test, beta 2, then RC that out to us. Even if they don't provide it into the update cycle, release a temp tool to help us out. I mean really, this is frustrating.

    Mario

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-12-19T21:22:02+00:00

    I had issues with the battery not charging at all - it was stuck at 0% not charging all day today after the update was installed yesterday.  Disconnect the power and Surface Pro 2 immediately hibernated maintain my work but would only work with power connected.  Mine seems to be behaving correctly now after running through the following steps.

    1. Download and extract the October Update pack from MS Download
    2. Device Manager - expand the firmware section and double click each of the firmware entries, click the driver tab and roll back the driver
    3. Then I rebooted
    4. Each of the 4 firmware entries I then chose to update the drivers but manually point to the Microsoft folder in the extracted update pack
    5. 3 updated to a newer driver dated between September and November and one remains labelled as Firmware Resource and a driver from June 2006
    6. Rebooted again and saw the problem still remained
    7. Then do a full shutdown using WIN+X > Shutdown or sign out > Shut Down
    8. Left it off for a few minutes with the charger connected and at the next boot my battery reported 100%
    9. Disconnected the power and after 30 minutes the battery meter reported a drop of about 5%
    10. Have used it on and off power throughout the day and the battery meter appears to be behaving correctly reporting charging and discharging at what seem to be normal rates

    I am unsure if the rollback and full shutdown fixed it or if the full shutdown alone simply fixed it.  It isn't rolling back the firmware as I am led to believe it is an update of the physical hardware that cannot be rolled back and also an updated driver the works alongside it from within Windows (the one found in Device Manager) - I may be wrong though so I will be glad to be corrected on that one if anyone knows any differently.

    This is what worked for me today so it is worth a try if Microsoft are not releasing an update to correct the issue before Christmas as seems to be indication from many sources.

    Hope it manages to help some of you out.

    Was this answer helpful?

    0 comments No comments