If you have a later Cubase license on the dongle it’ll unlock all previous versions.
You might try running XP on Virtual Machine. VMware Workstation is capable of passing the dongle through.
Runninig in a VM is not a good solution to try to actually use Cubase to play projects, so I wouldn’t even bother to install the instruments and extras, but it does work enough to start it up and convert things.
One of the huge plus’s of Steinberg was that the older versions could be retained on machine in perpetual operating mode, does the new licensing system not allow older versions to cohabit on the same machines? An essential commodity for people with exterbpnal hard drives full of archived projects, it’s all part of the business to retain projects, a colleague of mine has stacks of 2” tapes he’s recorded over years and I’ve a number of 16 track tapes that need to be digitised myself!
Thanks for your reply. So are you saying that your understanding is that, when the Sternberg dongle is formerly discarded by Steinberg licensing in the new year, as long as a dongle is in good shape with earlier licensed version of cubase on it will continue to be available and continue to run cubase and other licences on there for use as long as the the machine has the dongle in place?
If that were so, would the earlier versions of cubase installed on another machine still be recognised by the dongle or vice versa and run as expected for a few years?
It would certainly put to good use an older machine and save trying to sell if off on eBay, that would make a lot of people very happy and would be worth buying a new dongle just for that!
Bascially you can run a simulation of 2025: Switch off the internet from the computers with version C11 or older. If they will work, they will continue to work until the dongle breaks, your computer breaks down, or you start to exchange major hardware components (thus changing the computer).
I’ve just ordered a new mobo/cpu/ram etc to build my new machine for the new year for composing and working on and I’m intending to that I’ll keep my older one with version 11 hooked into my Yamaha DM 1000/2000 desk as the Yamaha Studio Manager (the software for those desks) and the Yamaha/Steinberg. When the individual projected have been recorders and exported in wav, they can then be imported into the other machine where they can be mixed through thr Yamaha DM1000/2000 desks as cub/nuendo 11 due to its OMS interface are superb fully integrated control surfaces for Cubendo and have the required facilities to create DTX and atoms outputs all under a master fader output to control during surround/atmos mixing.
Yes I just voted for this very good idea. But I fancy that there may need to be other methods needed to get Steinberg to give this priority. So far this request has 7 votes. I think I may try a more direct email to Steinberg as well.
Yes, mixing two technologies can lead to hiccups though it would basically be two different daws working together through Steinberg connect or another clock device should do the job, one, the cubase/nuendo 13/14 machine would be composing station, no dongle and cubase 11/12 would be the mix station using using the Steinberg/yamaha OMS protocol from the Yamaha DM 1000/ 2000 doing the mix work once the project has been transferred across entirely in wav files that would all a lot of archived tracks to digitised and moved across immersive mixing on the Yamaha which is still a great digita mixing desk, and a great Cubendo /controller. It’s very unlikely that Steinberg/Yamaha will release a great controller , let’s face it,they way way behind in that race but unfortunately the third party systems fro other third parties just don’t cut it. Probably take some research and exchange ideas with Steinberg Yamaha .
It worked for me when I used Task Manager (Win 11) and ended running process like Native Instruments Task/Hardware, Macrium, etc. Guess they were conflicting with the installation.
Go through and end running tasks while having the stuck install on page and then when it continues installing - you found the processes that was preventing it from running.