Surface Pro 3 - Missing Surface Pro Touch Controller Firmware after reimage

That's actually the "funny" thing - the support staff I've "talked" with (either via online chat, phone or email) have all been really nice to work with.  But nice doesn't cut not getting a fix when it is needed - although that is no fault of the support staff I know.  I'm just hoping they come up with the fix soon.  It's just a shame a product like this with so much potential (and plenty of advertising $$ spent if you watch any NFL games at all :)  ) is having so many problems.  

Someone else said they went through several installs before it actually "took."  I may try that as well...what have I got to lose at this point...

yea james its defo a hardware version issue as all the ones that have the issue have the same hardware revision.

I cant say its a hardware fault as yet but when i took mine back i classed it as a hardware fault. I would say its a 50/50 chance of it being a hardware issue due to the time it has taken to try and fix it as to me itst he firmware that wont upload to the hardware part of the pen controller but is this due to incompatability or is it the hardware that is not allowing the flash ?

Lets see how long microsoft take to repair or attempt to repair it.

I don't know if it necessarily applies to lot numbers, but it appears people have found certain hardware IDs for the Surface Pro Touch Controller Firmware are the troublesome ones...

I will say three things:

1. On all of my units, if I just kept trying over and over again to install the firmware, it eventually installed.  On my last one it took probably at least 50 tries.  So you COULD try that and hope you get lucky.
2. Now that there is a knowledgebase article for this, you should reference it with your support rep, either via email or over the phone. I would imagine that will give you much more leverage and that will give them help on their back end to do much more research and narrow down the exact cause of your problem without guessing.  They may have access to more information on their end than we can see on the public site.
3. With the knowledgebase article posted it sounds like there really is a fix in the works and this is a software issue.  If it turns out this really is a hardware issue that they can't fix with a future firmware update, I fully expect Microsoft to step up and replace the device regardless of the warranty status as this is a manufacturing flaw.  There would be some serious push back if Microsoft knowingly has a faulty product and won't fix it.

Again - here is the knowledgebase article: http://support.microsoft.com/kb/3024327

-James