I recently bought some new plug-ins which Sonar x3b does not seem to see in the vst folders on boot up, So I went into the preferences and asked Sonar to scan VST folders again, and made sure the folders were in the list to be scanned...No Go on them VSTs being seen, But oddly the scanning continues on on and on and on, and on...and on over and over....seems the only way to stop the scanning, is to close the program and restart it, cause clicking on the x only starts it over.....What is up with dat?.
 
Just thought I would put it out there.
 
Sir Les
 

What plugins? Are they the same bit as your system? VST2, VST3, DX? Can't really help you out without more details.

Not Sure...NEWLY RELEASED Sasquatch Drum Plug.Win: VST 32/64 bit
Mac: VST/AU 32/64 bit. I believe , but it does not say for sure what vst type, Just a Guess...and I am using some free Computer Music Plugs RECENT Edition, which do not show up, and these also do not really state their sort either...mostly I would imagine vst 1s 2s 32bit with some 64bit ones here and there....
 
Doesn't matter really about the plug ins.?..As I have other software where they may work...what is odd, is that the vst scanner keeps on scanning and scanning when asked to rescan the folders ...the blue window (vst scanner) has a X at the top right to close or stop the process?, clicking this X closes the window..but it reopens and continues to scan....and scan, and scan....Can you reproduce it?, by going into preferences, selecting the plug in tab, and selecting scan folders?...doesn't need vsts of any sort to be buggy...If it is Buggy...right?
 

You have to go to preferences/vst scan and change from background scan to scan at startup. This should help.

Thanks Cowboydan...I will try to do  that next time on the system...But isn't the default already set to scan at startup?
I noticed it scanning whenever I launch/start Sonar x3b, and when it is finished it stops scanning , when left to do it's thing on startup......So it must be set by default to scan at startup....right?
The problem seems to start when I start the scan manually after the startup scan, and I am in Sonar x3b with a template opened....
 
But like I said, I will try the suggestion you put out...But I believe a bug of some sort is happening here.
 
Thanks to all.