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-25T10:42:49+00:00

Since the january firmware update my SP2 128 GB goes into sleep and hibernate properly.

My main concern is the battery report:

Full charge/design capacity

http://www.picfront.org/d/94lC

Battery life estimates

http://www.picfront.org/d/94lB

Full charge capacity dropped from 42mWh to 22mWh in one month.

My guess is that's hopefully just a software failure. Anyone else noticed such a dramatic decrease?
Was this answer helpful?

0 comments No comments
Anonymous

2014-01-24T20:13:29+00:00

I have a 256 Gb system, 4200U, lot 1341. My system sleeps normally after ~10 min and hibernates normally after 1 hour with its Surface Type 2 cover attached. Haven't tested it any other way. Haven't tried an SD card in my machine.

Perhaps a paraphrase of Abraham Lincoln's famous quote applies:

You can fix all SP2's some of the time and some SP2's all of the time but you can't fix all SP2's all of the time.

I haven't been offered any update multiple times other than some update back in October or so (can't determine as wiped Windows Update history clean in December following Dylan Tullberg's fix for Dec. Firmware update). Have had a few failed update installations that were then successful or overridden by subsequent updates but these were all for the English Input Personalization (and might be indicative of Microsoft pushing things out the door before fully ready).

Perhaps Microsoft has a problem with a hardware component in its SP2's and that's the reason for the failed firmware updates and the variability of results after applying the fix? I was originally going to suggest that's why they started offering the 4300U processor but the fact many folks are just getting 4200U's as replacement devices goes against that idea.

I'm lucky with my SP2 compared to some folks in this forum but I knew I was purchasing a bleeding edge device - that's part of the reason I got it, and knew that the battery was irreplaceable. Microsoft seems to regard its Microsoft Complete as its battery replacement policy. But that only lasts you two years and then they'll just replace your device if your battery conks out (and get a refurbished one?). The business extended service plan is for three years. When I complained about irreplaceable batteries to a rep in a Windows Store, the rep offered various excuses why it was a good idea but did allow that things might get interesting a few years down the road when a whole bunch of people come back to the Windows Store and find out the batteries in their devices can't be replaced as they can in the Apple Store just across the way (Windows Stores are deliberately being built, where possible, near Apple Stores-they are opposite each other across the mall aisle where I'm at).

Still, love my SP2 as a relatively light, powerful device with a nicely integrated, excellent keyboard that still is detachable plus an active stylus, which I mostly use to point at impossibly small menu items in classic Windows programs on the small screen. Sometimes I wish the screen was larger even for on-the-go use. Too much squinting!
Was this answer helpful?

0 comments No comments