System Firmware Update - 12/10/13 fails to install

Anonymous

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.

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

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

0 comments

Answer accepted by question author

Anonymous

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.

0 comments

Answer accepted by question author

Anonymous

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.

0 comments

997 additional answers

Anonymous

2014-01-24T16:04:43+00:00
I perform a similar test. Since the 1st Jan firmware update, this is what I have found:

SP2 (with Dec failed firmware)

- Prior to the Jan firmware and after Dec failed firmware, consistently able to replicate an auto wake problem.

After 1st Jan firmware, immediately observe the auto wake problem fixed.  Has yet to be a problem after several days.

However, since 1st Jan firmware have experienced incorrect battery "Full Charge Capacity" value one time.

- At that same time observed a 2nd Jan firmware update.  Loaded it, but no correction to Full Charge Capacity. Performed up volume + power button reset to reset value.

Have tested about 15 sleep tests, >10 sleep to hibernate. Ok so far. No idea if this has any correlation to 2nd Jan firmware.

Confidence somewhat shaken. Still testing.

SP2 (no Dec failed firmware)

Observed 3 Jan firmware updates over a series of days.

Note, this SP2 has not shown any issues after loading Oct updates. Did not experience Dec update.

1st Jan firmware update appeared to work ok.

After 2nd, had occasional crashes upon wake. It appears the crash is related to hibernation.

After 3rd, tests show it wakes normally from sleep-hibernate.

Still testing. Confidence shaken.
When you say sleep test - how are you putting it to sleep? Are you letting it timeout and go to sleep and then timeout to hibernate or are you initiating the sleep by some method such as from the Charm Settings-Power-Sleep or may be you have configured the close touch cover to initiate a sleep. Also is this on battery or powered?

If I try to make mine sleep by timing out, then the display goes off but it doesn't enter sleep mode (If I specifically put it in sleep mode it works but doesn't timeout to sleep mode) If it is really in sleep mode it won't wake up if you touch the screen other than on the windows icon at the bottom centre.

If yours does timeout to sleep I would be interested to know what setting you are using Thanks

Jon
Was this answer helpful?

0 comments No comments
Anonymous

2014-01-24T15:23:31+00:00
I perform a similar test. Since the 1st Jan firmware update, this is what I have found:

SP2 (with Dec failed firmware)

- Prior to the Jan firmware and after Dec failed firmware, consistently able to replicate an auto wake problem.
- After 1st Jan firmware, immediately observe the auto wake problem fixed. Has yet to be a problem after several days.
- However, since 1st Jan firmware have experienced incorrect battery "Full Charge Capacity" value one time.
- At that same time observed a 2nd Jan firmware update. Loaded it, but no correction to Full Charge Capacity. Performed up volume + power button reset to reset value.
- Have tested about 15 sleep tests, >10 sleep to hibernate. Ok so far. No idea if this has any correlation to 2nd Jan firmware.
- Confidence somewhat shaken. Still testing.
SP2 (no Dec failed firmware)
- Observed 3 Jan firmware updates over a series of days.
- Note, this SP2 has not shown any issues after loading Oct updates. Did not experience Dec update.
- 1st Jan firmware update appeared to work ok.
- After 2nd, had occasional crashes upon wake. It appears the crash is related to hibernation.
- After 3rd, tests show it wakes normally from sleep-hibernate.
- Still testing. Confidence shaken.
Was this answer helpful?

0 comments No comments