losoriojr
After this update, I'm unable to load 64bit or VST3 version of my waves plugins.   Wave support says they don't support the latest version of Sonar.  
 
What to do?  Geesh

Think about investing in another DAW.
Will probably be the cheaper alternative since you have invested in Waves plugs. And waves isn't the culprit, sonar is.

losoriojr
After this update, I'm unable to load 64bit or VST3 version of my waves plugins.   Wave support says they don't support the latest version of Sonar.  
 
What to do?  Geesh

Try a re-scan, I have the Diamond bundle plus a few others, all ok here after updating.

Thanks KingsMix.
 
How exactly is sonar (64bit) the culprit?  Meaning, all the waves plugins (4 total) were working:  VST3.  After the waves update, only 32bit vsts are working.  The only delta is the waves update.  
 
Regards,

As I mentioned above, I ran all of my VST-scanning apps after updating, to check for problems.
 
Found none, so I assumed there were none.
 
Wrong.
 
I'm going to guess that what happened to me was due to the fact that I don't pay WUP, and that I've got a lot of Waves plugins that are out of the 1-year free update period.
 
I was starting a new song yesterday, and went for a Waves plugin I use all the time.
 
Not there. Nor were a bunch of others.
 
I remember a lot of threads over the years re Waves plugins disappearing.
 
Here's what I believe happened.
 
When the update ran, one step in that process was to delete ALL of the Waves plugins (the .bundle files) in:
 
C:\Program Files (x86)\Waves\Plug-Ins V9
 
and then only redownloaded the ones still under warranty (a lot bought for $29) and reinstalled them.
 
The solution turned out to be running Waves Central and reinstalling the missing, post-WUP plugins. I then needed to force each VST-scanning app to do a full, clean rescan.
 
Next time there's an update, I need to click through it slowly and look for some option about retaining old (post-WUP or whatever they might call it) files, or at least download and reinstall everything that was there before the update.

losoriojr
Thanks KingsMix.
 
How exactly is sonar (64bit) the culprit?  Meaning, all the waves plugins (4 total) were working:  VST3.  After the waves update, only 32bit vsts are working.  The only delta is the waves update.  
 
Regards,

I understand what you are saying, but I deduce it to that conclusion because waves plugs are working fine in Presonus Studio One. 
Not trying to bash cake at all, but reality is ,there is no one manning the updates.

Pretty sure WUP has nothing to do with this.
 
But Waves did change the names of their VST shell plugins with this update.  Depending on how you have SONAR setup that kind of name change can cause plugins to vanish.  If you have SONAR set to scan for plugins on startup it should have done the right thing, but if you have it set for manual scanning you will have to do a scan yourself and plugins will look like they vanished.
 
When I updated, the installer didn't remove any of the bundles (for me), but if the Waves installer does do that (it can be flaky) you just have to do the full install in Waves Central and then a scan inside SONAR (or have it scan on startup).  When the names of the VST shell plugins change like this, it can cause all sorts of issues since the DLL/VST3 that was being used will no longer be there.
 
In this case the previous wave plugins were WaveShell-VST3 9.91_x64.vst3 the new ones are WaveShell-VST3 9.92_x64.vst3 (and if you have lots of Wave plugins you can end up with multiples with numbers as in WaveShell1 and WaveShell2, etc).  Some of the Waves plugins are also in a 9.7 shell (I think that's just StudioRack but I could be wrong).  When the shell names change, all sorts of things can happen, in any DAW, not just SONAR.