code 38 on Win 11

[bangthebox]

I'm in an interesting dilemma and hoping maybe someone here might've had a similar issue, with a success story. my set up is:

OS: Windows 11
Intel i9 14900K
motherboard: asus z790 pro creator (chipset 790)
64gb DDR ram
interface: Apollo 8x (1st gen)
add'l: UAD satellite

I recently updated the Thunderbolt port from TB2 to a TB3 card. The Apollo is daisy chained with the Satellite: one TB4 cable to the Satellite (which i hear the cables are backward compatible if needed), and one tb3 to the tb port on my motherboards input ports. In console, both devices are detected. I have no problem connecting, everything opens up fine and this is a brand new computer I built a few weeks ago; however when opening older sessions in my daw (Steinberg Cubase 12), i'm getting a code 38, plug in was disabled or not found. When I look at my plug in inserts, sure enough all the plugins paid for are there. I'm able to open them, and they don't display any sign of demo user, so console in a new session and it does acknowledge, however, the recording sessions I have are not detecting the use of my uad plugins and throwing a code 38 error. before I upgraded my computer, this session opened up with no hiccups, no problems. I have a few lexicon 480's, some 1176, tubetech c1-lb, and a few other uad plugins that I can't remember right now; and it would open with no problems. Now i'm getting this error. I did reboot, no luck. I haven't reinstalled (but will later today), I don't see any option for firmware update.

Has anyone went down this rabbit hole before and happen to have or can confirm a working solution?

 

[Procman60]

Hi, BangTheBox, I have exactly the same config. TB4 cable from Apple, 1meter. Even Apollo (1st) connected in serial, or on the second TB port of the Asus motherboard, even with ONLY the Satellite connected ... the error 38 appears as soon I have more than 6 plug ins (1176, or API 2500 Preamp for example). Definitly, UA IS NOT COMPATIBLE with Windows (10 or 11).
It's a shame they haven't been able to fix this for years.
My advice: don't use Universal Audio if you are on Windows

 

[bangthebox]

Ive been up and running since this post. Definitely dont cheap out on your thunderbolt cables and get the apple grade ones. I eneded up doing a clean reinstall and using apple grade tb3 cables and no issues...every once in a while i will need to reboot as ua console gives me a message that my plugins have reached capacity, when really only 2 are running and no open session. Hope this helps you in your journey to get things stable.

 

[Neotrope]

Hi, BangTheBox, I have exactly the same config. TB4 cable from Apple, 1meter. Even Apollo (1st) connected in serial, or on the second TB port of the Asus motherboard, even with ONLY the Satellite connected ... the error 38 appears as soon I have more than 6 plug ins (1176, or API 2500 Preamp for example). Definitly, UA IS NOT COMPATIBLE with Windows (10 or 11).
It's a shame they haven't been able to fix this for years.
My advice: don't use Universal Audio if you are on Windows

Works just fine on my Windows i7 machine -- you just need to have genuine Thunderbolt on board, with properly set BIOS settings, and follow the UA tweak guide, and the forum post roundup on Windows optimization. Definitely, UA *IS* compatibile with Windows, if Intel based system with TB chip on the mobo and properly optimized.

 

[djangodeadman]

My advice: don't use Universal Audio if you are on Windows

I have not encountered any problems running two X8Ps on either Windows 10 or 11. However, I did, in the past, have problems with Code 38 errors on a Thunderbolt Octo Satellite. Support were helpful, but not able to some up with a solution. Eventually, I sold the TB Satellite and bought a USB Satellite in its place. I have not experienced any Code 38 problems since.

 

[Neotrope]

I also had one machine that would not play nice with anything Thubderbolt, even a dock. That little box ended up with a used USB Twin dual and solved that.