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-31T23:03:54+00:00

Crash to hibernation associated with opening/closing Type 2 cover reared its ugly head again last night.

Variety is the spice of life. This time the shutdown seemed to occur upon OPENING my Type 2 cover after sleeping because for a tap or two on the Windows screen icon after opening the cover, there would be a vibration, then nothing, and I'd have to restart the SP2.

May have found a way to fix the problem on my SP2. Ran "powercfg /h OFF" - which turns off the ability to hibernate spontaneously. (then closing the cover and opening it seemed to cause a complete Shutdown?!). Then I ran "powercfg /h ON" - which turns hibernation capability back on. I'm pretty ignorant about these things but I believe in the process of this command sequence, the original hibernation file is removed and a brand new one is created in its place. Strangely enough, turning hibernation off, then on, seems to have solved the lid opening problems for now.

Also wondered whether this problem arose because of my 1/29/14 complete discharge where I ran down the device until battery was very low and it shutdown, probably to hibernation since that is the default setting for Critical Battery Action for the Balanced Power Plan. Perhaps the battery was so low, a corrupt hibernation file was created?

May be specious reasoning on my part. Don't know why one would get crashing while sleeping on opening/closing Type 2 cover if there is something wrong with hibernation file/hibernation conditions?? Eager to be better educated by knowledgeable folks..... Also, if a thread on unwanted hibernation already exists somewhere on this forum, someone point me in the right direction.

I reported this bug since day 1. ALways is associated with EVENT ID 41 when waking or going to sleep(usually waking if you check the timing of the logs) when opening or closing or pushing the power button. Of course you loose all unsaved data when this happens and the system reboots. most people don't realize this is happening until you look closely and search your logs for EVENT ID 41. I have had 4 surface pro 2's so this is obviously a software issue still unresolved.

People need to start returning these devices in droves before Microsoft will finally fix some of these deal breaking bugs.
Was this answer helpful?

0 comments No comments
Anonymous

2014-01-31T21:10:58+00:00

Crash to hibernation associated with opening/closing Type 2 cover reared its ugly head again last night.

Variety is the spice of life. This time the shutdown seemed to occur upon OPENING my Type 2 cover after sleeping because for a tap or two on the Windows screen icon after opening the cover, there would be a vibration, then nothing, and I'd have to restart the SP2.

May have found a way to fix the problem on my SP2. Ran "powercfg /h OFF" - which turns off the ability to hibernate spontaneously. (then closing the cover and opening it seemed to cause a complete Shutdown?!). Then I ran "powercfg /h ON" - which turns hibernation capability back on. I'm pretty ignorant about these things but I believe in the process of this command sequence, the original hibernation file is removed and a brand new one is created in its place. Strangely enough, turning hibernation off, then on, seems to have solved the lid opening problems for now.

Also wondered whether this problem arose because of my 1/29/14 complete discharge where I ran down the device until battery was very low and it shutdown, probably to hibernation since that is the default setting for Critical Battery Action for the Balanced Power Plan. Perhaps the battery was so low, a corrupt hibernation file was created?

May be specious reasoning on my part. Don't know why one would get crashing while sleeping on opening/closing Type 2 cover if there is something wrong with hibernation file/hibernation conditions?? Eager to be better educated by knowledgeable folks..... Also, if a thread on unwanted hibernation already exists somewhere on this forum, someone point me in the right direction.
Was this answer helpful?

0 comments No comments