dbmm001
Thanks for the suggestions, but I always set up Windows to show all files including system files and hidden files. The only thing I can figure is that Sonar made a duplicate copy of the plugins somewhere that aren't visible by traditional search methods.

I can think of a couple of other things. You cannot set "Windows" as a whole to show all files from within Windows, you can only set something (unless you tell us what your version is we are only guessing what) in windows. The setting is only valid under a specific account, so setting it in one account does not set it in others, and setting it in an account with administrator group privileges does not set it in every user account. You cannot search for files that belong to another account from within the account you are logged on to. If you are running Sonar "as administrator" for example, it can access files in a user account that the current user is not able to search (or in some cases even see) because he is searching from within a different account. It could be that the file name you are searching is not correct. I doubt that Sonar somehow incorporates plugins files into itself in some form that is not available to Windows or file explorer.

dbmm001
I figured that, not goin' there...lol, now that I don't see them, they don't bug me at least...took the "Splat" plunge last night, (Kudos to the genius that thought up that acronym btw.....)Love it so far.......Thanks for the suggestions everyone.

Its not that hard or daunting....Just delete any reference or tail of a VST/Plug In you have un-installed but be careful and make sure you delete the ones intended.
 
Regedit isnt that scary if you are careful.

So, it's best to disable the plug-in first then uninstall it.

I'm the Administrator and only user will full access rights to all files including hidden and system files, so that's not the issue. I've moved on to Splat and don't seem to be having the same issues now that I've moved on to a new version, thanks everyone.

If you select the plug-in in question in Plug-in Manager, the "filename" displays the full path to the DLL that Sonar is actually using. This is a more positive means of finding ghosts than using a Windows search, I feel.
 
I have often used that to find out whether I am actaully using the "expected" version of a plug-in. It is surprising how often I end up with duplicates (or near duplicates) typically as a result of my having deviated from the default installation location at some point in the past.

I have a similar prob. The VST scan in X1, 2, & 3 is showing duplicates of every instrument. Although this doesn't affect Sonar's functionality, it shouldn't be happening.
 
Deleting Registry Entries CAN be sometimes scary. I found 10,000 entries for one VST that needed to be deleted. For that you need a utility willing to find and delete them for you, unless you have several years to delete them one by one yourself.

The only sure way is to start from a completely clean version of Windows, but only if you're prepared to reinstall everything from scratch.

Like said above, there might be a dupe .dll somewheres. You can run a registry clean utility to try and remove the old file path associations. I use the one inside Ccleaner. You can also exclude the plugin from SONAR's plugin manager if it just won't go away. I seem to recall there's a command line way of de-registering a .dll as well, though I can't remember the syntax off-hand.
 

I have Ozone 5 still showing as available to load in Sonar, but it then says it's  not available.  I've always upgraded and am on Ozone 7 now. Many times I've had sessions trying to track down and delete any references on my PC to Ozone 5, including in the registry, and still it shows as available in Sonar.  I've had to give up.  Very, very, annoying!!