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-17T06:52:34+00:00

I find annoying the email that I just received from Microsoft for a Surface Pro 2 128 GB for $300 off! IE, instead of the $899 which we early-birds paid (not me, I paid even more; I got the 512 GB)... but now it's only $599. Now what does that tell you?

I thought they were oversold out of their Presales which were reserved until June 2014, but sold out by Dec 2013. Now they drop the price of their product $300? Is there something wrong? Or, do they already have the next latest greatest now ready for release? Hmmmm.....

Meanwhile, the Dec 10th firmware glitch is met with mushroom treatment... kept in the dark and fed B.S. (politeness for the board)

Nevermind me... just grumbling.
Was this answer helpful?

0 comments No comments
Anonymous

2014-01-17T06:39:54+00:00
I just received my replacement after 1 week of waiting, after sending mine out. I was told in my conversation it would be a new unit and that it would have the newer version of the processor. What I got was a individually bagged refurb unit with the same original 4200 processor.

Sorry to hear that.

So, new strategy now:

Call in the Support Request (SR) ticket. You might need to run a few worthless tasks on the first try.

Then follow up the SR with another call after nothing changes (because it won't), and then get a warranty exchange set up with the Rep.

Don't mail it in or do an Advanced Exchange.

Tell the rep that you just want to swap at the store. If you don't have a store nearby, this is a good excuse for a trip.

At the store, you can examine their stock of 256's or 128's for Lot #'s that are higher than 1350. 512's are not popular enough to have run through their stock of the old CPU.

Go home with a Lot 1351 or higher. The higher the better.

Before connecting to wifi, turn off auto updates.

Apply all of the updates up to and including the first Oct. 24 firmware update.

Stop applying updates and enjoy!

Optional: monitor these boards for news that firmware updates are again stable, so you can hopefully re-enable auto updates.

Good points. Except I don't agree with you regarding the Oct 24 firmware update. You'd have to do some serious convincing there.
Don't know about everybody else, but I found that:
1. Cold Booting a SP2 factory firmware with an SD-Card inserted meant having "Client Runtime Server" csrss.exe hogging up CPU, lagging battery draining system, and a SP2 hot to touch. A sleep or restart fixes this temporarily :(
2. On the other hand, cold booting an SP2 with Oct 24 Firmware installed (and with SD card inserted) would lead to "System + System Interrupts" running high but not as bad as csrss.exe in point 1. Again a sleep or restart fixes this temporarily :(
Absolutely annoying.
Was this answer helpful?

0 comments No comments