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-02-13T14:53:07+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.
Was this answer helpful?

0 comments No comments
Anonymous

2014-02-13T12:04:57+00:00
I've got my SP2 for a couple of months now and I have only experienced the battery-meter-issue-thingy once. A reboot and it sorted itself out.

Regarding the FW Upgrades etc. the 11.feb 2014 update gave me a "Unknown Device". Pretty much the same as the cover telemetry driver as beeing described above.

Though never (and still don't) have any sleep or hibernation errors.

I'll keep you guys updated sometimes tomorrow as I might figure out some more.

Yashin_AL; Keep me posted!

Did a sfc /scannow and Windows made "some" repairs.

Went for another Windows update, got a whole bunch of .net updates (bundled with some other W8 / 8.1 updates).

Did a reboot, now the telemetry device is working properly (by working, meaning not showing any warning in the Device manager)

I have completey reinstalled windows 8.1 on my SP2.

Unfortunately I have had to perform the procedure 5 times.

In the end I have used the following steps:
1. perform complete reinstallation with new partitions using a previously saved/generated USB recovery pendrive
2. an unknown device is present in Device Manager
3. download the complete January 2014 Surface Pro 2 firmware and driver pack from microsoft website
4. install/update manually one by one the drivers (included video and the unknown device)
5. only now start windows update manually (install, restart, install,.......)
6. In the end I have not installed the optional update microsoft silverlight and the following security update for microsoft silverlight; because after the above-mentioned optional updates I have had during the first 4 reinstallations a strange problem: a) no-stop/endless windows update and b) endless/hang windows shutdown.
During the next days I'll try to install silverlight again (I use it a lot) directly from microsoft download page and not as a windows update. But I'll probably try a full ssd backup beforehand with clonezilla; in order to avoid the pain/time of a new, sixth, complete reinstallation if something will go wrong.

Now the SP2 seems to work well apart from the high CPU issue with microSD card inserted.
Was this answer helpful?

0 comments No comments