I have a project which has crashed and I can no longer open, unless I use safe mode;  I have not identified which plugin is the culprit and instead, have loaded the file by selecting No to All.
 
In my quest to solve the crashing project, I have reset and rescanned my plugins.  A lot of plugins failed the scan:
 
BX stereomaker, PSP Xenon, PSP Stereomaker, Stillwell the Rocket, Trackspacer, Eventide UltraChannel and 3 UAD plugins out of the full UAD package that is installed.  All of the plugins are the 64 bit VST 2.4 versions and this is the first time I have seen these plugins fail, after having worked fine for years and many projects.
 
Yesterday I reinstalled all of the plugins that failed the scan, I followed this procedure:
 

• I reinstalled Sonar
• I uninstalled all plugins that failed the VST scan
• I deleted all remaining files in every directory I could find including %appdata%
• I emptied the recycle bin
• I reset and rescanned
• I reinstalled each plugin one by one and rescanned after each installation, WITHOUT resetting (no need, right?)

Each plugin worked the first time it was scanned so I didn't reset before each scan.  All was well until today.  I am using Lounge Lizard in this project and Sonar can't seem to find it since the reinstall, so I reset and rescanned.  Now all the plugins I just re-installed have failed the VST scan again.  I have enabled the plugins anyway and I know it is risky.  They seem to load in Sonar ok, despite failing the scan and this has me worried;  if I continue to use them, will they corrupt my project one day?
 
Does anyone have similar experience with plugins working fine for years then suddenly breaking?  Why would only a handful of UAD plugins fail, wouldn't they all fail if they were incompatible?  Also, I am pretty sure UAD plugins are compatible!
 
I have run MSE, Avast and have Symantec running and I am virus free.  It does seem that this trouble may have started when I updated Sonar to the Foxboro update, but that seems unlikely as I haven't seen anyone else in the forum have this issue.
 
Any help is appreciated, I will email support about this if I can't work it out.
 

Hi. Do I understand correctly, that you are running your Antivirus in realtime? Try disabling it (when using SONAR), and see if that helps. I have seen this suggestion before.
Best of luck.

You seem to have an awful lot of antivirus stuff running. Never recommended to have on during installation. Certainly no need to have it on while running Sonar.

Have you tried a system restore?

Hello please send me a vstscan log which should list the reason for the failures. In Foxboro there is a new feature to capture a scan log.
 
To do this, first ensure the following folder is present on your system.
%appdata%\Cakewalk\Logs
You can type that path in windows explorer. If The Logs folder doesn't exist yet create that Folder. (the scanner needs that to store the logs - future builds auto create that folder when necessary)
 
Open preferences VST
Hold down the shift key and click the "Reset" button.
This should reset the VST inventory and automatically rescan all the plugins. However this time it will write a VstScan.log file in the %appdata%\Cakewalk\Logs folder.
 
The log file should reveal what is failing. If you provide a link to that file I can take a look at the failure messages.
 
thanks,
Noel

I should clarify that I only have Symantec idling in the background and don't have Avast running while I'm working.
Also, I installed Symantec and Avast after the track got corrupt.
 
Thank you for help Noel! I will create the log file and send it to you.

You shouldn't be running two virus scanners at the same time. They will conflict. You will probably need to uninstall one of them.. Try disabling symantic in the meantime.

Ta.

Hello Noel,
 
Thank you for looking into this, here is the drop box file:
 
https://www.dropbox.com/s/0tw1ydvgvqwhry0/VstScan.log?dl=0
 
Thank you!

I actually did uninstall Avast before I started the reinstallation, I should have clarified.
 
Thanks

You asked for reasons. We see a lot of issues when people haven't run windows update for a very long time, and/or they haven't updated the plugins to the latest version.

Sometimes running Sonar as Administrator works around some issues.. Cheers..