Hi, so basically i opened an older project of Cubase 13 Pro on Cubase 14 Pro but says that i’m missing my third party Vst’s libraries. I know already that i need to enable Vst2 on the Plugin manager but the thing is that when i did those projects my Vst’s were on a different folder inside my laptop, then later i moved those libraries inside my external San Disk driver, what is weird is that i scanned them already and i can use them. What i want is Cubase to set my instruments and patches as i left them not having me to add them again manually.
Welcome to the forum.
Most DAWs (the one’s I’ve used, anyway) behave this way if you’ve moved the plugin. This is expected behavior, particularly when you may keep multiple versions of a plugin from a vendor over time that are named the same thing but in different folders. Ableton does this as well, as I can have as many of the same plugin name in different folders as I want, which is kind of common for folks designing Max for Live plugins, etc.
Cubase IS leaving them “as you left them,” which is “gone” in this case.
Thanks for replying, maybe i needed to add that i’m using Spitfire libraries and that some libraries for example Intimate Strings, was able to load as it was saved before eventhough i changed it’s location, but not for Albion Colossus
This seems more like a Kontakt issue than a Cubase one. Cubase doesn’t load libraries the players do.
But I’m sleepy and may be I’m getting my wires crossed.
So, just to make sure we’re saying the same thing, do you mean the plug-in VST2 file itself, e.g. Kontakt7.vst, or do you mean the actual sample libraries that the plugin will load?
Two different things, with 2 different implications for solutions.
My reply was in regard to you moving your actual VST2 plugin files themselves to a custom folder, which you can do in Cubase. VST3s are all in the default OS plug-in folder (unless there’s some way to choose a custom VST3 folder in Cubase that I’m not aware of). I thought that’s what you were doing, and that upon opening the old project, it was pointing to the old VST2 location.
If you’re talking about the Library (e.g. Kontakt Session Strings or EW Adrenaline, etc) then that’s quite different, and something you can fix one time and be done.
Clarification please?
EDIT: I didn’t know what “Albion Colossus” was, but now I see it’s a library. As @Googly_Smythe has mentioned, you’ll need to make sure you’ve used the library manager for Spitfire audio to relocate those - but the good news is that you should only have to do it once. I don’t know anything about Spitfire audio or I’d point you in the right direction.
Spitfire Audio released a major update last year which changed the way libraries are handled. Have you by any chance updated Spitfire lately?
I think i’m talking more about the vst plugin. Albion Colossus uses a dedicated plugin from Spitfire, so no kontakt in this case. As you said there’s a way of relocating spitfire libraries using their App, which i’ve already done. What i’m seeing right now on the Cubase plugin manager is that there is two versions of the Albion Colossus plugin, VS3 and 2. Vst3 says [missing, missing], also it’s path is inside C: commonfiles (which i don’t know why if i moved it) and Vst2 it’s totally fine and it’s path it’s in my external drive.
Now comparing it to Intimate Strings library: It has the same dedicated plugin, was moved too, same location but no Vst3 appearing on C: Common Files and it loads up with the project totally fine.
AFAIK, you can’t move VST3’s in C14. It requires your VST3’s to be in the C:\Program Files\Common Files\VST3 folder structure. I can’t verify as I’m on MacOS. I’ll presume your reference to “Common Files” is that entire path, though.
I think you’re going to have to do some digging - it’s kind of hard for me to follow what’s actually happening on your side 
Have you checked if the VST3 plugin file is actually located under c:\common files\vst3? If not, you should reinstall the plugin, so that it gets correctly installed.
If you have actually moved the vst3 file away from that location: just don’t do that. As @Thor.HOG wrote, vst3 plugins must reside in the common files\vst3 folder, it is a strict requirement.
Thanks, i reinstalled the plugin and everything is okay now, i probably moved or deleted something