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: Most helpful
  1. Anonymous
    2014-02-12T17:15:58+00:00

    Did you check your update history to make sure the install did not report as failed?

    I am a microsoft systems engineer of over 20 years experience. I know what I am doing.  In fact I helped identify these issues in the first months when nobody from Microsoft would listen.

    My new system purchased on Feb 12th(previously purchased 1 on launch day and had it replaced 3 times but then returned it in early February to protect myself.  The new device was stable until the firmware update was installed last night. The install said successful but my surface pro stopped going to sleep when closing the lid.  I had to use the power button + volume button several times since last night to even get the unit to boot up.

    I did perform a system restore to a system restore point created prior to the updates. This removed the updates and rolled back the firmware update.  NOw my system is functioning fine.

    It doesn't get any clearer than that.

    Check to see that the update even installed for you I've read several reports where it failed.

    Check some of the other forum posts for people reporting issues with this new firmware update.

    If you were talking to me, no, I did not check the History.  I had no real reason to think anything had gone wrong.  I've said it before, the day I can't reliably do an update, is the day I throw the device away and get a different one.  Other than some angst right around install, there was not an indicator that anything was wrong.  I was at work, working, not digging into what Microsoft did or didn't do this time around.  The Update pop up was a surprise to me.  When it installed, there were no issues.  Going back through my Update History now, I do see it failed originally.  But again, I would not have known that, or even been drawn to checking it since I had no indicator I was on the brink of oblivion.

    The device is NOT hot, not running fans.  I see no indicator of excessive CPU usage.  I touch Power, it goes to sleep.  I touch power again, it restores.  I close the lid, it goes to sleep.  I touch the Power, it wakes.  I tried all of that right now while this reply was open.  There was no rebooting. 

    I understand why people go looking for issues.  I understand that others may not see the issues  others look for.  I don't understand how TrevM's device crashes and bluescreens, when mine does not.  Is there a configuration difference between our machines?

    I am a Supportability PM with many many years of experience, just like you.  I understand how to work through these things.  I also know there is a reason why your device does what it does while mine may not.  What is it that is different on my machine that is not, or is exclusive to mine or yours, that produces different results. 

    I have used my Surface devices at work, everyday since day 1.  I have lost 2 days in all that time to Update issues.  I have no backup.  There is no other machine to turn to.  The Surface has had to work for me, or I don't work. It has not failed me.  Why is that?  Why is your Surface reacting in such a way that requires you to send Apocalyptic email?   

    If you can't or are unwilling to check your update history then your add no value here.  Many users have reported installing these firmware updates with no visible failure but if you check the update history you will see the update failed.  Especially since you mentioned that the update was offered to you multiple times I think the update never applied and your system is having issues.   Don't use the force.  Your not a real Jedi.  Look at the logs and use facts and data to create conclusions.

    Seach your system logs for EVENT ID 41.  These are unexpected shutdowns.  I bet you don't even realize your system is crashing...  In every case of someone I have worked with who thinks it is operating perfectly they just aren't experienced enough to realize the system is crashing because the solid state drive is so fast and it boots up quickly.

    PS, the hardware is identical in these units.  This is a software issue in most cases.  Microsoft couldn't even be bothered to put a functional recovery image on these devices.  When you do a full reset the surface cover telemetry driver does not reinstall properly.  That issue has been ongoing since launch.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-02-12T16:50:19+00:00

    Did you check your update history to make sure the install did not report as failed?

    I am a microsoft systems engineer of over 20 years experience. I know what I am doing.  In fact I helped identify these issues in the first months when nobody from Microsoft would listen.

    My new system purchased on Feb 12th(previously purchased 1 on launch day and had it replaced 3 times but then returned it in early February to protect myself.  The new device was stable until the firmware update was installed last night. The install said successful but my surface pro stopped going to sleep when closing the lid.  I had to use the power button + volume button several times since last night to even get the unit to boot up.

    I did perform a system restore to a system restore point created prior to the updates. This removed the updates and rolled back the firmware update.  NOw my system is functioning fine.

    It doesn't get any clearer than that.

    Check to see that the update even installed for you I've read several reports where it failed.

    Check some of the other forum posts for people reporting issues with this new firmware update.

    If you were talking to me, no, I did not check the History.  I had no real reason to think anything had gone wrong.  I've said it before, the day I can't reliably do an update, is the day I throw the device away and get a different one.  Other than some angst right around install, there was not an indicator that anything was wrong.  I was at work, working, not digging into what Microsoft did or didn't do this time around.  The Update pop up was a surprise to me.  When it installed, there were no issues.  Going back through my Update History now, I do see it failed originally.  But again, I would not have known that, or even been drawn to checking it since I had no indicator I was on the brink of oblivion.

    The device is NOT hot, not running fans.  I see no indicator of excessive CPU usage.  I touch Power, it goes to sleep.  I touch power again, it restores.  I close the lid, it goes to sleep.  I touch the Power, it wakes.  I tried all of that right now while this reply was open.  There was no rebooting. 

    I understand why people go looking for issues.  I understand that others may not see the issues  others look for.  I don't understand how TrevM's device crashes and bluescreens, when mine does not.  Is there a configuration difference between our machines?

    I am a Supportability PM with many many years of experience, just like you.  I understand how to work through these things.  I also know there is a reason why your device does what it does while mine may not.  What is it that is different on my machine that is not, or is exclusive to mine or yours, that produces different results. 

    I have used my Surface devices at work, everyday since day 1.  I have lost 2 days in all that time to Update issues.  I have no backup.  There is no other machine to turn to.  The Surface has had to work for me, or I don't work. It has not failed me.  Why is that?  Why is your Surface reacting in such a way that requires you to send Apocalyptic email?

    Was this answer helpful?

    0 comments No comments