Cubase LE 11 does not start due to VST plugin errors?

I downloaded the demo version of Cubase Elements 11, version 11.0.40. It does not start properly.

If I start the program then the ‘info’ box appears; and right after ‘Initializing VST.2 plugin manager’, the program closes. If I start the program again then I can enter ‘safe mode’ and disable 3rd party plug-ins. Then the program starts normally, and I can manually load VST instruments.

I tested all the VST plugins that are on my computer, and two of them (LABS, BBC orchestra, both from Spitfire) produced weird sounds so I deleted them from my computer. The others (Kontakt, and Groove, HALion Sonic, Prologue) work fine. However, despite deleting the Spitfire VST plugin, Cubase still does not load – I still have to start it, then start it again in safe mode with 3rd-party plugins disabled, and then manually load the VST instruments (Kontakt and Groove)

My question is: what can I do so that Cubase starts normally, and loads all VST instruments?

PS I checked several related topics about start-up problems on this forum but could not find a match.

Hi and welcome to the forum,

Are you on Windows or Mac? Which OS version exactly, please?

Hi, Windows 10 version 20H2 OS Build 19042.1466


Does Cubase crash while start? Or does it hang/freeze?

Hi, it crashes', i.e. it simply disappears (also from Task manager) after showing Initializing VST.2 plugin manager’


Is there any DMP file available?
Win: Documents/Steinberg/Crash Dumps

No, no DMP file, and no Crash Dumps folder within Documents/Steinberg…


The error will be most probably in any of your plug-in. Please, make sure, your plug-ins are up to date.

Generate a DMP file and share it via Dropbox or similar service, please.

Use Microsoft ProcDump utility to generate a DMP file, please.

  1. Please download ProcDump64 from Microsoft (~650kB) and extract the archive to a local folder on your harddisk.

  2. Run Command Prompt (cmd) as administrator (right click and select “run as administrator”)

  3. Navigate (in the Command Prompt) to the folder with the extracted procdump file.
    For example:
    cd C:\ Users \ \ Downloads \ Procdump
    Note: the dmp file will be written into that folder.

  4. Launch Cubase/Nuendo. You can work as usual. At any time, change to the command prompt and start procdump, to monitor Cubase/Nuendo for unexpected behavior (see next step).

  5. Launch procdump64 via Command Prompt:
    Cubase 11:
    procdump64 -e -h -t Cubase11

Nuendo 11:
procdump64 -e -h -t Nuendo10

The -h option will write a dmp file in case of an application hang. This might kick in too early sometimes, in case some action takes a little longer. Feel free to skip the “-h” option, if you are only up for fetching crashes.
The option -e will catch exeptions and the option -t terminations of the application.

  1. Prodump is now monitoring the Cubase/Nuendo process and will write a crash log, in case Cubase/Nuendo crashes or hangs. Perform the action that causes Cubase/Nuendo to crash and send us the generated crash dmp.

ZIP and share the DMP file via Dropbox or similar service, please.

Hi, thanks. I have updated the plugins.

I did not manage to generate a dumpfile using procdump64; I get the message ‘No process matching the specified name can be found’.

I have been able to generate a DMP file via Task manager.
www dropbox com/s/ocupx2y3bt16r76/Cubase%20LE%20AI%20Elements%2011%20%285%29.DMP?dl=0

I don’t know if it is informative, however: I generate the DMP file just before Cubase crashes. After Cubase has crashed I can not generate a dmp file anymore. So I don’t know if the error is captured in the DMP file…


Unfortunately this DMP doesn’t point to anything.

With some help of the Steinberg helpdesk I have been able to solve it.
Thanks again Martin for your efforts.

1 Like

Hi avdenboer, what was the solution? I am also experiencing the same with Windows 11, and have a feeling that Halion plugin is causing the issue

Hi tnyotta, what helped me to find which plug-in wasn’t working was to manually rename the folders of each plugin, as described here:
helpcenter(dot)steinberg(dot)de /hc/en-us/articles/206618850-Troubleshooting-for-Cubase-and-Nuendo-on-Windows#plugins

In my case I thus discovered that the Spitfire Labs plugins where the cause of errors.
(I had tried to delete this plugin, but it turns out that that is not trivial).

Hope this helps!