Thanks for this note. There were a few Tips in this thread. Which is the one that worked for you ?
I wish to add one more TIP: after many weeks, I have also found MAPPING a Network Drive that is NOT in USE but still Mapped, will cause Waves to load very slowly and in my case crash Studio One (freeze) as well. No one had the answer, including Support or the Development Team in Tel Aviv. Oddly, it’s the only plugin / VST out of every one I own that causes this issue and that includes: Arturia, East West, KV, and many others.
I have several Mapped Network drives off this Desktop. Some are powered Off and Powered On only when needed. This is to save on wear and tear, infrequent use etc. This may occur if you have a Tablet or Laptop that is connected to your LAN and you go off Site, same scenario could occur.
Unfortunately Waves tries to access those disconnected Mapped Network drives which drags their plugins to a crawl when loading and may also crash your DAW. I discovered this by creating a second Windows account on this Desktop with No Mapped Drives. Studio One and Waves plugins (all) loaded fast and they worked fast. This led me to dig further, compare both accounts and figure out is this a Permissions issue or some other issue. Sure enough, after I Disconnected my Mapped Network Drives on the 1 User account, the issue was resolved and has been working fine since.