I'm having a similar problem with the mono version of the L2.  Everything else WAVES works fine but all of my projects that contain the L2 mono open with an error (couldn't tell you the exact message as I'm not in the studio).  I've read a couple of fixes but all seem like a total PITA.  Using X3e.

mgh
why does every Sonar update break Waves? as someone on the monthly scheme I initially thought this was a good idea, but now I'm regretting it!

I've not had this happen with Waves during the monthly update process. I do know from past experience though that moving the Waves shell dll file breaks the link to the actual plugins. You can't move that file like you can with other VST dlls.

For waves VST3, the support dude told me when I first started using Waves, point Sonars scan to Program Files\Common Files\ VST3 (or whatever it is) and DO NOT have it pointing anywhere else. Once I done that I have not had a problem. Sometimes when installing a new product, a plugin may not work, it is usually C4 mono, all I do is remove waves location from Sonars VST scan, apply or whatever, close preferences/options, reopen preferences and VST Scan settings, and add back Waves location, apply, close and everything is fine. Never had to uninstall/reinstall, really never had a problem to speak of, especially after doing what support said to do above.

skinnybones lampshade
Thank you very much, mudgel ! The solution you offered worked perfectly :)
 
 

Glad it worked. That fix is specific to the issue you mentioned.