Sonar X3 Trial won't start

I downloaded the X3 trial version, installed it, restarted my PC and started it.  
 
It went through some sort initialization process where it checked my hardware timing, and said everything was OK, and then it copied my user settings (what's up with this - I hadn't made any user settings yet?) and that was it.
 
Now when I click on the SONAR X3 icon the splash screen appears for a fraction of a second and goes away.  In Task Manager the process SONARPDR.exe*32 appears for the same fraction of a second and that's it.   Nothing.   Also, nothing is written to the operating system's event log  (I'm a software engineer -  what's up with Cakewalk's exception-handling?!)   I tried a second reboot of the PC with no change.
 
My PC is a Lenovo E31 Thinkstation running Windows 7 Professional. 
 
I have no special hardware attached to my PC right now -  just a mouse and a keyboard.    This is my first experience with a cakewalk product.    Not very impressed so far . . .
 

The *32 implies 32 bit sonar on 64 bit windoze

check task manager - all process names with "*32" suffix are 32 bit on 64 bit windoze
 
to the op, check windows event log

lawp
The *32 implies 32 bit sonar on 64 bit windoze

 
Yes, that's correct.  64 bit Windows runs 32 bit apps just fine. 
 
(I'm running the 32 bit version because I've seen reports of problems with plug-ins (i.e., 32 bit plug-ins) with the 64 bit version.)
 

Yeah I was replying to bob really, his questions seemed redundant

What sound card are you using? Asio drivers?

robert_e_bone
Yes - and I apologized earlier for that.  
 
The other questions were valid.
 
If you have an audio interface that uses a USB connection to the computer, is it possible you have it plugged into a USB 3.0 port?  This can cause instant crashes and other flaky behavior.  My Presonus audio interfaces wants to be plugged into only USB 2 ports. 

 
As I said in my OP, "I have no special hardware attached to my PC right now -  just a mouse and a keyboard.   "
 
There's no special sound card with this PC, just the integrated audio.  I have several other software tools that manipulate audio -  Audacity, MP3DirectCut, and a few video editors - and they have no problems.    I expect an application to trap exceptions in things like drivers.   For example, Adobe Creative Suite doesn't like something about my video card driver, but it doesn't crash; it just puts up a box telling me that various features will be unavailable.
 
I know I sound like a broken record, but how does X3 do its exception-handling and does it maintain a log file someplace I can interrogate?    In 2014 it's almost unheard-of for a modern piece of software to crash without a trace of what happened.   I think Sonar X3 is the software equivalent of MH370.   I just want a ping.
 

lawp
We don't know how sonar does error handling and it doesn't save a log

What sound card/audio device are you using?

As I said above, it's just whatever integrated audio comes with the Thinkstation E31.    The technical specifications for the E31 workstation just say:  "High Definition (HD) Audio, Realtek® ALC662 codec"
 
But why does it matter?   It's just for output to speakers.  I've got dozens of things on this PC that output to speakers with no problems - other audio editors, video editors,  audio and video players, streaming music and streaming video players, browsers, etc.
 
Also during installation X3 did some kind of check of internal system timing which appeared to involve audio resources and pronounced everything just fine.
 
The only purpose of the soundcard should be to play music I'm editing to speakers so I can hear the results of what I'm doing.   I won't be using the soundcard for anything else.  My PC is on my network and I have lots of files on my network from audio-recorders, video-cameras, MIDI sources, etc, and those will be the raw material for what I'm editing. 
 
How do I get actual Cakewalk tech support for this?      Do I have to buy the product?  (this is the trial version).   Can I get my money back if they can't solve it?
 

Just a follow up - I sent a private message per my post above - to Ryan Munnis of Cakewalk, and hopefully he forgets to enjoy the beautiful weekend and logs on to the forum over the weekend to help you.
 
Bob Bone

I thought I'd start from scratch incase anything that got downloaded from Cakewalk was corrupted in the download.   But I don't see a way to UNinstall the existing crashing app. 
 
Originally it did the whole install procedure including creating a desktop icon and putting the files in C:\Program Files (x86)\Cakewalk\SONAR X3 Producer Trial (I asked it for the 32 bit version) and filling up the registry with Cakewalk stuff.    But it's not listed as an installed program in Control Panel\All Control Panel Items\Programs and Features .   Why?    
 
So how do I get rid of it?
 
 

I re-downloaded the app and did a total reinstall.    Everything appeared to happen just the way it did the first time.   It asked me to make some selections and check off that I read the rules, etc, etc, and then it said it needed to reboot my computer.
 
It asked if it could shut down any running programs in order to reboot.   Of course the installer was the only running program because earlier it had suggested shutting down all the other programs.   And since the installer was the thing doing the asking I assumed it knew what it was doing.    The installer was the only running program and it was asking if it was OK to shut down any running programs so surely it must have determined that it was safe to shut it down.
 
But this time I decided to assume the X3 installer had no idea what it was doing!   So I said no, don't shut down and reboot.    Sure enough, the installer had more to do and after a moment it put up a message saying it was unable to register APRO.DLL and did I want to try again or ignore?   I told it to try again and then it was happy.  And now the app comes up just fine.
 
So the problem was that the installer wanted to reboot the PC before it was done doing the install!!  
 
I've written quite a few Windows installers myself and I can't imagine how they did this unless their install code is running in separate threads, or even whole separate processes that don't talk to each other.   I'd get fired if I wrote an installer that told the user to reboot while it was still in the middle of registering DLL's.