The main problem I had when fresh-installing sonar on a new machine was scrounging up licenses for things I purchased in the stone age. Things like cakewalk mp3 encoder which I bought back with Sonar XL (!) or the original version of PSP stereo pack...

PenguiN42


The main problem I had when fresh-installing sonar on a new machine was scrounging up licenses for things I purchased in the stone age. Things like cakewalk mp3 encoder which I bought back with Sonar XL (!) or the original version of PSP stereo pack...

Shouldn't be a problem for me. All of my audio production software is of recent vintage (unlike my collection of audio hardware). Some of my OTHER software is rather old, and might be difficult to find the software and/or license numbers.

Old thread I know. I'm getting a Win 10 machine and have a Win 7 machine with Sonar 8.5.3 and a lot of VSTs.

Scanning them in the new install will allow those (freeware) that are just .dll files work fine. My issue is more than half probably need to d a full installation, as installing them isn't just about putting a .dll in your VST folder but putting a few other things in System 32 and / or the Registry. 

I learned years ago here (and did it on a prior similar new PC scenario) you can drag the .dll in File Manager  over to touch something found in System 32. I just can't remember what. It worked 90% of the time, saving a lot of time in not having to authorize as much stuff. Help anyone?

I've always clone my setup over the top of the os with Acronis True Image on the new machine taking into consideration that it's only 50-50 that it will boot after I do that and that I'll have to install drivers for the new machine.
 
I'm a tech so that doesn't scare me.
If you're not then don't try this at home.