Complete uninstall and reinstall of X3 ? Because of a bug that has existed since at least version 8.5 ? That's like completely rebuilding a car engine just because it needs an oil change. I'm not going through all that trouble just for a bug that although really annoying is not mission critical especially when uninstall/reinstall will have no chance of actually fixing the bug. Closing and restarting Sonar always fixes the problem for awhile at least and that smells exactly like a bug to me. I have just never been able to find a trigger event or precursor to reliably reproduce the bug or I would reported my findings to support. It's appears to be completely random and intermittent but there must be a cause, it's just not apparent yet.
(For the record I am presently or have been in the past a beta tester for quite a few music software developers including a very famous one from the Boston area so bugs are not an unfamiliar experience. )
Yes I always use the latest version of Sonar and all the software I use including the 269 plugins I have installed.
This bug has nothing to do with the way Sonar was installed or upgraded or scanned or reset, etc etc.(See Kylotan's post) Like I said the other 3 DAWS I use have never called up a wrong plugin and they were installed in exactly the same manner as Sonar.
Thanks for trying to help, I appreciate it a great deal but recommending a complete uninstall and reinstall of Sonar X3 is just unnecessary. If I were a newb and didn't know better that would cost me a lot of work for absolutely no chance of reward.
EDIT: Actually after giving it some more thought there is a clue in my first post. The incorrect plugin was called up when trying to load the second instance of an already loaded plugin. I'll have to keep an eye on that to see if it's a factor going forward.