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-13T10:56:25+00:00

My answers:

Updates al ok

No sleep or hibernate problems so far in the combinations I've tried (closing cover, pushing button, leaving the unit alone)

Battery metre showing seemingly correct numbers

Just to clarify: I had all of those problems before the Feb update
Was this answer helpful?

0 comments No comments
Anonymous

2014-02-13T11:36:22+00:00
Dear Steven_B,

I can't afford the luxury to be on-board another leaking vessel for another month. The failed Dec update was fun while I had the spare time, and we learned a lot about our SP2 in that time frame, others may disagree nor be so convenienced. I know I went from someone who loved my SP2 to not being able to trust it. Could you please give the reasons as to why the lab-rating phases falls to us users? An insight into how the Microsoft smart update works perhaps would help us understand why these problems occur. I'm only suggesting a speculation here. Personally however, I would love to hear about the Jurassic high CPU when boot with microSD card inserted.

It is unfortunate so many of us have had issues with the device after December. Since my replacement my device is working fine, but I am not installing this February update for at least another week due to a lack of trust.

Might I ask what type of microSD card you have installed? I have never seen this high CPU problem when booting from a microSD card. At least I was never able to reproduce or verify it. My first Surface Pro 2 did have a lot of the symptoms of waking up on its own and getting very warm, and unreliable battery meter, but I never saw the high CPU. My current new device has no issues.

Dear TBone,

I have 3 x Surface Pro 2s and am using a SanDisk Ultra 64Gb MicroSD cards.

All of my 3 units displayed exact same signs of the problem.

These are as follows...
1. Cold-booting a BRAND-NEW out of the box SP2 with the MicroSD card inserted and leaving the unit idle for 30sec, Task Manager opened showing CPU usage sorted view. Hogging the CPU is the Client Server Runtime (csrss.exe). The 40%-60% csrss.exe lags the system to the point where starting applications are a pain and scroll or swipes gestures at the Start Screen are no longer smooth.
Solution: Put the unit to sleep and wake it back up to temporary rid the problem.
1. Once updated to October Firmware and above... Cold-booting SP2 with the MicroSD card inserted and leaving the unit idle for 30sec, Task Manager opened showing CPU usage sorted view. Hogging the CPU are System (ntoskrnl.exe) & System Interrupts. The 30% ntoskrnl.exe does not visibly lag the system, but battery hungry enough to ruin your day, every day.
Solution: Put the unit to sleep and wake it back up to temporary rid the problem.

A Jurassic issue cross-threaders can read all about HERE... something which plagued all of my 3 x SP2 units, Tried updating the SD-SLOT driver in the Device Manager but there isn't one. You can try updating the SD-Card driver after you insert it, but the best driver has already been applied. Hope I make sense.

PMR.
Was this answer helpful?

0 comments No comments