I started to think that this may be the case, but I also strongly suspected that it was a driver corruption issue.įinally, I gave up for the evening and powered everything down. Support suggested that it was a faulty TB cable. When I powered the Apollo on, my desktop icons would refresh, and the Thunderbolt software would show only 'port 1' as connected, and in add/remove hardware on the taskbar, the Apollo appeared as 'base system device' but was not showing up in the Win10 Device Manager.

I tried uninstalling/reinstalling all UAD software, drivers and preferences, but could not get the installation to work or the Apollo to be recognised. Restarting the system, or power-cycling the Apollo would usually allow it to reconnect, but it would disconnect again after 15-30 minutes with a loud 'SQUEAK!' noise, then it would attempt to reconnect on it's own, would appear in Console, but would only have 44.1 and 48Khz sample rates selectable, and there would be no audio output.Īfter a while, the Apollo would not reconnect at all after power-cycling or a system restart. It had not done this before.Īt the time, I was transferring EastWest Hollywood Strings Diamond from their USB3 hard drive to a 1TB Samsung SSD, so I had to wait several hours before I could restart the system and see if it would reconnect. I went downstairs to make some coffee and when I came back up, the Apollo had disconnected. I just had this start happening the other day with my Apollo Twin MK2. (I have the GA-X99-Designare EX in mind, as it's the only thunderbolt mobo i can put my 6850k inside.) Im about to go and buy a new Thunderbolt AIC card and try once more, but im seriously thinking about switching to a different mobo. My question now - were you guys able to get it working again? I mean, i guess that when unknown base device got shown in device manger with thunderbolt turned OFF in BIOS - it recognized something is plugged in, but as soon as thunderbolt was on in BIOS - error45/device not connected because of the damaged cable. So now im guessing i probably damaged it when plugging/unplugging the card when reinstalling it.Īnd im unsure if it would work, but i guess so. One of the smaller cables connecting to the pins is out and i can't securely place it back in. Sadly it's still not working, HOWEVER i just noticed that the cable that goes from the card to the thunderbolt header is damaged. Now i enabled the update back, and im on: I even tried the Thunderbolt_Win10_64_17.3.72.250 drivers (that are newer but theoretically unsuported for ThunderboltEX3 - but are made for the exactly same hardware piece) with no luck. Even after i rolled back to 'Version 1709 - April 10, 2018-KB4093112 (OS Build 16299.371)' i wasn't able to get it working.

Windows 10 bootcamp thunderbolt drivers