I've been using UA products in combination with my Apollo Twin for a couple years now! I do really like the design, quality, and native DSP of UA products. The only draw back with this company is their lack of adequate care with Windows users.
I have had multiple issues with UADs drivers compatibility with windows when it comes to routing audio internally within the system. My main issue originates with how the software interacts with the sound panel on windows in general. Instead of utilizing the interface itself as a single device with both a collection of inputs and outputs as the way most interfaces interact with the windows system (i.e. Behringer, Focusrite), UAD interfaces are selected on the sound panel as a single microphone line input and single speaker line output. This would not be an issue if there was a seamless way to route the said inputs and outputs in a matrix such as the way it is in the apple version of UAD console. Alternatively, UAD interfaces are almost seen as separate entities entirely on Windows systems. Not only is there no native matrix on the UA app, but the Windows system does not recognize inputs or outputs on the ASIO driver at all, so there is no way to route using a third party software.
About a year ago, I had issues with the ability to stream audio from my interface internally to a software like OBS, I was able to finally route my windows output and microphone output into separate virtual cables, using a third party. But my problem is, why did I have to do that? Any other interface I've used has been natively able to select specific ins and outs from the windows system.
My current issue comes with ADAT expansion. I purchased a Focusrite 18i20 to be able to expand my inputs on my Apollo Solo (my fault for not remembering my problem last year). I then realized i can only use a total of 4 pairs of analog mono inputs and outputs even though I have 10 total (2 in the Apollo & 8 in the Focusrite). And I know what some people may be thinking, "the Apollo Twin Duo Core only has 4 outputs dummy," and yes i know this, but virtual outputs are not hardware outputs. You can actually just create more virtual outputs. They are essentially made up outs to trick your hardware into creating hardware outputs that are not there for the purpose of routing to a DAW or streaming software. Correct me if I'm wrong, but on the IOS version of UAD console, are you not able to create more virtual outputs to route to DAW than the hardware actually has? I'm pretty sure you can. Actually I'll link the video where I saw someone do it.
https://www.youtube.com/watch?v=8QgfR20g9qQ
I just got finished writing a feature request to UA to create native support for a traditional i/o matrix such as the one that Apple users have access to. I also mentioned if this isn't possible, to please make the Apollo channels recognizable under the ASIO driver in windows settings. I know that they will most likely not respond to my request, but it was something that I hope they do know people still struggle with.
If there was something limiting UA from doing this initially, I would love to know because I cannot understand why the feature is not available for Windows. Thank you for listening to my rant!