Brand new install crashes at launch.

I used to use SONAR many years ago and decided to try it again. I ordered the Platinum (from Sweetwater) upgrade, installed everything, then pushed the Launch button. It immediately crashes with a SONARPLT.exe has stopped working error. I've tried running as admin and nothing. Kinda worried that a brand new install of a brand new program won't even run the first time and of course tech support is closed on the weekends. I'm hoping someone here might have some ideas. I also use Ableton and Cubase and those are running fine so I doubt it's a driver issue.
 
Thanks in advance for any help.

Uninstalled and reinstalled from CC, still crashes. Uninstalled and tried installing with the individual installer, still no good. Tried Administrator for both, nothing.
 
I used to love Sonar and switched cause school used Cubase, but I never really liked the Cubase workflow. I had used Cakewalk for MANY MANY years. I'm hoping this is some minor thing that can be quickly resolved, and they'll obviously not start my year countdown until it's working.
Thanks

Sure. 1 month old Alienware 17 i7-4710, 16GB RAM, Windows 8.1 64bit, program drive is 250GB SDD, 500GB SDD and 1TB HD storage, NI Audio 6 audio interface. Cubase, Ableton Live, NI Komplete Ultimate, VSL, EWQL all working fine. Ummm... missing anything?

Skippysonics
 pushed the Launch button. It immediately crashes with a SONARPLT.exe has stopped working error. 

slartabartfast
What do you mean by "crash?" Do you get any indication that the program is launching, or any error message? How does the programs's exit occur? Does it "crash" Windows (BSOD freeze restart), or is it just that Sonar does not do what you expect it to?
 
 

I can only ask, have you tried launching from outside of the Command Center?

I have tried starting from the CC and externally. I click on either, a black box saying Sonar Platinum comes up and within a second a "SONARPLT.exe has stopped working" message pops up and it closes. Gonna give Sweetwater a call now.

When a driver takes down an application it probably hasn't loaded enough to enable any error message logs because it's not inside Sonar.

A few questions for you.
 
1.  Do you use on-board sound or an actual audio interface for Sonar?  I ask, because you will achieve much better results by offloading all the analog/digital conversion to a dedicated audio interface, than by making your computer's CPU try to handle it.
 
2.  Are you using ASIO4ALL?  If so, be aware that a great many folks have had all sorts of errors - even just having it installed.  It is at best a 'wrapper' that really uses WDM but presents itself to applications as ASIO.
 
3.  If using ASIO drivers, if you have your default Windows Audio Device set to use the ASIO drivers of an audio interface, AND you launch Sonar, Windows and Sonar will fight over the drivers, and will likely be problematic.  Even simple things like the audible sound of a mouse, can cause disruption/crashes.  I have chosen to have only my high-end music applications, such as Sonar or the stand-alone versions of synths, to point to my audio interface, while I have the Windows Default Audio Device set to use my on-board sound chip.  This way, I never have anything fighting over the ASIO drivers of the audio interface.
 
Bob Bone