This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I've got a new Dock connected to a Surface Book. The dock has several USB devices connected, a LAN Ethernet cable, and a DP monitor. The dock works fine for a time after boot; however, connectivity to the dock begins to bounce. The USB devices and monitor disconnect/reconnect rapidly. Removing and reapplying power to the dock has no positive effect. Disconnecting/reconnecting the connector from the surface also has no positive effect. The only solution is to reboot the Surface Book. After a reboot the dock functions as expected for a time, and then the process starts all over.
All of the Windows updates have been applied.
Any feedback would be greatly appreciated.
Thanks,
Blake
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.
My dock has exactly the same behavior. Only way it works well is a clean boot with dock connected. I am trying to be patient with the surface book but there are just so many irritating bugs - coming from Apple where things just pretty much work makes it hard. Problem is Apple doesn't make a 2 in 1.
Mine has all these problems too. The troubleshooting page is worthless. Are these issues patchable, or do I need to return this?
The dock has been quite a struggle. When it works, it's great. However, I find that at random times the setup starts freaking out. Windows makes the "unplug" noise, screen stays on, but keyboard and mouse stop working (MS sculpt kb/mouse combo). Then a few seconds later it makes the "plugged in" noise and things resume. Sometimes the screen will go off and back on when this happens as well. It will then go into a cycle of doing this roughly every 30-120 seconds.
If I move the USB wireless dongle for the kb/mouse to the side of the surfacebook it seems to stabilize a little bit. Perhaps the more devices plugged into the dock the worse it behaves? Currently I only have one monitor, ethernet cable, and the wireless dongle plugged in.
You described my symptoms to the "T". Good to know I'm not the only one. I don't really think it's a hardware issue. It seems more like a driver problem. Waiting patiently for a fix. Hopefully it comes sooner than later. I absolutely love the Surface Book and the Dock. MS just needs to work out the kinks as with any brand new product.
-Blake
I have a few issues with my SB and dock (some related to monitor order and DPI not sticking), but at this point the USB problem is the most pervasive issue I have as well. Basically, if I've ran my SB without being docked and I later dock it, sometime within the next hour USB plugged in devices (and sound; I'm using my built in wifi so I don't know about ethernet) will drop out and come back a second later. Once that happens it continues, faster and faster until it occurs within seconds.
If I perform a reboot right after docking, or shut down the SB and dock, then boot, this problem has not yet occurred for me. The problem also occurs if I remove the screen and leave the keyboard docks, then re-attach the keyboard. That though generally creates so much monitor instability that it makes this a secondary issue. ;)
As a sort of side note, there was a firmware update released today for the SB. I installed it, but the problem persists. The firmware update doesn't have a KB attached so I'm not sure what it was designed to fix, but not this. I'd also say unless there's a really strange hardware issue affecting all docks, replacing the dock with a new one isn't the solution. I'm not really looking for a lvl 1 support type of reply to this reply, but hopefully someone further up the chain is monitoring and sees these messages, and works to come up with a driver/firmware related fix.
