This time, Alex, but you have certainly beat me plenty of times.  :)
 
Bob Bone

CakeAlexS
 please install this:

 
If this does not work,  please remove and reinstall Sonar (or dump it ;) ).
 
BTW did you run AVG at any stage?

 I tried this and it didn't work, though I am so thankful that you tried to help. And I don't use AVG.

caminitic
http://forum.cakewalk.com...messages-m2745641.aspx

Thank you , but I had tried the ideas listed here before sending my own problems out to the world.

robert_e_bone
Did you launch the installer with 'Run As Administrator'?  That's important for proper installation, and also for the completion of the registration process.
 
Many folks also have the Sonar icon set to also always Run As Administrator, as it gives you elevated permissions, even if your user account is an administrator.
 
Also, is antivirus software running, and was it running during the installation process?  It can interfere with both installation and execution.
 
I believe this is likely an installation mishap, and you may want to consider removing Sonar and installing it again.
 
Please post back if you need complete instructions for removal (including the registry keys and hidden sub-folders and such).
 
Bob Bone
 
 

I launched with Run as Administrator. I might have had Windows Defender running during install, not positive. Thanks and I could use the removal instructions.

robert_e_bone
It is a MS routine - looking things up on the web shows it coming up missing for other applications as well.
 
I would recommend having Windows up to date on maintenance, in any case.
 
If it were me, I would remove and install Sonar again, after first running Windows Update until it got all needed maintenance applied.
 
Bob Bone
 
 

I am up to date on Windows.

I may have missed it - what version of Sonar are you using?
 
Also, had this version been working and then suddenly go belly up?
 
Is it opening a particular project and then dying, or just getting into the program?
 
Bob Bone
 

robert_e_bone
I may have missed it - what version of Sonar are you using?
 
Also, had this version been working and then suddenly go belly up?
 
Is it opening a particular project and then dying, or just getting into the program?
 
Bob Bone
 

 
Thanks for helping. I'm using Sonar X2a Producer 64, build 351. I haven't had a version of Sonar that doesn't go belly up on a regular basis, and I go back to when you could put the whole of Cakewalk on a single floppy disc. Since the introduction of the Sonar X series, I use SoundForge mostly, even though it is not an ideal song creation tool. (People ask my why I don't switch, and the reason is I have enough of a working knowledge of Sonar to at least occasionally create something - when it works - plus I have all the soft synths and effects, and I'm not so sure how well they would translate with another DAW, and finally, the cost to get something else, both in time and money, seemed too high.) I have decided to permanently get off the Sonar upgrade merry-go-round until I can get a solid working version. I mean, do you guys usually just use versions that are one or two gens back to try to assure some stability?
 
What was happening was that I couldn't even get the program to start, now it will start, but it always ultimately crashes.
 
I completely uninstalled Sonar, reinstalled it as the administrator, and now I can at least open the program. However, I have worked on four pieces  and in all cases, Sonar crashes. Sadly, I didn't realize that I had to turn on the "save document" for it to work. Consequently, I lost all four. Now I have it turned on.
 
Most importantly, does anyone else have this problem? I haven't made it through one whole song without Sonar X2 crashing.
 
Thanks again in advance for any ideas.

Welcome back...
 
Well there's a million different reasons why Sonar would crash, and not all of them Sonar.
Could you update your footer to show the version of Sonar and whether it is 64 bit or 32 bit?
 
Please run chkdsk on all your hard drives for starters.
Then have a look at driver boost.
Please update your sound interface drivers and firmware if available.
For fun, run a defrag.
 
After you've done all this, and if the issue persists, please check your Windows event viewer for errors, please paste any errors here.
 
If issue still persists we would be looking at latency, Sonar configuration, and dody plugins, AUD.INI configuration or anything exotic hopefully signalled by the event viewer. But I will leave that to one side for now.
 
Hope this helps...

theloniouscoltrane
...However, I have worked on four pieces  and in all cases, Sonar crashes. Sadly, I didn't realize that I had to turn on the "save document" for it to work. Consequently, I lost all four. Now I have it turned on.
 
Most importantly, does anyone else have this problem? I haven't made it through one whole song without Sonar X2 crashing.
 

I don't really understand what you mean by "turn on the save document for it to work", since in all versions have always supported the standard Windows commands Ctrl+S, File > Save and File > Save As.   But that does raise a question - how exactly do you typically start a new project?
 

I think OP means autosave.