No wonder, if you installed it without "run as administrator"?
How about try to reinstall it "as administrator" like other user mentioned, since it's also related to the Window's Registry as well! Hope this helps!
 

LHong
No wonder, if you installed it without "run as administrator"?
How about try to reinstall it "as administrator" like other user mentioned, since it's also related to the Window's Registry as well! Hope this helps!
 

 
Me thinks this is one for Sonar's install build dev to think on - it is quite unusual for an application to request the user to manually execute a setup with Administrator privilege, at least these days. Most installations now automatically request Administrator privilege during execution so that it's not possible to do otherwise. Easy-peasy, solves the problem, work fine - last long time....

.msi usually do request user elevation. Whether most .exe installers do, I don't know because it's become so second nature for me to run them as administrator to prevent the type of problems it seems Phil is going through. Why not take the safe route for something as important as your DAW. Just saying....
 
Steve

 
.msi usually do request user elevation. Whether most .exe installers do, I don't know because it's become so second nature for me to run them as administrator to prevent the type of problems it seems Phil is going through. Why not take the safe route for something as important as your DAW. Just saying....
 
Steve



I've never installed a version of Sonar by right clicking the installer and run as administrator including X-3c and I don't have the problem that Phil is having. Just saying....

If you run the install again as administrator and install advanced setup with only the basic install your problems should be fixed.

Actually, these suggestions have already been tried. I even re-formatted the HDD. I re-installed from the disk, and then it worked fine until X3c was installed.

It does sound like the registry is jacked up somehow. I wonder if re-personalizing SONAR would help? Be aware the starting SONAR with the CTRL and SHIFT keys held down will overwrite all the files in your user directory\AppData\Roaming\Cakewalk\your version of SONAR. So if there is anything in there you want to keep, make copies beforehand. I would also make sure that SONAR was running as administrator while holding the CTRL and SHIFT keys.

I believe that the Registry key which affects this is "AlwaysLaunchTemplate"
Now, here's where it gets really weird.
The value there is set to "0" (off) [just as it is in Sonar under Preferences]
If I change it in Sonar or in the Registry, it doesn't "take" - something on the Sonar start re-sets it back to "0" BUT, Sonar still loads the template.
In other words, I change the entry in both Preferences and the registry, but no - it doesn't take, and it doesn't work.
Bug report . . .
 

pdarg
 
Bug report . . .
 

I would call to Tech Support before bothering to file a problem report. They are in a better position to assess whether this is a bug or a problem related to your particular setup. Still would try re-personalization because it fixes some registry issues.

I did try re-personalization - makes no difference.