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-19T03:46:01+00:00

After my failed update, the diagnostic tool reports the following:

https://www.dropbox.com/s/i9bx3kf7gxqxpgl/Screenshot.png

perhaps these updater issues are stopping windows asking for the new update?

That would complicate things... some may not wish to go through this, but perhaps a refresh is required?

Wait wait wait... This just hit me. Those who haven't received the Jan Firmware Fix, before jumping to conclusions and refresh your devices, have you noticed whether your system received any Definition Updates of late? If so then probably your Windows Update routines aren't effected. But if not, I remember during one of my 8 resets, I pulled a Dylan Tullberg's maneuver, a maneuver which wasn't designed to be performed after a reset and the updater completely died. If that's your scenario, reset.

Tried the Update Cleanup. All it did was offer me the 10/24 HW update again. Why doesn't Microsoft just offer a standalone updater.

Oh and some info might be nice, too, MS.
Was this answer helpful?

0 comments No comments
Anonymous

2014-01-19T03:26:59+00:00

Misadventures with firmware updates and "Shutdown /p" command.

I've been using the Admin Command to prevent my Surface RT from going into Connected Standby when "Shutdown" and occasionally mysteriously completely draining my battery. Has worked for many months with no problem and no mysterious battery discharges.

Thought what is good for the Goose would be good for the Gander and tried it on my SP2 after the 1/14/14 Patch Tuesday updates with strange SP2 waking episodes during the following night.

Just got an inkling that "Shutdown /p" could be a dangerously powerful command to best use only when really necessary (In Case of Emergency Break Glass, etc.).

The 1/15/14 Surface RT firmware update offered AGAIN today disappeared from the Windows Update list and I found it had already been installed to begin with on 1/15/14. So didn't' think too much about it and went to shutdown the RT with the good ol' "Shutdown /p" command. To my horror, the "Updating, Do Not Shut Off Your Computer" appeared, probably 'cuz the 1/15/14 firmware had redownloaded and was waiting to be installed.

The "Shutdown /p" cut the legs out from under the process and the RT went off. Guess 'cuz someone said firmware updates are only flashed on the reboot after the Surface logo appears, nothing bad happened. The reinstall of the firmware update was probably killed completely as Windows Update still says it happened 1/15/14, not today 1/18/14.

So something else Microsoft might need to address is that other idiots like me might decide to use "Shutdown /p" when a firmware update is lurking in the background. One would think "Shutdown /p" should do a quick check (flag set??) and not follow through when a firmware update needs to be installed..

For those folks using Hibernate to stop their SP2's , if the firmware update appears in Windows Update, then disappears (because it's downloaded and waiting to be installed), perhaps they should reboot their machines at least once a day just to give firmware a chance to install in case they didn't notice its arrival in Windows Update.
Was this answer helpful?

0 comments No comments