UBubba- You should write a book ;)
 
 Mike- I guess this is what can be frustrating about opening up to folks on the X2 board about a problem. It's like pot luck. You might get a 15 year old commenting on your problem.Who knows? He might just have a solution. Or you might be led down a rabbit trail.
 
 You knew it was happening on your machine and couldn't understand why. The nature of the problem pretty much eliminates any hardware configuration issues. Maybe an issue with how the ASIO talked to Sonar,or how Sonar was seeing the ASIO talk. Definitely a candidate for a  bug report to Cakewalk. 
 
 I hear you saying that you have a real problem with assumptions made from individuals who never bothered to look. In all honesty most people likely won't take even more than 5 minutes to look at a problem that they themselves don't think they are having. Human nature I guess. It is sad.Even worse if they said they looked and they didn't. Probably what sunk the Titanic. The worst problems might be the ones we don't think we have.
 
 

Starise
I have been guilty of making some of those " It's working fine for me" comments. I figure if they see that computer a,b and c are working ok  with the same keystrokes then  this leads to a probable conclusion that it might be a hardware or software configuration issue. 
 
 Since most issues from newbs seem to come from configuration or hardware I don't generally fault the software until those other things are eliminated. OTOH if computers a,b and c are all having the same issue then we can be pretty certain someone needs to file a report with Cakewalk on what's happening.
 
 I know you guys have had real issues. If it were me and it wasn't hardware or software configuration then I would do the same thing and try to find a solution/work around. If I simply couldn't get the product to do what I needed it to do I would look for another product that did. I think in saying " it's working fine for me" we are saying that it can work correctly. We may not know why but we know it works for us.

I've done it.
 
In the beginning it was meant as "it's working for me, as I use it".
 
Then I got into "I tried to reproduce your scenario, and I could not... so it's working for me".
 
Now I no longer (well hardly ever) say anything about how X2a works for me. What's the point? 
 
Back to the OP, yeah spacey, I believe that bugs may or may not affect everyone. And I believe that this may bue due in large part to what portions of the program each person uses and how they use it. That is not to take away from your situation where a particular 3rd part VSTi will not work for you.
 
But spacey, send me your discs and auth codes and I'll try it on my system with X2a and report back.

If I'm running the same version, I definitely think it adds value to say if it's working fine for me.  Of course, it's even better if I add in some details about what I'm using with it or what features I'm not using.  In trying to resolve these types of issues, you need to eliminate things one by one until you find what may be causing the problem (having programmed for over 40 years, including several years of tech support, I'm brutally aware of this concept).  Developers are usually screwed from the get-go in terms of financing, deadlines and the fact that it's virtually impossible for them to test the millions of different possible configurations and methods of use (this is why software gets released to the public early as a Beta Test).
 
Saying it works for YOU might not mean the software doesn't have a bug, but it may show that the bug only appears under certain conditions.  Heck, the software may work fine for 999 people out of 1,000, but you can bet that you'll mostly be hearing from that 1 person it doesn't work for!
 
The trick is to find out what's different in their setup (Ohh...  So you're using a SoundBlaster card, eh?) then you can debug the issue better.