System Firmware Update - 12/10/13 fails to install

I have a 256 Gb system, 4200U, lot 1341.  My system sleeps normally after ~10 min and hibernates normally after 1 hour with its Surface Type 2 cover attached.  Haven't tested it any other way.  Haven't tried an SD card in my machine.

Perhaps a paraphrase of Abraham Lincoln's famous quote applies:

You can fix all SP2's some of the time and some SP2's all of the time but you can't fix all SP2's all of the time.

I haven't been offered any update multiple times other than some update back in October or so (can't determine as wiped Windows Update history clean in December following Dylan Tullberg's fix for Dec. Firmware update).  Have had a few failed update installations that were then successful or overridden by subsequent updates but these were all for the English Input Personalization (and might be indicative of Microsoft pushing things out the door before fully ready).

Perhaps Microsoft has a problem with a hardware component in its SP2's and that's the reason for the failed firmware updates and the variability of results after applying the fix?  I was originally going to suggest that's why they started offering the 4300U processor but the fact many folks are just getting 4200U's as replacement devices goes against that idea.

I'm lucky with my SP2 compared to some folks in this forum but I knew I was purchasing a bleeding edge device - that's part of the reason I got it, and knew that the battery was irreplaceable.  Microsoft seems to regard its Microsoft Complete as its battery replacement policy.  But that only lasts you two years and then they'll just replace your device if your battery conks out (and get a refurbished one?).  The business extended service plan is for three years.  When I complained about irreplaceable batteries to a rep in a Windows Store, the rep offered various excuses why it was a good idea but did allow that things might get interesting a few years down the road when a whole bunch of people come back to the Windows Store and find out the batteries in their devices can't be replaced as they can in the Apple Store just across the way (Windows Stores are deliberately being built, where possible, near Apple Stores-they are opposite each other across the mall aisle where I'm at).

Still, love my SP2 as a relatively light, powerful device with a nicely integrated, excellent keyboard that still is detachable plus an active stylus, which I mostly use to point at impossibly small menu items in classic Windows programs on the small screen.  Sometimes I wish the screen was larger even for on-the-go use.  Too much squinting!

Hi Jon, posted a few pages ago I wrote out the basic test which is similar to yours.  I set screen = 1min, sleep = 1min and hibernate = 1min.  On one test, I let the system time out and go into sleep on its own.  Another will be to use the power button (which I have set to sleep).  Admittedly, I don't formally test the "close keyboard" method, but occasionally do so during regular activity.  I will, however, during the 1st two methods, attach or detach the keyboard while in the sleep state as that activity reflects my regular use.  I've been trying to determine if there is a relationship with crashes. 

These tests are mostly done under battery use.  I do pay attention when using power and by observing the scenario of sleep under power, removed from power, allow hibernate.  I am currently not finding problems, but that's not to say that I will. 

To your post, I believe I have observed a similar scenario where it times out on the screen and sufficient time has passed such that you would expect it to sleep, but instead find that it has not.  I haven't been experiencing that scenario now.  I recall that scenario happening pre Jan firmware but I believe my Dec firmware caused greater concern and I may not have recorded it. 

Let me know if the settings mentioned above answer your question and if you find resolution.