The first version of ESP specifically references the free "AI" version of Cubase as the foundation.  The standard for a PC would be VST3 and this was available in not only the free version of Cubase AI supplied with the Montage M series but also the previous generation(s) of Cubase AI going back many years.   Cubase Version 4 (circa 2008) supports VST3.  You're not locked in to Cubase - any VST3 compatible DAW would work and there are other options out there.  ESP is not only VST3 compatible - but the other compatibility is more geared towards the Apple side of the fence.

I have sometimes found challenges installing VSTs into Cubase.   Not ESP (since I don't have it) - but other VSTs I would have struggles with.  Even though I know I'm installing the VST to the right directory Cubase would, for whatever reason, not "pick it up".   And, for the record, this isn't a 32 vs 64 bit issue.  BTW: my most recent challenge was with Cubase on a Mac.

On Windows the name of the game usually is to know where the right directory is on the hard disk where Cubase "looks" for VSTs and copy the files over to that directory.

On Windows the name of the game usually is to know where the right directory is on the hard disk where Cubase "looks" for VSTs and copy the files over to that directory.

On Win 10 using 'Run as admin' on startup the bottom of the black rectangle shows:

'Initializing: xxxxxxx' and one of the items is 'Expanded Softsynth Plugin for MONTAGE M.vst3' which makes me think it found it.

But in the 'Cubase AI Hub window that opens selecting 'Studio' and plug-in manager it doesn't show.

Cubase installed into: C:\Program Files\Steinberg\Cubase LE AI Elements 13\VST3'. The folder path under that contains:

Cubase Plug-in Set.vst3

vintagek-plugins.vst3

Yamaha

   Expanded Softsynth Plugin for MONTAGE M.vst3

       Contents

          Resources

             contents

          x86_64-win - this is where the actual VST file is located 'Expanded Softsynth Plugin for MONTAGE M.vst3'

I've tried dropping ALL of the above folders and the '.vst3' file itself into every directory I can't think of and it doesn't help.

In Add Track -> Instrument dialog it says 'No VST Instrument' but for MIDI Inputs the dropdown shows

2-MONTAGE M-1 (the default)

2-MONTAGE M-2

2-MONTAGE M-3

2-MONTAGE M-4

So it sees the 4 midi ports - the new MIDI 2.0 port isn't listed but that isn't surprising.

One thing I forgot to mention (and can't edit it) is if I don't use 'Run as Administrator' Cubase displays a message about not being able to find a license.

When I do use 'Run as Administrator' it finds the license and runs just fine.

Could there be a privilege issue on the folder that allows the Cubase startup code to find it but the Cubase runtime code can't find it or use it?