At first I thought this was a one-off weird problem on my end, but I just ran into two other people having the same issue with different 3rd-party plugins on Cubase 14, so I am wondering if there is a trend.
Anyway, a couple weeks ago I had a project with 6 instances of Waves Element. I had manually programmed the patches in each instance, and also saved them as Cubase presets for future reference. Over several days of working on this song I discovered that every time I re-opened the project, all my Element instances were reset to the default “Init” sound you get when you load the plugin for the first time. I would spend a few minutes re-loading the presets I had saved (very thankful I had bothered to save them to begin with) and continue working. But the next time I opened the project, all the Element instances were back to their Init patches again!
I asked around on other forums thinking it was a Waves problem, and never found anyone with a similar issue. I decided to just use Retrologue instead of Element. But then this morning, on a Cubase Facebook group I found a post by a guy who is having the exact same problem with Native Instruments Reaktor, and someone else who just started having the same issue in Steven Slate Drums.
The common thread in all three cases is Cubase 14.0.20. Has anyone else here had problems with random plugins losing their settings across project reloads?
I just ran into someone having the same issue with Omnisphere; when they re-open their Cubase project, Omnisphere doesn’t remember its settings from the last session. Has no one else here experienced similar behavior with Cubase 14?
If I ever had something like this, it was always with demo version of plugins, or plugins that weren’t correctly licensed and revert to demo limitations (of which one could be to not load session data).
I can’t speak for the other folks, but in my case (Waves Element), not only was the plugin properly registered, I even paid to upgrade it to V15 (and re-installed/re-activated) to test if it was a problem with the plugin. Did not fix my issue.
I have a theory the problem involves having multiple instances of the same plugin in the current project- because I know I had many Element instances in mine and the fellow with Omnisphere problems said he had multiple instances in his project…
I have never experienced this with the current version of C14. To make sure we are all on the same level, what is your Media Bay Version number? Did you check Media Bay to make sure the .vstpreset is there? I know, silly, but I have had issues with this and what is in Explorer.
Is it an intermittent issue or something reproducible?
If NOT using multiple instances, has this ever occurred?
@Martin.Jirsak may have some additional questions.
@Greg_Purkey - Hmm, how do I check what my Media Bay version number is? When I do Help > About in Media Bay, it just shows the Cubase credits (version 14.0.20).
I did notice that the presets in question do appear in Media Bay, under “This Computer” (specifically in “Documents\VST3 Presets\Waves\Element Stereo”)
You will be surprised - you can see it when starting the Steinberg Download Assistant, then click the About icon in the top bar of the SDA.
Got any ideas about this @Johnny_Moneto ?
Im just covering the basics, and not sure what avenues to pursue.
Ultumate Outsider has been around for years, creating some pretty cool tools for VST users.
Oh wow. Cool. Looks like I’ve got version 1.2.40.50.
This is not a burning issue for me; I worked around my Waves Element problem by just using Retrologue instead. 
But I just find it very interesting that I keep running into folks having this same problem with Cubase 14, each one with a different plugin. They could well be unrelated random problems…
No idea. It doesn’t happen on my end and I can’t see a pattern.