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
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
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
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

997 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-01-15T14:16:14+00:00

    Yes, this has happened to me with the October firmware, but not for these particular updates.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-01-15T13:48:58+00:00

    Please have the courtesy to read my most recent question  and advise me on course of action. In the event of not getting any satisfaction from Microsoft I intend to take some action in relation to UK sale of goods legislation.        

    It would indeed be good to get word from Microsoft as to what is going on now that the planned firmware update hasn't shown up.  But it seems that a more effective and faster route to getting this fixed is making clear to Microsoft and the wider public that more than 0.3% of users are affected by these problems.

    For many of us, however, this has been more than a nuisance than anything else, since all we've had to do is minor things, such as avoiding the sleep state and being careful about keyboards and SD cards being engaged.  Those would be a big nuisance in the long run, but are not a deal-breaker in the short run, and while we should make clear that it is a problem, we should not encourage Microsoft to drop the Surface line. 

    With the first round of small tablet about 8 years ago, the first batch of Motion Computing LS800 tablets had overheating issues.  Motion got this solved after a few months, but so much fuss was made that the computer was always considered damaged goods, and small tablets were considered not ready for prime time.

    It would be a shame for the same to occur to Microsoft.   

    I agree it would be a shame.  A shame that Microsoft didn't learn from prior experience and potentially killed (in the public's eye) a nice piece of hardware because of a lack of execution on updates, communications with customers, and a sense of urgency on the fixes.

    Let's face it, they are facing an uphill battle in the mobile/tablet/hybrid department and don't need to be slow to respond to any significant issue if they are serious about competing.

    Microsoft only has themselves to blame.

    All that said, I hope they are at least listening and learning now.

     

    One thing I've noticed on my system -- and I've not seen here -- is that every time I get a Windows Update -- perhaps it is a FW update or a HW update (which I got yesterday but was dated 10/24) -- The Marvell drivers don't seem to load after boot and I have no wi-fi or Bluetooth.  To get it back, I have to disable then re-enable.  It's a bit unnerving, though, as I always wonder if it will come back successfully.

    Has anyone else noticed this?

    Was this answer helpful?

    0 comments