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
    2014-01-08T05:02:42+00:00

    Well I have the same problem reported here, mine has gone back to store I got it from to be returned to microsoft NZ for them to look at.

    Was working fine until about the 13th December when the firmware was loaded on, in windows update it said it did not install however after checking the version numbers most of the update went in.

    Mine would turn itself on after using shut down, It would be sitting on my desk and the screen would just turn on. 3 or 4 times it did it in my bag while driving home in hot weather (it's summer in new zealand),  When it did this it would almost cook itself so have no idea if there was any damage inside the unit, Fans were going flat out and hot to the touch on the back and very warm on the front of the unit.

    It would also sometimes not go to sleep and drain the battery in about 6 hours.

    Called the support number for "surface support" and talked to a tech, he told me to do the +vol and power button for 20 seconds, the tech said this should "correct some of the issue" it just made it worst after doing this and now my battery always shows 100% had it running for 3 hours still said 100% until I plugged it in then it dropped to 99% for 1 or 2 minutes then back to 100% (did not do this before talking to tech support).  Tech support said the fix "should" be out in 8 days time but would not confirm this as a hard date.  I asked about it overheating and he said that the system is designed to turn itself off to protect itself.  Yet mine did not turn itself off and would not trust it too as it would turn itself on.

    I am hoping to get a brand new unit as I have no idea what damage has been done to the inside due to the overheating from it turning itself on (after using shut down).

    So at the moment I don't have any computer but still out $1200 while MS looks at it.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-01-08T01:12:38+00:00

    ... well count me out from this update. Given past performance, I'm going to wait at least two weeks. Right now my surface is limping along. crashes, freezes now and then and randomly reboots and turns on. I have had dells, hps and Toshibas that have been more stable than surface...being made by MSFT. how this makes ANY sense is beyond me.

    If Microsoft has any sense they should do the following for the 14 January firmware update:

    1.  Contact a few people on this thread soon before the update goes live.

    2.  Have them try the update.

    3.  Have them post their experiences to this thread.

    The new update is likely to be fine, but I'm sure most of us would rather if someone else tried it first and reported back.  And those who try it first would rather have some hand-holding from Microsoft to make sure they are not dead in the water if the second try at this update is botched.

    Was this answer helpful?

    0 comments No comments