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
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

126 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Anonymous
    2014-12-08T22:33:56+00:00

    once I replaced mine earlier, my corporate bought about 20 surface pro 3. I had reimaged with mdt 2013 successfully....the only issue I had with pen and onenote, but I had figure it out. so its good so far.

    Was this answer helpful?

    0 comments
  3. Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
    2014-12-08T20:56:55+00:00

    On Mon, 8 Dec 2014 17:58:35 +0000, aidanhammond wrote:

    >>Hope the above clarifies and goes some way to help resolve the issue.

    It sure sounds like the driver was not built correctly to reference all

    applicable ID's. In any case, I've also sent this in to an internal contact and

    referenced your case number to insure it is on someone's radar.

    Thanks for the info.

    __________________________________________________________________________________________________

    Barb

    Windows Entertainment and Connected Home MVP

    My Blog - http://digitalmediaphile.com/

    Please mark as answered if this answers your question

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-12-08T17:58:35+00:00

    Hi Barb - I closed off my comments in both threads as there will likely be different users subscribed. 

    I purchased the first surface Friday 28th November. The firmware update failed and driver issues reported in device manager. Microsoft support tracked these problems under 1271333827. At the time of reporting, this was seen as an emerging issue with Microsoft support and I was offered a replacement (refurbished) surface, however opted to exchange with the retailer for a new surface.

    I exchanged the first surface on Wednesday 3rd December. The firmware update failed and driver issues reported in device manager. Microsoft support tracked these problems under 1271851583. As of today it was confirmed that this is a known issue, however with the fix due in January, I was once again offered a replacement (refurbished) surface, however I again opted to exchange with the retailer for a new surface.

    I exchange my second surface today, Monday 8th December and am happy to report that my third surface works as it should out of the box. The firmware installs without issue, however this device does have a different hardware id for the touch controller firmware.

    Some high level notes from the troubleshooting over the past week and a bit...

    Surface #1; #2

    Surface Pro Touch Controller Firmware / Hardware ID:

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

    Surface #3

    Surface Pro Touch Controller Firmware / Hardware ID:

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

    Official driver pack (as referenced in Microsoft Answers)

    \SurfacePro3 - November 2014\OOBNovember18th2014SurfacePro3\Microsoft\FW\Touch\TouchFirmware.inf:

    Line 29: HKR,,FirmwareVersion,%REG_DWORD%,0x1AA1B42

    Note: No reference to Hardware ID: 0x1A31A36

    Given there is no reference to the hardware id in the official driver / firmware download, I believe this is likely the reason it is not possible (at this time) to both update the firmware of the surface and why the device shows up as an issue in device manager, with a code 10.

    Hope the above clarifies and goes some way to help resolve the issue.

    Aidan.

    Was this answer helpful?

    0 comments