maybe there’s multiple vital versions in your plugin folders and due to a naming conflict the wrong one is loading.
i recommend doing a search in the plugin folders that are listed in your DAW for any instance of vital and seeing if there’s more than one copy in there. I don’t know if that’s a possibilty, just a wild guess.
i use Linux not windows, but there must be some kind of config file or registry entry that remembers things like themes and preset databasery.
I’m new to Vital, but presumably, it has preset/settings folders somewhere on your computer? If so, I’d look there and maybe try to open a preset or two with Vital.
I’d also look to see if Studio One 6.5.0.96106 was affecting any other plugins. If so, that would seem to be a dead giveaway that it’s a problem with Studio One 6.5.0.96106. Is that version some kind of nightly experimental build? If so, I’d stick with a recent stable build.
Failing a problem with Studio One 6.5.0.96106 or another build, at some point, I might also uninstall-- properly/completely-- Vital before reinstalling another version. Before that, though, if they were important enough, I’d make a copy of the presets/folder and other custom settings and place it/them elsewhere, like the desktop.
Then I’d ‘go around’ and make sure no traces of the previous version(s) of Vital-- including presets and other custom settings-- where leftover.
I might also test Vital in another DAW.
I have two DAWs installed on one of my systems and even if I only use one DAW, the other can be handly, if only as a troubleshooting device.
Does Windows have some sort of registry-cleanup utility and/or can one rollback any Windows upgrades?
In the past, I’ve have automatic Windows updates make a mess of my system before, including one where my computer kept turning off and rebooting endlessly.
Of course, it goes without saying to always make backup copies of important stuff.
I haven’t been following this precisely, but how about uninstalling Vital-- thoroughly (like eliminate any instances and settings)-- and re-downloading a fresh copy. It’s possible that it got corrupted. And again, try it in another DAW. That way, we might see if it’s the DAW.
Had the same issue. Projects would open up and vital would be set to Init. I had migrated to a new system with a fresh install of everything. Luckily I had my old drive from my previous system where vital still opened correctly. So I copied the 64bit dll and VST3 plugin file from the old system and just copy pasted them into my new system and then patches loaded correctly.
You might not have this option available, but you can maybe try installing older versions, and see if that will do the trick