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-02-13T10:30:29+00:00

    Greetings,

    Just to confirm, it is not possible to roll back firmware. I've seen posts that say the Battery meter issue is fixed, and posts that say it is not. Please ensure that you have installed all Windows Updates, and checked again if you are not sure, to ensure that all updates are installed.

    I have not see any posts around Firmware showing as failed in Windows Update, which is what this thread was originally about.

    I have seen a few posts that the Surface now Sleeps or enters Hibernate correctly, and some that are saying it is not happening.

    So I can correctly pass information back to the appropriate teams, I need a direct, Yes these (above) are working now, or No they are not.

    I think it's dangerous just to deal in Yes/No answers.  For the failed 12/10/13 firmware update, some nuances were obviously overlooked and it will be more of the same if the details get lost again.  The devil is in the details.

    Since MS just wants Yes/No, here's my Yes, No.  YES the 2/11/14 firmware is listed as successfully installed and all updates since 12/11/13 have been successfully installed (Windows Update History eradicated before then to recover from 12/10/13 firmware update failure)..  And NO (since we only deal in Yes and No), the "successful" firmware update did not solve all my Sleep/Shutdown problems.

    Since the 2/11/14 firmware update, I've had THREE Event 41 system crashes.  One when my system was set to sleep.  Two when the system was shutdown and crashed on reboot and had to be manually shutdown, triggering the Event 41's.

    Yes - my battery stats appear correct and have always been correct since I got my SP2 10/22/13 except for one instance pre-2/11/14 firmware where a critical battery action level shutdown triggered a continuous 5% battery charge report even on AC until Volume Up/Power Button were held together (reboot did not fix).

    The problem is most of the time everything is working great but even after the 2/11/14 firmware update, my SP2 can be flaky who knows when, e.g., the three Event 41 crashes.

    Illustrated by some "statistics" I did just to see what happens in a short series of repetitive trials (one after the other).  Tested Sleep, Hibernation, Shutdown, and cover removal/reattachment while system on.  System sleeping, hibernating,  or shutdown for > 1 min each time before reawakening.

    10/10 times system went to sleep/woke up successfully by closing Type 2 Cover.

    10/10 times system went to sleep/woke up successfully by Settings Charm, Power Button

    10/10 times system hibernated/woke up successfully by closing Type 2 Cover with close action changed to hibernate

    Only 9 of 10 times did system successfully shutdown and properly reboot.  1 of 10 times on awakening with the Power button, after the Surface logo, the screen went dark, showed only a mouse cursor, and the system had to be manual shutdown (triggering an Event 41).

    10 of 10 times the Type 2 Cover could be removed and replaced while on the Start Screen or classic desktop (in the past I've had occasional crashes causing a reboot while removing or reattaching my Type 2 cover while the SP2 was on)

    So if we're only allowed Yes/No answers, I'd say No, the 2/11/14 firmware is not a complete fix as I've still had issues with Sleeping and Shutdown even though they rarely occur (1 Sleep issue, 1 Shutdown issue since 2/11/14 outside my repetitive trial run in addition to the one shutdown flakeout within the trials).

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-02-13T05:15:33+00:00

    Greetings,

    Just to confirm, it is not possible to roll back firmware. I've seen posts that say the Battery meter issue is fixed, and posts that say it is not. Please ensure that you have installed all Windows Updates, and checked again if you are not sure, to ensure that all updates are installed.

    I have not see any posts around Firmware showing as failed in Windows Update, which is what this thread was originally about.

    I have seen a few posts that the Surface now Sleeps or enters Hibernate correctly, and some that are saying it is not happening.

    So I can correctly pass information back to the appropriate teams, I need a direct, Yes these (above) are working now, or No they are not.

    Yes the battery stats appear correct

    Yes, there are no failed updates, mow

    Yes, I can enter and exit hibernate

    Yes, I can enter and exit sleep

    Yes, I close the lid and enter and exit sleep without a reboot.

    Yes I have 5 event id 41. 2 were from a manual shutdown. Event 41 is the expected message for this.

    3 event 41's were caused by a sleep exiting reboot that I did not know had occurred.  But, none have occurred after the firmware update. I understand a battery meter, AND, sleep fix were part of the firmware rollout. So, I would expect there to be no sleep generated events.

    Look, anyone who has used event logs to help look for problems, knows that's a very slippery slope. Its very easy to scare off the non experienced users by showing them this collection of errors, warnings, etc. Using event logs like was mentioned here just went prove a point we all knew. That is, know it or not, sleep was an issue. Putting a gun in the hands of an expert, they will usually hit their target. Put a gun in the hands of an amateur, they will hit something..most likely not the target.

    I'm glad my scenario's appear resolved. I learned my device had rebooted 3 times without me knowing it, prior to the patch. I also learned that preaching doom is as valueless as preaching successful, without giving it a full try.

    Was this answer helpful?

    0 comments