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-13T16:49:28+00:00

    You guys all REALLY need to look in your system event logs and look for EVENT ID 41.  This is NEVER a good thing.  It is an unexpected shutdown event when the system crashes usually during sleep or wake or hibernate.

    Those of you thinking your Surface's are working NEED to look at ACTUAL data and stop using your gut.

    EVERY Surface Pro 2 I have worked on has experienced these issues and the end user is just not fully away of them.

    I've searched through my event log and there are no EVENT ID 41.

    Going through the list the only device related ones I've had since installing the February updates are (loosely translated from Swedish):

    Errors:

    MTConfig EVENT ID 1: Failed to configure input method for a multitouch device.

    BTHUSB EVENT ID 17: The local Bluetooth-card did not work in an undefined way and will not be used. The device driver has been inactivated.

    DeviceSetupManager EVENT ID 121: The device driver couldn't be installed, result=0x8024402C for devnode{5494A00A-6AE1-4641-AD07-0DC2FAB88BC}\SURFACETYPECOVER\8&21DD112B&0&10

    Warnings:

    Display EVENT ID 4101: The graphics driver igfx stopped responding and has been reset.

    My Surface Pro 2 has worked fine though, no issues with waking it or using my type cover 2.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-02-13T15:45:36+00:00

    You guys all REALLY need to look in your system event logs and look for EVENT ID 41.  This is NEVER a good thing.  It is an unexpected shutdown event when the system crashes usually during sleep or wake or hibernate.

    Those of you thinking your Surface's are working NEED to look at ACTUAL data and stop using your gut.

    EVERY Surface Pro 2 I have worked on has experienced these issues and the end user is just not fully away of them.

    This is maddening....

    The Feb firmware did not resolve these issues and with the feb firmware my surface no longer goes to sleep at all when closing the lid.  After rollback it does.

    Also those of you that keep saying you can't rollback firmware on a surface are also ill informed.  When you reset a surface pro the firmware absolutely reverts.  Same with the firmware patches.  They CAN be reverted.  Microsoft built this in i would assume to prevent bricking devices by a bad firmware update.

    Instead of just making comments based on your semi knowledge of firmware for other products you should make sure you understand how it actually works on a Surface.   Here is a tip, actually look at the firmware version in device manager and roll it back and see it revert.

    David,

    I'm really not sure anyone is prepared to argue with you about this.  You may indeed be very right about what you're saying.   But, this thread is filling up with people who have achieved resolution with the Updates on Tuesday.  Yet you are still screaming the sky is falling.   Again, you may be right.  But yelling ID 41 doesn't help anything.  The vast majority of people here, do not understand what that means.  You can't argue away they are not of value, because they do not understand what you are saying.  You point them to the Event Viewer and they see red, and freak. 

    Why don't you be more specific about what you want people to look at, and why.  

    For me, I currently have 5 ID 41's.  2 are power down related and 3 are sleep related.  But I have NONE since the update was installed.  According to what you have written, I should be freaking out, but this update was supposed to deal with battery meal and restarts from Sleep problems.  For me, I would call this a success so far, but according to you I should still be freaking out.

    Help us all out by being specific at what you think people should look at, and why...what's the impact.  We're not all system engineers with 20 yrs experience.  Help us understand what you're saying.

    Was this answer helpful?

    0 comments