I've got two new SoundToys plugins that I'm trying to get loaded, and I can't get Sonar to find them.  I've run the VST scanner several times.  I've verified that the .dll files are in a folder that is in the "VST Scan Paths" list.  I've activated the licenses in the most recent version of the iLok software.  What am I missing?
 
I have SoundToys Little Alter Boy that loaded without trouble when I installed it.  The ones at issue now are Sie-Q and Tremolator.  They are not showing up in the plug in menus or in the lists in the Plug-in Manager.
 
Thank for any thoughts on this,
Seth 

How did you determine SONAR does not see them?
Are you using a custom layout?
If not which layout are you using?
Did you try scanning for failed plug-ins, a check box in Preferences VST Settings?

Hi all, I just got the trem freebie from soundtoys and I have the same problem. During the scan I see the folder where the dll is fly by but the plug doesn't show up in the available VSTs or VST 3 menus. Well, at least I'm not alone 🙄. This is the first time this has happened. I also installed a Waves plug today with no problems.

Hi. Besides what scook asked. Is the plugin activated to the correct device? I have not had any issues with them.
All the best.

Hi Zargg, yes it's activated to the correct device (same device as ultrachannel which works fine). I've tried recanning,rescanning failed plugins etc with no success. I must admit I'm a little puzzled. I know my way around Sonar pretty well and can usually make things work but so far not for this one.

Well, I put the tremolater plug into the cakewalk vst directory, rescaned and all is now working. Hope this helps Sethmopod.
 

I ended up doing a VST Reset and then it found the SoundToys plugins.  This has caused me some other headaches, though.  I had a large number of old VST2 plugs that have now migrated to VST3.  I uninstalled the VST2 package before rescanning because I had been having some system slowdown problems related to too many plugins.  Sonar is not recognizing the VST3 versions as the same plugin.  I'm afraid I've just lost my settings on many years of mixes unless I re-clog my system with the older plugins.

Sometimes it works when you rename the '.dll' into something else e.g '.old' or move the dll(s) outside the installed folder and wait for sonar to scan again. (You'll see x plugins removed in the notification) after this you simpy restore the original name or location of the file and wait for sonar to scan again. This has often fixed my problems with plugins that wont appear in the browser.

Sometimes, removing the vst3, can also help.

sethmopod
I ended up doing a VST Reset and then it found the SoundToys plugins.  This has caused me some other headaches, though.  I had a large number of old VST2 plugs that have now migrated to VST3.  I uninstalled the VST2 package before rescanning because I had been having some system slowdown problems related to too many plugins.  Sonar is not recognizing the VST3 versions as the same plugin.  I'm afraid I've just lost my settings on many years of mixes unless I re-clog my system with the older plugins.

A rescan, as you found out, is often necessary to properly install a new plugin.  If it reveals other problems, it's certainly not the rescan's fault.  If you've been avoiding a rescan for fear of these problems, maybe now was not the time to do it just to get the free plugin installed.