Cakewalk/UAD plugins issue in Cakewalk by BandLab Posted July 8 On 6/21/2021 at 9:19 AM, Tommy Byrnes said: I've found the best way to deal with UAD plugin problems like this, and many other VST problems as well, is to make sure I only have one VST2 folder location, which for me is Cakewalk\VST Plugins. Have the VSTScan only scan that one folder. I've always used that location, no matter the DAW just because I've been doing it since the early Sonar days. VST3 defaults to its normal place (C:\Program Files\Common Files\VST3). I copy (don't cut) the dll for the plugin I own from the main UAD Powered Plugins folder and paste them into a new UAD Plugins folder in my main VST2 folder and there they stay, unaffected, unless I buy an update for one of them or there are fixes to specific plugins. This way the VST folder and their contents aren't changed and there aren't all the UAD plugins to scan, just the ones you own. Just don't scan the normal UAD folder and you're good. Keep the UAD Powered Plugins folder intact because Console uses that location to load the plugins. I hope this helps. (edited for a stupid spelling error) Sorry, I'm a little confused here. Is it something like this: Perhaps if I create a special folder for UAD plugs in my cakewalk vst folder, I can just copy the plugins I want/own from the current vst folder (x86/steinberg/powered plugins) and only have cakewalk scan that folder. Then run the newer update, copy anything I want from it to that cakewalk vst folder I made and never scan the steinberg folder where it gets installed. Then it will utilize any new console updates but cakewalk only sees the plugs in the cake vst folder? Something like that? Just wondering if the update/firmware itself might not allow me to run the older plugins. hmmmm Maybe i'm way off here... thanks!