Some older plugins cause Cubase 10 to crash in Windows 10

[currentsound]

Running windows 10, I noticed that some older plugins that still work in Cubase 9 on the same machine crash when opened in Cubase 10.

But... I found a work around....
If you run Cubase 10 in 'compatibility mode' for 'windows 8'. All those plugins work fine, however you get a message saying "Soft E-Licenser does not have enough permissions" on bootup if you do this and Soft E-licenser plugins are disabled so that is the negative side effect of running it in 'compatibility mode' but the plugins that would previously crash Cubase end up working fine.

Running Cubase 10 in administrator mode does not fix the issue. I assume this is some sort of permission issue?

[volvissimo]

Hi, I make the same experience with Cubase 10. Would be nice to fix that issue in the next update. Thanks.

[bassbill]

Same issue here. Very frustrating indeed. I have C 10 for a week now, and still working with 9.5.41.
This is totally unacceptable!
Plugins in most of my templates cause C 10 to crash.
I will try your workaround @currentsound but still this is not a solution.
Anyone listening from Steinberg ???

Win 10 64 bit

[bassbill]

Yes, the workaround solves the problem as you described.
Hopefully everything will be alright with the first update.
Will continue like this till it comes.

Thanks @ Currentsound

[sonic74]

A big project of mine opened seamlessly in Cubase 10, but a smaller one crashes (suddenly disappears). (I am aware of the auto track color issue that crashes Cubase 10, this is not it) (also HiDPI isn't selected)


Working on multiple serious projects... once you lose the feeling of a rock-solid stability, you have no choice but to go back to 9.5.

----------------------------------------------------------------------------------------------------------------
Dear Steinberg,

There are really lots of power users out there. It is not anything like your trailer videos with a bunch of channels and instruments where a few hipsters come together and make one of those same songs over and over again. You have to test big projects with a wide variety of plugins and configurations. In a recent post, one of your staff is asking people about multicore usage with version 10. Why? Don't you have systems to test it? Build an i9, build a threadripper, build a Xeon, etc.. and test!

Are you aware you charge some serious amount of cash for the updates, only to have them fail in some way? Obviously that price doesn't cover betatesting.

P.S.#1 I also wish this forum becomes a place of free-speech and threads don't get suddenly locked.

P.S.#2 There is nothing wrong about hipsters.

[Fiction]

A big project of mine opened seamlessly in Cubase 10, but a smaller one crashes (suddenly disappears). (I am aware of the auto track color issue that crashes Cubase 10, this is not it) (also HiDPI isn't selected)


Working on multiple serious projects... once you lose the feeling of a rock-solid stability, you have no choice but to go back to 9.5.

----------------------------------------------------------------------------------------------------------------
Dear Steinberg,

There are really lots of power users out there. It is not anything like your trailer videos with a bunch of channels and instruments where a few hipsters come together and make one of those same songs over and over again. You have to test big projects with a wide variety of plugins and configurations. In a recent post, one of your staff is asking people about multicore usage with version 10. Why? Don't you have systems to test it? Build an i9, build a threadripper, build a Xeon, etc.. and test!

Are you aware you charge some serious amount of cash for the updates, only to have them fail in some way? Obviously that price doesn't cover betatesting.

P.S.#1 I also wish this forum becomes a place of free-speech and threads don't get suddenly locked.

P.S.#2 There is nothing wrong about hipsters.

+1 !!

[TidesN]

Please anyone an explanation , after much frustration, I found that deleting VST_Transit_64bit and Generic_Lower_Latency_ASIO_Driver_64bit I could finally get pass the Cubase 10 Pro becoming unresponsive at initialization. Win 10.

[maartenl945]

This seems to be a duplicate of issue: viewtopic.php?f=286&t=147296&start=25

[PRILIPAK]

me too

Same issue here. Very frustrating indeed. I have C 10 for a week now, and still working with 9.5.41.
This is totally unacceptable!
Plugins in most of my templates cause C 10 to crash.
I will try your workaround @currentsound but still this is not a solution.
Anyone listening from Steinberg ???

Win 10 64 bit

[pillerk]

I also crash Cubase 10 with older but still usable 64-bit plugins. 8.5 works fine with them. I do not think this update will be solved. I think Steinberg has started in that direction! And as usual, this is not a mistake but a property!

[pillerk]

I'm looking forward to the update...

[currentsound]

This seems to be a duplicate of issue: viewtopic.php?f=286&t=147296&start=25

I guess it is now since most of the people in that thread have found that the reason that their 9.5 projects aren't opening is because the plugins themselves are causing Cubase 10 to crash on Win 10 even though the same plugins work fine in 9.5

[currentsound]

I'm looking forward to the update...

The same plugins that were causing Cubase 10 to crash for me, still cause Cubase 10 to crash with the 10.1 update. Hopefully they'll eventually fix this in another maintenance update but I'm starting to worry a little as I thought this would have been one of the first things to be resolved. If they work in 9.5 and in Cubase 10 when running in 8.1 compatibility mode, I see no reason why they shouldn't run in 10. I speculate that something must have changed with how Cubase interacts with Windows 10 and VST plugins that is not happening when running it in compatibility mode or on other operating systems.

[maartenl945]

I'm looking forward to the update...

The same plugins that were causing Cubase 10 to crash for me, still cause Cubase 10 to crash with the 10.1 update. Hopefully they'll eventually fix this in another maintenance update but I'm starting to worry a little as I thought this would have been one of the first things to be resolved. If they work in 9.5 and in Cubase 10 when running in 8.1 compatibility mode, I see no reason why they shouldn't run in 10. I speculate that something must have changed with how Cubase interacts with Windows 10 and VST plugins that is not happening when running it in compatibility mode or on other operating systems.

Agreed!

Regards,
Maarten

[maartenl945]

I'm looking forward to the update...

The same plugins that were causing Cubase 10 to crash for me, still cause Cubase 10 to crash with the 10.1 update. Hopefully they'll eventually fix this in another maintenance update but I'm starting to worry a little as I thought this would have been one of the first things to be resolved. If they work in 9.5 and in Cubase 10 when running in 8.1 compatibility mode, I see no reason why they shouldn't run in 10. I speculate that something must have changed with how Cubase interacts with Windows 10 and VST plugins that is not happening when running it in compatibility mode or on other operating systems.

Agreed, and confirmed that the update doesn' t fix the problem.

Regards,
Maarten

[xhqk5]

There is a workaround in the german Forum. if u add the plugin microshift (from soudntoys, it can be disabled) to the insert in the control room, all the plugins are working again. Dont Know why but it works

[maartenl945]

There is a workaround in the german Forum. if u add the plugin microshift (from soudntoys, it can be disabled) to the insert in the control room, all the plugins are working again. Dont Know why but it works

Unfortunately, adding microshift in the project (in Cubase 9.5) and then trying to open with Cubase 10.0.10 doesn' t work for me.

Thanks for the suggestion though,
Maarten

[Steinberg]

@currentsound: do you have crash dumps from 10.0.10, too? If yes, please send them over, preferably to support but if you update here I'll have a look in any case when time allows.

The previous crashes were:

22.19 - Acoustic Feedback, access violation
22.21 - Metal Amp Room, access violation
22.29 - Likely related to Autotune 8, unknown error in process

Could you check that these are updated and (especially if you can't update the VSTs for whatever reason) check that the licensing software they use is a recent version?

[sonic74]

There is a workaround in the german Forum. if u add the plugin microshift (from soudntoys, it can be disabled) to the insert in the control room, all the plugins are working again. Dont Know why but it works

Strange thing, my 9.5 project is now loading on 10.0.10, before it was crashing, and the only difference is I switched on Control Room and inserted a Sonarworks plugin on my monitor outs.

So maybe it doesn't matter what plugin, but any plugin as an insert at the Control Room output? Very strange anyway ) But the project is working now:)

EDIT: Just tested... Switched off that insert plugin, closed / opened that project again, it still works. Even switched off Control Room, close/open, still works... I'll never know what the cure is, but I am happy, and sorry for this post.

[Steinberg]

Any licensing relationship with other plugins you had problems with?
Likewise, any UI relationship?

Some 'unknown error' crashes might hint at the first; the three crashes above all had a GPU driver component call just before the boom, which might hint at the second and would be very interesting to know if anyone remembers which plug-ins' UI were open (or opened automatically with project recall on loading) at the time of the crash.

[Rockefeller313]

I tried putting SoundToys Microshift on Control Room and bypassing it.

Now all Antares, Softube and Slate Digital stuff seems to work without running Windows 8 compatibility

I don't get it, but it seems to work now...

[currentsound]

I tried putting SoundToys Microshift on Control Room and bypassing it.

Now all Antares, Softube and Slate Digital stuff seems to work without running Windows 8 compatibility

I don't get it, but it seems to work now...

I have also read before on a forum somewhere that if you load a Soundtoys plugin first then the plugins you have mentioned will not crash Cubase 10. I don't have any SoundToys plugins to test this though but this is not the first time I have read this so there is likely some sort of relationship there with loading Soundtoys plugins that makes all the other plugins you have mentioned load properly.

[currentsound]

@currentsound: do you have crash dumps from 10.0.10, too? If yes, please send them over, preferably to support but if you update here I'll have a look in any case when time allows.

The previous crashes were:

22.19 - Acoustic Feedback, access violation
22.21 - Metal Amp Room, access violation
22.29 - Likely related to Autotune 8, unknown error in process

Could you check that these are updated and (especially if you can't update the VSTs for whatever reason) check that the licensing software they use is a recent version?

Here are the crash dumps from 10.0.10 I haven't updated the plugins yet. I used WeTransfer because it wouldn't let me attach them to this message for some reason: https://we.tl/t-mhQQ6P8pSO

The plugins you mentioned are the same ones in these crash dumps and all work jBridged for some reason even if you jBridge the 64 bit plugin version to a JBridge 64 bit plugin version file. You don't need to JBridge the 32 bit version. That combined with the soundtoys work around that other people have discovered would indicate some sort of bug to me.

There is a workaround in the german Forum. if u add the plugin microshift (from soudntoys, it can be disabled) to the insert in the control room, all the plugins are working again. Dont Know why but it works

And as mentioned they also all work when running in 'windows 8 compatibility mode'

It's easy for me to mix without these plugins at all. It's just opening 9.5 or earlier projects that uses any of these becomes a problem as you know from this other thread: viewtopic.php?f=286&t=147296&start=25

[naveman00]

Same issue here. Loading 64 BIT Waves Plug-in into Audio Insert causes crash.

[currentsound]

Looks like the soundtoys trick is working for all the people on this thread too. viewtopic.php?f=286&t=150923

Hoping Steinberg will acknowledge the problem and fix it without users having to do these sort of work arounds.