The automatic scan should never get stuck on a plug-in that has already been scanned. The automatic scan should only scan new plug-ins. Make sure the "Rescan Failed Plug-ins" and "Rescan Existing Plug-ins" are NOT checked in Preferences > File > VST settings. These options are intended for temporary use with the manual scan option.

FYI, I have had plenty of problems with the Youlean Loudness meter plugin. So much so that I've completely removed it. Apparently, the developer is aware of the problems but hasn't gotten around to fixing them.
 
Dan

scook
The automatic scan should never get stuck on a plug-in that has already been scanned. The automatic scan should only scan new plug-ins. Make sure the "Rescan Failed Plug-ins" and "Rescan Existing Plug-ins" are NOT checked in Preferences > File > VST settings. These options are intended for temporary use with the manual scan option.

OK scook  I have to give it to you , I did what you said yesterday after I updated SONAR on my main PC .
 
Old Kenny  "Made sure the "Rescan Failed Plug-ins" and "Rescan Existing Plug-ins" were NOT checked in Preferences > File > VST settings."
 
 
I don't know what happened next because it all happened so fast I missed it
Walked into my kitchen to get a fresh cup of coffee and when I got back my scan was over ...
There were no crashes , and everything was there where it was supposed to be
 
Now I'm starting to wonder if Cakewalk should create an online detention classroom for all the dumb a$$ed holdovers that don't know some of the basics I'm not gonna mention any names but I know where I'll be after 3 O clock
 
What can I possibly say at this point ? other than Hey scook I'm glad you came down hard on me 
 
thank you ,
 
Kenny
 
 

dcumpian
FYI, I have had plenty of problems with the Youlean Loudness meter plugin. So much so that I've completely removed it. Apparently, the developer is aware of the problems but hasn't gotten around to fixing them.
 
Dan

Hi Dan ,
Thank you for the info  I'm glad I nixed that plug early in the game ...
The TDR Kotelnikov I had on that computer was on there for years and it came up as from 2015 ...
I'm sure if I updated w a more recent version it would be OK ...
The TX16x was another one I haven't used much ...
Had I known what I know now I'm sure things may have worked out different....
FWIW, none of these I consider a loss ...
 
all the best ,
 
Kenny
 
 

None of those plug-ins may be the problem. Now that the scanner has run to completion I would not be surprised if adding the plug-ins back and running scan again (or if automatic background scan is enabled), they will get picked up. Just do not run a reset or have the two scan options set. Sometimes a plug-in that does scans correctly trashes memory in a way that causes plug-ins to fail later on in the process.