All my existing waves stuff and all the new plugins I purchased during the "big sale thingy" are working just dandy...EXCEPT...Element which, of course, is an instrument and not an effect.  It loads up (for the most part) fine and plays and loads presets but if I try to delete it from the project or simply close a project with Element in it I get the dreaded "Sonar.exe has encountered a problem and needs to close" crash dialog.  And, on occasion, just working with Element will bring it up.  The WAVES fellers thought at first it was due to Sonar not seeing the 64bit VST...not on yer tintype, little lady.  Not the problem.  They've been very helpful and prompt (on a weekend no less) but since they are more or less stumped they have asked me to let them remotely control my computer...they even have a little program they've had me download.  Now, I have nothing to fear from WAVES looking at or working with my DAW...it just seems Orwellian to me.  I suppose I'll give it a go but if early next week my posts start looking clipped and robot like you'll know the worst has happened...I'll be a cyborg or somethin.  Sheesh!!

Yeah, happens where I work sometimes. It can be quite spooky watching the cursor dart around the screen opening and closing files, while you stand helpless.
You might learn a few things though, and its good that they are trying to help.

I had them do a remote when I had problems with older dx versions.
IIRC they found a video driver error. Still have the program too.
Good luck..

When I was an IT Specialist at Ford Motor Company (many moons pass) I would use PC Anywhere
to control other workers computers...I also sold and repaired PC's, so I would always include a copy
of PC Anywhere to be able to "fix" certain problems from home....that was 20 years ago...
PC Anywhere was Purchased, along with The Norton Utilities, by Symantec....at that point, with
Peter Norton no longer involved, I stopped using their programs all together...

It's funny that, still today, people find it "weird" to have someone else controlling their computer...

I use remote control to help out my customers every day. It sure beats the old way of solving problems that defy a telephone-only solution, which was to hop on a plane. Ugh. And that was back before they started confiscating your aftershave.
 
Once in a while, I'll have some 20-something computer geek (always, strangely, named "Jason" and probably has a goatee and tats) tell me that it's a security risk and that company policy won't allow it. After a brief game of "I was flipping bits before your daddy was potty-trained" I can usually convince them it's safe.
 
The key is that the user starts the host service himself and establishes the connection to me, rather than the other way around (we give them a convenient desktop shortcut to make it simple). Nothing is left running after the support session that bad people could exploit. I let the end user see everything I'm doing on their own screen. As long as the remote tech follows these procedures, there is close to zero possibility of harm to the end user.

^^^^
What he said...especially being Waves...

I think they're pretty reliable...and a pretty safe bet...

I wonder how often those Waves techs find cracked versions of some of their plugins while they're remotely poking around on people's computers. ; )

Just make sure you have no pr0n on the desktop....

Well...spent about an hour on the phone with a tech in Israel with both of us working my computer to no avail.  The problem, so far, has them stumped.  I've sent an info file that Shahar worked up on my box to him/them and maybe they'll be able to tell from that what's causing the trouble. 
 
One scary thing was that at some point during our mucking about my MOTU interface quit responding.  Hence, no sound from Sonar on anything.  Not good.  Finally managed to get it back to normal after they relinquished control of the box and I rebooted.  Whew. 
 
 

If you've got the unfortunate 64-Bit Sonar issue with 32-Bit Waves plug-ins issue, I've found the solution. The Waves guys in Knoxville know the fix as well. You have to "hide" the 32-Bit versions of the plug-ins from WaveShell and re-scan/reset your plug-ins in Sonar. BEWARE of resetting your plug-ins! If there's a version change, minor or major, you could lose ALL your saved Waves settings from all your projects, since Sonar will no longer be able to find those plug-ins. Word to the wise.
 
And yes, very normal to have them jump onto your system. I've had Cisco Systems use my work desktop at times to help me troubleshoot something that I couldn't resolve on my own with CallManager/Unity/CCX VoIP or Nexus 7000 switching platforms.