Intel NUC + OWC Thunderbolt 3 Dock

I’ve been using an Intel NUC as my primary PC for about a month, with no issues. Today, I finally added a Thunderbolt 3 dock to the system.

And if you listen to First Ring Daily, you may know that I initially struggled with that: As I noted in Friday’s episode, the dock—a 14-port OWC Thunderbolt 3 wonder—worked just fine with a few laptops I tested. But with the NUC, it was only driving video-out; all of the other ports, including the USB ports, were invisible to the PC.

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

I had asked whether any listeners/viewers had suggestions, and a few did, so thank you for that. But I had resolved to figure this out today, one way or the other. And in the end, I’m semi-proud to tell you that I figured it out myself. And semi-embarrassed that I didn’t figure it out sooner.

My first thought was that I needed to get the Intel Thunderbolt 3 utility that I sometimes see on other PCs. So I went to the NUC’s software download page, searched for Thunderbolt 3, and started downloading the Thunderbolt 3 DCH driver for Windows 10. As I did so, it suddenly occurred to me—yes, I’m a real genius—that maybe the NUC already had this software installed. And that maybe it just needed to be configured.

Bingo.

Sure enough, there was a Thunderbolt 3 Control Center application in Start. And when run, it showed me that the dock was connected to “Port 1” on the NUC. (Which is the only TB3 port on the NUC.) But the Connection Status link under Device Info said “Not connected.”

Not connected. Ah boy. So I clicked that link and was presented with three choices for the port: Connect only once, Always connect, and Do Not Connect. (Yes, with that mix of capitalized and non-capitalized words; Intel must have the Windows Insider bloggers moonlighting on the side.)

Obviously, I chose Always connect. And then Windows pinged and issued a notification: “‘OWC Thunderbolt 3 Audio Device’ is set up and ready to go.” Success.

Sure enough, I unplugged the three USB devices that were originally attached to the NUC—the webcam, the keyboard/mouse dongle, and the USB interface to my podcast mic—and plugged them into the dock. Everything works normally, which is what I had originally expected when I first attached the NUC.

And that means that there is now only one (non-power) cable coming from the NUC: The USB-C/Thunderbolt 3 cable which connects the PC to dock. In other words, this works as it does with a laptop now. (I’ve not tried powering the NUC from the dock, but I doubt that would work: One of the dock’s Thunderbolt 3 ports can drive 85-watts, which should satisfy just about any compatible PC or device. But the NUC uses a desktop-class 28-watt processor and probably can’t be powered over USB-C/TB3. I may test this later for the heck of it.)

The USB-C/Thunderbolt 3 ports on the back of the OWC Thunderbolt 3 Dock.

This is good for a number of reasons. But the big one, for me, is that it will help me swap out my NUC for other computers, especially portable computers, much more easily; I can simply use all my peripherals by swapping a single cable now. That will help especially with the “Living with…” series, where I am testing various (often non-Microsoft) technologies over periods of time. I’ll test this setup with a Chromebook or two sometime this weekend.

The USB ports on the back of the OWC Thunderbolt 3 Dock.

Now, the OWC Thunderbolt 3 Dock is the center of my daily-use PC setup. And the NUC is just a bit player. An easily-swappable bit player.

This post contains one or more affiliate links. We only recommend products and services that we believe are of high quality and helpful to readers. Making a purchase through an affliate link is one small way you can support Thurrott.com, and doing so does not result in any additional cost to you.

Tagged with

Share post

Please check our Community Guidelines before commenting

Conversation 16 comments

  • jim.mcintosh

    21 September, 2019 - 2:22 pm

    <p>Thanks Paul, I am so glad to see that I'm not the only one, who should know better, who has those DUH! moments! It's happening to me more frequently the older I get.</p>

    • Paul Thurrott

      Premium Member
      21 September, 2019 - 3:12 pm

      <blockquote><em><a href="#469274">In reply to jim.mcintosh:</a></em></blockquote><p>Yep :)</p>

  • brettscoast

    Premium Member
    21 September, 2019 - 2:25 pm

    <p>Great stuff Paul thanks for sharing I've really enjoyed your recent series on the Intel nuc you've given it a rebirth of sorts and the final outcome is very positive indeed.</p>

  • infloop

    Premium Member
    21 September, 2019 - 2:28 pm

    <p>It always feels good when you can solve tech problems on your own, regardless of if it's a small thing, a user error, or a tough one.</p>

    • Paul Thurrott

      Premium Member
      21 September, 2019 - 3:12 pm

      <blockquote><em><a href="#469277">In reply to infloop:</a></em></blockquote><p>Yep. As is so often the case, this one came to me as I was walking around the house doing something else. </p>

  • frank_costanza

    21 September, 2019 - 2:50 pm

    <p>Nice. I'd like to see something like this with a switch for swapping machines.</p>

    • Paul Thurrott

      Premium Member
      21 September, 2019 - 3:13 pm

      <blockquote><em><a href="#469293">In reply to frank_costanza:</a></em></blockquote><p>Yeah. Actually, that would be very useful.</p>

  • alexoughton

    Premium Member
    21 September, 2019 - 3:04 pm

    <p>For anyone wondering why you have to explicitly tell Windows to connect Thunderbolt devices: This is for security reasons. Thunderbolt devices get a connection to the system's PCIe bus, and get DMA access too. This creates the potential for a malicious device to compromise the system. By putting the connection control with the user, it reduces the risk since you are presumably only going to authorize devices you know about and trust. People can't surreptitiously plug rogue devices into your machine.</p><p><br></p><p>Something else to know about (at least this is the case on my work computer – which I don't fully control the configuration of), even authorized devices won't connect back to the system until I've logged back in to the laptop. This means if I walk back to my desk with the machine locked, I must unlock it on the laptop's keyboard before the dock (and external keyboard) will come alive. I'm not sure if this is always the case, or some additional security my employer has configured.</p>

    • Paul Thurrott

      Premium Member
      21 September, 2019 - 3:12 pm

      <blockquote><em><a href="#469294">In reply to alexoughton:</a></em></blockquote><p>Interesting, thanks for this.</p>

    • brettscoast

      Premium Member
      22 September, 2019 - 1:21 pm

      <blockquote><em><a href="#469294">In reply to alexoughton:</a></em></blockquote><p>Thanks Alex wasn't aware of this good catch. Thanks for all the useful information there</p>

    • IanYates82

      Premium Member
      23 September, 2019 - 6:58 pm

      <blockquote><em><a href="#469294">In reply to alexoughton:</a></em></blockquote><p>Yep. Stops the "evil maid" attack. </p><p>Firewire had a similar issue but wasn't as well policed – the devices had direct access to memory whereas USB is more of a request / response protocol (gross simplification) </p><p><br></p><p>TB3 is really powerful because it can act as part of the bus, but that can come with risks. </p><p><br></p><p>It'd be nice if Windows was able to pop up a prompt about a docked TB3 device and offer to let it connect. I've not had such a docl before – do other PCs do this perhaps? </p>

  • chrisltd

    22 September, 2019 - 9:19 am

    <p>I’ll be interested to see if the dock works with Chromebooks or what is likely to be the new Surface USB-C devices. Your dock is specifically a Thunderbolt dock, and I don’t know of any Chromebook or Surface that supports Thunderbolt.</p>

  • dontbeevil

    23 September, 2019 - 3:05 am

    <p>Nice that "thunderbolt control center" UWP</p>

  • sespumapsi

    23 September, 2019 - 6:20 am

    <p>thanks for this information</p>

  • vernonlvincent

    Premium Member
    23 September, 2019 - 9:10 am

    <p>Will you be testing with an eGPU soon?</p>

  • lewk

    Premium Member
    23 September, 2019 - 11:34 pm

    <p><em style="color: rgb(0, 0, 0);">"(Yes, with that mix of capitalized and non-capitalized words; Intel must have the Windows Insider bloggers moonlighting on the side.)"</em></p><p><br></p><p>I laughed way too much at this.</p>

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Thurrott © 2024 Thurrott LLC