clintmartin
Sorry to say this again but...
I have 3 daws and all but Sonar work fine with Windows 10. I always get the same error as the OP.
Since I value Sonar much more than Win 10, I went back to Win 7. Problem solved, all 3 daws work perfectly again.
 

In that case, to back up everything or take an image, and clean install Windows 10 would probably be the easiest fix. Or stay with Win 7, lots of folks have, and I don't blame them.  But if you decide to take the leap again, this is the best way.  Clean the hard drive and lose all of the baggage.  It's a guaranteed productivity killer, took me about a week to get everything I wanted loaded back on, but still worth it.  I love the smell of clean Windows in the morning
 
Once your copy of Windows 10 has been previously activated on your PC, you can do this clean re-install without re-activating with a key.
 
I did the clean install from the Windows 10 Media Creation Tool and I now have a clean machine that is running both Sonar X3 and Platinum, without a hitch. 
 
http://mspoweruser.com/clean-install-windows-10-using-media-creation-tool/
 
https://www.microsoft.com...are-download/windows10
 
Disclaimer: I have avoided the Anniversary update so far due to the high number of problem reports I saw.
 

Well, unless I read wrong, the OP said he had a creative xtreme audio and was using asio4all.  IF that's the case as I wrote above, he should use the legacy creative drivers.  Glad you're doing ok abacab.

eph221
Well, unless I read wrong, the OP said he had a creative xtreme audio and was using asio4all.  IF that's the case as I wrote above, he should use the legacy creative drivers.  Glad you're doing ok abacab.

Yep, I agree with you.  I just think he needs to eliminate ALL audio drivers from his rig and let Sonar cough up an error about missing drivers.  There is still something in there, possibly fragments in the registry, that is preventing Sonar from coming up for a clean audio reset.  Then it can be fixed.
 
My example clearly is to just illustrate how Sonar SHOULD behave, when the drivers are removed from the system.  Sonar has to recognize the problem correctly, not just exit.  Got to get there first, before Creative drivers or any others could be of any use ...

Just curious, if you have renamed or deleted the Sonar Platinum aud.ini file, does it re-create one before it crashes on startup?
 
If it does it would be interesting to look at the file in an editor to see what it contains ...
 

booksmusic
Chuck,
I've tried both those suggestions: the control start tried to initiate but I got this message: "Your personalization process didn't complete. You may have canceled the copy...Please redo the personalization if necessary." I don't know what that last live means.

try re personalizing sonar again.
hold down CTRL while opening Sonar.
click yes to the pop up "would you like to re personalize Sonar".
this time go through all the steps. click yes, if your prompt with another window, select yea again.
 
im convinced this what you need to do.

I've tried the personalization process several times, always getting this message: "The personalization process did not complete. You may have canceled the copy or your disk maybe full. The application may not launch successfully. Please redo the personalization if necessary."
 
Don't know what's meant by "canceled the copy" but the disk isn't full, and the application does not launch, but gives the original "not working" message, and when trying to personalize immediately again, the same "not working" message comes up immediately.
 
I haven't deleted the other ASIO drivers on my system yet, but I'll try that next, nor am I ready to do a reinstall of Win10 and having to reinstall all my other software ... that's a big leap ... oh, where, oh where is Product/Tech support when you need them...
 
Meanwhile, thanks for the suggestions...

The full personalization process copies with overwrite the contents of "C:\ProgramData\Cakewalk\SONAR Platinum" into "%appdata%\Cakewalk\SONAR Platinum." My guess is that is the copy referred to in "cancelled the copy."

booksmusic
 
I haven't deleted the other ASIO drivers on my system yet, but I'll try that next, nor am I ready to do a reinstall of Win10 and having to reinstall all my other software ... that's a big leap ... oh, where, oh where is Product/Tech support when you need them...

When I pulled the ASIO drivers (aka: ASIO4ALL) off my laptop after setting Sonar up to use them, Sonar knew they were missing and asked me to fix them by choosing another driver.  But they were the last and only ASIO drivers on my system, so Sonar had to realize they were gone.
 
In your case, even though you have removed ASIO4ALL, I believe Sonar still thinks there are ASIO drivers in your PC.  But since the other flavors are maybe not exactly configured correctly now, Sonar encounters an error it cannot handle and exits.
 
Cleaning ASIO up is probably your best next step.  At least it shouldn't be too difficult.

scook
The full personalization process copies with overwrite the contents of "C:\ProgramData\Cakewalk\SONAR Platinum" into "%appdata%\Cakewalk\SONAR Platinum." My guess is that is the copy referred to in "cancelled the copy."

UAC issue maybe ?
 
forgot to ask the OP, are you running the latest version command center ?

chuckebaby
UAC issue maybe ?
 
forgot to ask the OP, are you running the latest version command center ?

IDK, it could be a permissions issue or some other disk access problem.