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

Anonymous
2014-06-26T13:57:29+00:00

MDT 2013 - Windows 8.1 all updates.

Download surface Pro 3 firmware and driver http://www.microsoft.com/en-us/download/details.aspx?id=38826 to mdt 2013 out of box driver. Reimaged it, but missing only one and most essential driver

Surface Pro Touch Controller Firmware

UEFI\RES_{e5fff56f-d160-4365-9e21-22b06f6746dd}&REV_0

UEFI\RES_{e5fff56f-d160-4365-9e21-22b06f6746dd}

without this driver, surface pro is just untouchable...can anyone help me to find this driver.

thanks in advance...

Surface | Surface Pro | Install and update

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 No comments
Answer accepted by question author
Anonymous
2014-06-27T23:39:57+00:00

Hello Orionbelt,

I'm sorry that you are experiencing the inconvenience of this missing driver on your Surface Pro 3. We're here to help.

As this is a pretty technical issue related to a re-image of the device, we suggest you contact our Technical Support Team to help you with this in real-time. You can contact them through chat or phone here.

Thanks for reaching out to us, and please contact us again if you have any other questions.

Best Wishes,

Zack_T

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

126 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-12-08T12:40:25+00:00

    I have strong suspicion that this is somehow related to only hardware id REV_1A31A36.  If you open up the touch firmware installation INF, there is not an entry for this hardware ID and thus I believe why the installation is failing.  I like to hear from anyone who has success with firmware 426.27.66.0 on this hardware ID.

    I'm on my second surface with touch controller firmware hardware id REV_1A31A36... Have tried the suggested solutions provided in the thread and from Microsoft support multiple times without success. 

    @ccote, good to hear you've resolved the issue - can you confirm the hardware id of your touch controller firmware?

    Aidan.

    Hi, the touch controller firmware version oils 426.27.66.0. The driver provider is N-Trig. Hardware Id is REV_1AA1B42.

    Let me know if you have other questions,

    Ccote

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-12-07T14:50:39+00:00

    I have strong suspicion that this is somehow related to only hardware id REV_1A31A36.  If you open up the touch firmware installation INF, there is not an entry for this hardware ID and thus I believe why the installation is failing.  I like to hear from anyone who has success with firmware 426.27.66.0 on this hardware ID.

    I'm on my second surface with touch controller firmware hardware id REV_1A31A36... Have tried the suggested solutions provided in the thread and from Microsoft support multiple times without success. 

    @ccote, good to hear you've resolved the issue - can you confirm the hardware id of your touch controller firmware?

    Aidan.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-12-07T14:20:10+00:00

    Well, I have finally been able to install the firmware by running all updates (including a windows update that takes something like 700-800 mb) before. Then, with my surface being in the docking station (not sure if it was necessary though), I restarted my it and the firmware update finally succeeded.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-12-07T13:43:29+00:00

    I have the same problem, and tried reinstalling with it at 100% and no keyboard, but I still have the "yellow triangle" and failed "firmware" note in the update list.

    I have had this less than a month, and although it seems to be working I am worried that this was a firmware update it is important that it should be on my surface pro i7

    John

    Was this answer helpful?

    0 comments No comments