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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-02-14T15:59:15+00:00

    after the feb update I was also getting the Event ID 41,  however,  I turned of hibernate which deleted the hibernate system file,  also,  I set the swap file size to 0,  rebooted then set the swap file back to default, and turned hibernate back on.

    since then I have not had any event id 41 errors.

    I followed your steps and disabled/enabled hibernation and pagefile. It helped for several consecutive resumes from hibernation last night, I was hopeful the streak is sustainable but this morning it came back to "normal" - won't resume :(

    sorry to hear that,  I have not had an event id 41 since I "cleaned" up the files.  the only issue I am still having has to do with the BTHUB and SD Card

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-02-14T15:50:26+00:00

    Yes, I have disabled fast start-up, without success.

    I have found only a trick to avoid HIGH CPU with SDCARD inserted:

    -

    -

    -

    -

    But now there is a new process: "windows audio device graph isolation", that is always active and consumes CPU power (about 2% instead of the previous about 25%). In any case I have not used this trick because I have very important files in my cards and because I think that this is not a final and "real" solution.

    Was this answer helpful?

    0 comments