Surface Dock USB ports not working - Dock Updater repeatedly fails

Anonymous
2018-01-02T11:42:03+00:00

I have Surface book 13.5, and Surface Dock. USB ports on the dock are not working.

Running Surface Dock updater says I need to power cycle the dock, although I already did it several times.

Event viewer reports error code 12105, with message: "Failed to update USB hub firmware."

Surface | Accessories | Surface Dock

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

87 answers

Sort by: Oldest
  1. Anonymous
    2018-03-05T17:22:49+00:00

    I'm experiencing the exact same issue everyone else is having. Uninstalled all previous versions of the dock updater. Cleared registry using above tool. Ran Windows Update tool. Uninstalled and deleted the Surface Dock Integration driver.

    Reinstalled the latest dock update tool and still get the immediate "Encountered an unexpected error" failure. And I'm told to cycle power on the dock.

    Event viewer gives me an Event ID 12105 and states "Failed to update USB hub firmware."

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-03-05T21:06:51+00:00

    I am having the same exact issue, none of my Surface Dock USB ports are working. I did everything as well, updated the Surface Book Drivers and Updates, uninstalled the Surface Dock Integration driver, restarted my PC. I made sure all Windows Updates were installed correctly. I was getting the same 12105 Event ID error when initially trying to update the Surface Dock firmware.

    However, after uninstalling the Surface Dock Integration driver and restarting my PC, I logged in as a local Admin and was able to update the surface dock firmware successfully. I thought this would have resolved the problem, but I still do not have the USB ports working properly. This is very frustrating. I don't believe this is a hardware issue since many users are reporting a similar issue. 

    I also ran the Hardware and Devices troubleshooter within the Control Panel and that didn't do anything either. I am running out of things to try! Microsoft needs to get on this ASAP!!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-03-05T21:09:58+00:00

    There was a sharp increase in the number of replies to this post in the last 2 or 3 days, which means that Microsoft messed up pretty bad recently.

    MICROSOFT, IT'S ABOUT TIME YOU FIXED THIS!!!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-03-09T07:29:44+00:00

    I don't get an error message, but a few weeks ago one port failed, now one of them work and my Surface Pro won't charge via the dock. The diagnostic test didn't tell me anything. I seem to get advice to do a lot of highly technical things that put my files at risk. You don't have to re-build your washing machine when it goes wrong, a technician fixes it for you. My dock is only a few months old and it looks like a total waste of money.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-03-12T14:57:29+00:00

    I have the exact same problem. Dock was working fine when I left the office on friday.

    Today it worked for half an hour or so, then mouse and keyborad died.

    Switched to another dock, worked for another hour...same thing again.

    Now we have two broken docks, dock updater fails with above message.

    Two observations though:

    1. It seems to not be related to my surface book (although my book might have killed the dock), since we tried two other surface books on both docks and also there, the USB devices don't work anymore (both surface books have never been used with those specific docks). My book still works with two other docks (where I could also successfully run the dock updater today).
    2. USB devices work again once I use an active USB hub and connect the hub to the Surface Dock. So it seems like a power issue (although I cannot explain how this is possible).

    Maybe this helps anyone

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments