I just wanted to point out that when you use an older trusted soundcard in Windows 10. And there is no modern driver but there is for windows 7/8 you can install with the compatability settings (rightclick installer). This might work. Then there is the possibility (if the former doesn't work) to install the driver and see it does not work. Go to device management and then search the driver in program files > manufacturer name and install using the manufacturer.INF file. If that doesn't work there is the possibility in the menu in the device management to INSTALL OLDER HARDWARE. Here I found a driver for a Korg Kontrol49.
 
So most old hardware should work with Windows 10. Maybe this will help someone.
 
When you plug in modern hardware Windows 10 (when connected online) will download the correct driver from Microsoft servers.
When your hardware is connected and you installed it with windows 8 drivers. Once online it may detect it has newer drivers. It will install those windows 10 drivers without giving you notice.

Yeah you actually helped me....or at least made me think more about installing Win 10. I have a brand new Midas console that doesn't have Win 10 drivers and an old soundcard that I use for clients that are bent on doing 24/192 projects. That card doesn't have any drivers for it past Win 7. So I am terrified to update to Win 10 at this point.
 
Your post makes me feel a bit better....but I'm usually in the minority...and when something goes wrong for me, it goes VERY wrong. :( Thanks for the post!
 
-Danny

I also know that UAD version 8.5 is toast with WIN 10, 8.4 and earlier work but not the latest update.  A user (Billy Buck) took the plunge and informed us in the UAD forum.  Then it was confirmed by other users but when they roll back to 8.4 all is well (just can't use the latest plugins from UAD yet).
 
Not sure where the problem lies but last time it was both CAKE and UAD that had to modify their software to get UAD to work last time (which they did do and didn't waste much time getting the fixes out to us UAD/SONAR users).
 
But, at this point, I am holding off on WIN 10 until the UAD issues are ironed out.  I, like most of us, want to make music and not be our own IT support getting our rigs to work.
 
Good ideas from the OP for those you wish to take the plunge.
 
Jim

jimkleban
I also know that UAD version 8.5 is toast with WIN 10, 8.4 and earlier work but not the latest update.  A user (Billy Buck) took the plunge and informed us in the UAD forum.  Then it was confirmed by other users but when they roll back to 8.4 all is well (just can't use the latest plugins from UAD yet).
 
Not sure where the problem lies but last time it was both CAKE and UAD that had to modify their software to get UAD to work last time (which they did do and didn't waste much time getting the fixes out to us UAD/SONAR users).
 
Jim

Jim, I believe it's UAD's fault. They don't even test on Sonar in house any longer. Remember when we used to have our own little Sonar check box in their control panel? I've been having a UAD 2 issue for the longest time. (it only happens with UAD 2 plugs) When I call up a preset and edit it inside a Sonar project and then save, upon reopening, my changes to the plug are gone and it reverts back totally to the stock preset I started with. I called UAD, waited on the phone for 48 minutes only to be told "we don't test on Sonar any longer" followed by "I don't see anything in our tech support notes about this." This happened to me in Reaper too...but seems to work perfect in Studio One 2. Something is weird somewhere.
 
UAD didn't even want to take a look at my issue and I even offered to beta test anything they wanted on Sonar and didn't even want any of their plugs for free. I figured if they'd let me, I'd be doing our community a service. They weren't interested. What I want to try and find out is....why they don't acknowledge our existence any longer. I wonder if someone at the bakery poo poo'd in their Cheerios or something? Maybe Noel or one of the bakers will see this and fill us in on what UAD's problem is.
 
Whatever the case.....glad there is a work-around. If I do update, at least I'll know to hang back on 8.4. I'm running 8.3 at the moment. No need for me to update further as they are just adding plugs and adding fixes for pro tools and their Apollo. Thanks for the heads up.
 
-Danny

Danny, 
 
A bit irked to hear of the lack of response from UAD. FWIW, I've submitted my vote/interest to UAD to address this and suggested a fraction of their marketing budget be allocated to engaging the Sonar community vs. the relentless coupon spam. Your offer is a great example of the potential benefit to both UAD and Sonar users. 
 
However wondering if this might be in some way related to the release of the Prochannel modules, specifically the Tape Emulator. Included vs. $349 list is a threat to any business model.  
 
In the meantime, I'm auditioning replacements. Perhaps an active sticky thread to outline a procedure for creating and comparing Prochannel preset equivalents to the stock settings would generate some interest. Possibly a bit of waving the red flag and any tweaks likely to deviate from the "meticulously modeled analog uniqueness" of their plugs, but I expect the results, while lacking the gorgeous GUIs and the HW assist might be viewed as some benefit to users with a priority on creating music. 
 
 
 

jackson white
Danny, 
 
A bit irked to hear of the lack of response from UAD. FWIW, I've submitted my vote/interest to UAD to address this and suggested a fraction of their marketing budget be allocated to engaging the Sonar community vs. the relentless coupon spam. Your offer is a great example of the potential benefit to both UAD and Sonar users. 
 
However wondering if this might be in some way related to the release of the Prochannel modules, specifically the Tape Emulator. Included vs. $349 list is a threat to any business model.  
 
In the meantime, I'm auditioning replacements. Perhaps an active sticky thread to outline a procedure for creating and comparing Prochannel preset equivalents to the stock settings would generate some interest. Possibly a bit of waving the red flag and any tweaks likely to deviate from the "meticulously modeled analog uniqueness" of their plugs, but I expect the results, while lacking the gorgeous GUIs and the HW assist might be viewed as some benefit to users with a priority on creating music. 
 
 
 

I'm irked also. It appears that company is plenty happy with suiting all the Pro Tools and Cubase users. I mean heck, why on earth would any company turn down a free beta tester that wants nothing from the company other than for it to support another DAW that they once supported?
 
Incidentally, I found that my issue happens in Reaper also. So at this point I believe it is something UAD related. I remember one of the other bakers posting something somewhere a few years ago that UAD had something other plugs don't which made them a bit strange in Sonar or something. Something to that effect....I'm probably messing up the answer, but it was Sonar X(insert version) something at the time.
 
Sorry for taking this thread in a slightly different direction guys.
 
-Danny

I dumped my UAD 2 Quad card and all the plugins midway though last year when I moved to Win 10.

I've got to know that I'm working with developers who are moving along with the times. They seem to be pushing the Mac side very hard with constant hardware updates that start off Mac only. I felt a bit like PC users were second class citizens.

Then there was the pricing that I felt was just not competitive anymore.