Well I finally seemed to have everything working then yesterday I go to launch Sonar and it just sits at the Splash Screen.
I rebooted and it still did the same. So I ran the Ipswich update and it launched several times and worked great. Now today again Just a Splash screen.
Anyone have any idea why this would happen? I'm on Win 10 now,
 
Thanks

Hoenerbr
Well I finally seemed to have everything working then yesterday I go to launch Sonar and it just sits at the Splash Screen.
I rebooted and it still did the same. So I ran the Ipswich update and it launched several times and worked great. Now today again Just a Splash screen.
Anyone have any idea why this would happen? I'm on Win 10 now,
 
Thanks

Probably need a bit more information about your system to go on - Your Audio interface for a start. 

Have you made sure you're using the latest drivers for your Audio Interface (might want to check all of your hardware drivers while you're at it) . 

Is Windows on your machine fully patched.  Have you checked your Application event viewer to see if there is anything in there that is causing the Sonar issue. 

Maybe your normal template is loading a buggy VST preventing Sonar from starting...

Wouldn't hurt to drop a note to cakewalk support as well.

Well I found this and it seems to have fixed it for the moment but I'm not really sure why.
Thanks for your help!
 
http://www.cakewalk.com/D...roubleshooting.05.html

Well, that rebuilt your aud.ini file, which may have had something happen to it.  I believe some other things are done in that process, but cannot recall the specifics.
 
Glad you are back to functional, 
 
Bob Bone
 

I have run into what appeared to be a stalled startup before but when this has happened it generally turned out to be some window needing information but it was stuck behind the main sonar programon the screen/monitor... minimize sonar and see if something is there asking for something...
 
(sorry for my crude depiction but I hope you get the idea...)

More than likely, Windows is setup to use your audio interface to play its own sounds. This may cause the interface to change sample rate or bit depth, or even become locked by Windows so that Sonar can no longer gain access to it. It is best to disable all system sounds to prevent these kinds of problems.
 
The other possibility is that you are unplugging your interface between sessions and the USB port has changed. Some drivers can fail when this happens.
 
Regards,
Dan
 

Vastman
I have run into what appeared to be a stalled startup before but when this has happened it generally turned out to be some window needing information but it was stuck behind the main sonar programon the screen/monitor... minimize sonar and see if something is there asking for something...
 
(sorry for my crude depiction but I hope you get the idea...)

+1. For example suppose you installed a demo version of a plug-in and the time limit has expired. A screen might be showing behind the SONAR splash screen saying "Plug-in requires authorization. Go to web site and purchase? Yes/No." It will sit there and wait forever for you to answer.

I have seen this behavior before after installing Cubase, where it adds its "low-latency ASIO drivers", which then crash Sonar on startup. Perhaps Windows 10's default drivers for our interface tripped it up in a similar fashion.