I am getting warnings during a VST scan after resetting all plugins. The Melodyne, Nectar and Waves DLL files are brought up  asking me to disable or enable the plugins during a scan.
 
These are fully registered plugs and I have not had issues before with X3 scanning, that I recall, until I installed SPLAT. I enable anyway and things seem to be ok.
 
I also get these errors in X3 now. Along with the above issue, does X3 share the same plugin browser with X3 if they are installed on the same machine?

Yes - vstscan.exe is shared between all versions of SONAR installed (well, one shared for 64 bit, one different one for 32 bit).  It's not ideal for the reason you've encountered.

Check your VST paths in all versions of Sonar. Make sure the settings under the VST (preferences) are more or less the same. Make sure the same path isn't listed twice (esp in the scenarios of parent folders scanning child folders). Open CCC settings and make sure it's all correct in there as well.
 
Sonar does have a tendency to change the values.
 
As general house keeping I suggest you remove the plugins you do not need (esp the old ones).

Cheers..

been using SONAR for years. The paths are the same. Since they share the same VST scanner, that explains why both versions are exhibiting the same behavior. I have a minimal set of Plugs I use and test. There is nothing extraneous in my libraries.
 
Something in SONAR VST Scanner is amiss...

I am getting this occasionally with I-lock plugins as well , 
   If I reopen the project it is fine .  
I only noticed this after the last update .

Guitarmech111
The paths are the same. 

Sorry to ask this again. You've definitely double checked this. I've had paths that have been changed before, most recently in fact.

I understand, thanks for checking. I try to keep the VST paths in sync since I am testing them in different versions of SONAR.
 
Never had the problem before SPLAT updates. which one? I am not sure.

Guitarmech111
Never had the problem before SPLAT updates. which one? I am not sure.

Hate to admit it, but my brain has failed me so I can't supply a decent enough answer here. Sorry.

I've had this happen once or twice out of the blue.   I just reboot, reset/rescan and the problem VSTs are suddenly not a problem anymore!

JonD
I've had this happen once or twice out of the blue.   I just reboot, reset/rescan and the problem VSTs are suddenly not a problem anymore!

maybe, but we shouldn't have to 3 finger salute in this day and age of software.