Ok, Cubase.. happy to hear that: One of the files this plug-in needs cannot be found, please reinstall or contact technical support for assistance.
But you’re not gonna tell me WHAT plugin!? JESUS…
You might consider providing some more information, such as “what plug-in are you using that requires the unknown file?” When I read what you posted, that message isn’t “some plug-in needs something,” but rather, “the plug-in you’re using now needs a file we don’t know about.”
The more information you can give, with screenshots where appropriate, the better folks around here can try and help you.
in case it wasn’t clear.. that’s my point. what plugin.. I have no idea? well I do NOW because after googling it for a while someone had the same problem with izotopes plugins and I think it was Ozone 11 causing the issue. but I have .. A LOT of plugins and cubase gave no more than that text as a warning before crashing. over and over. a screenshot would have consisted of .. a screenshot of that text.
A DAW hosting 3rd party VSTs doesn’t necessarily know which VST is throwing an error when the VST itself is reporting some operational error. If they knew, they would probably tell you. This is true for any DAW, really - but there are various dependancies required for proper error attribution in multi-tiered sub-processes.
What I do in those cases is simply look and see what plug-ins are loaded, and which ones could potentially have their own file-based dependancies and start from there.
If you have a hundred different plug-ins, then systematic examination may be required. An easy way to help identify this is to open a new project and import track-by-track and see which one errors out. But there are multiple ways you can approach it.
It’s worth exploring because the DAW won’t necessarily know what the plugin was.