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-14T14:04:06+00:00

after the feb update I was also getting the Event ID 41, however, I turned of hibernate which deleted the hibernate system file, also, I set the swap file size to 0, rebooted then set the swap file back to default, and turned hibernate back on.

since then I have not had any event id 41 errors.

I followed your steps and disabled/enabled hibernation and pagefile. It helped for several consecutive resumes from hibernation last night, I was hopeful the streak is sustainable but this morning it came back to "normal" - won't resume :(
Was this answer helpful?

0 comments No comments
Anonymous

2014-02-14T13:56:28+00:00
--- DAY 1 ---

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:

perform complete reinstallation with new partitions using a previously saved/generated USB recovery pendrive

an unknown device is present in Device Manager

download the complete January 2014 Surface Pro 2 firmware and driver pack from microsoft website

install/update manually one by one the drivers (included video and the unknown device)

only now start windows update manually (install, restart, install,.......)

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.

Now the SP2 seems to work well apart from the high CPU issue with microSD card inserted.

--- DAY 2 ---

I have found a new problem: my SP2 now show "endless-hang windows shutdown" when I use micro SDcards; this new problem is in addition to the high CPU issue with microSD card inserted.

Today I have tested 4 new microSDHC cards of 4 different brands

(two of them 32GB class10 UHS-1) and

(then low speed: 8GB class2 and 8GB class4)

Moreover I have tested and formatted them using different methods, including the formatter software found at sdcard.org

Unfortunately without success with SP2 (no problems with SP1)
It's amazing how different these issues are. The fishy stench of began after the failed December 2013 firmware update where most folks in Australia experienced the issues, where most of those I know in the U.S.did not. And with the lack of explanations from the corporation, I really think Microsoft has a problem with its smart update system propagating dissimilar-to-damaging files to different units in different regions. I'm in NSW Australia and my SP2 boots up high CPU with microSD card inserted, System (ntoskrnl.exe) hogging CPU chewing battery like m&ms. Thus far I'm running the fixed January drivers & firmware and avoiding the Feb versions at all costs. Could all posters tell us their issues along with region when the updates were obtained, Microsoft maybe able to narrow down on the problems. Thank you.

Francesco, regarding your hang-on-shutdowns, have you tried disabling hybrid shutdown? At Start screen, type "choose what the power button do".
Was this answer helpful?

0 comments No comments