No dought something changed! And updated! And my life is allot easier. From what your saying it sounds more like a windows 10 update. But what's crazy is it only effected Sonar.

And at this point, it really don't matter as long as everything works as expected.

robert@gmwmusic.com
No dought something changed! And updated! And my life is allot easier. From what your saying it sounds more like a windows 10 update. But what's crazy is it only effected Sonar.

And at this point, it really don't matter as long as everything works as expected.

I have auto updates disabled and Control panel doesn't show any updates from MS. I'm wondering if  MS is interacting with my computer in another way, possibly a internet database that we all connect to or something. This is really a mystery why all of a sudden it works. Did your sudden fix happen on Tuesday?

@gmp
 
Not sure what "internet connectivity" means exactly vs. specific OS or application s/w updates but there was a recent Win10 Pro update on this system (more than a couple days ago) before I decided to try release 2016.12 two days ago. The simple test project passed the test and so far the money projects are all opening/running with no issues, with the GUI appearing to be much "snappier" (responsive).
 
Please note this is -without- updating to the "early releases" announced for the two CW VSTs (no time for beta testing at the moment.) Of course, that will be the first thing I try if I run into problems again.
 
This is pure unqualified speculation on my part, but perhaps in your case, given the "timing issue" noted by the CW devs, there is some "timing issue" as a result of running the network drivers on your PC. By disconnecting, you may have changed the state just enough to make a difference. 

Since I can't claim any specific action on my part to restore performance other than what was mentioned in my update, I'm going with the elves.
 
Happier holidays.

gmp

robert@gmwmusic.com
No dought something changed! And updated! And my life is allot easier. From what your saying it sounds more like a windows 10 update. But what's crazy is it only effected Sonar.

And at this point, it really don't matter as long as everything works as expected.

I have auto updates disabled and Control panel doesn't show any updates from MS. I'm wondering if  MS is interacting with my computer in another way, possibly a internet database that we all connect to or something. This is really a mystery why all of a sudden it works. Did your sudden fix happen on Tuesday?

 
"Any sufficiently advanced technology is indistinguishable from magic"
-Arthur C. Clarke

jackson white
@gmp
 
Not sure what "internet connectivity" means exactly vs. specific OS or application s/w updates but there was a recent Win10 Pro update on this system (more than a couple days ago) before I decided to try release 2016.12 two days ago. The simple test project passed the test and so far the money projects are all opening/running with no issues, with the GUI appearing to be much "snappier" (responsive).
 
Please note this is -without- updating to the "early releases" announced for the two CW VSTs (no time for beta testing at the moment.) Of course, that will be the first thing I try if I run into problems again.
 
This is pure unqualified speculation on my part, but perhaps in your case, given the "timing issue" noted by the CW devs, there is some "timing issue" as a result of running the network drivers on your PC. By disconnecting, you may have changed the state just enough to make a difference. 

Since I can't claim any specific action on my part to restore performance other than what was mentioned in my update, I'm going with the elves.
 
Happier holidays.

I do have 2 other computers in my network one is a Win 10 computer, last time it got updates was 11/14. The 3rd computer is an XP. I did try a test with the other 2 computers turned off and my DAW with an internet connection and still got the runtime error. So that appears to rule out the networking theory.
 
I'm glad things are better for both of us, I just can't help wanting to figure what went wrong and know why this happened to my system and no one else has chimed in that they had a similar experience.

It did and yes it's crazy! Does make your wonder?

robert@gmwmusic.com
It did and yes it's crazy! Does make your wonder?

Thanks for chiming in, Robert. I feel like I've been alone in my situation. I'm one of the few that developed problems without updating to 2016.11. Can you please let me know if you had the same experience I've had with the problem surfacing out of the blue, without me changing  anything and then going away out of the blue with no changes from me?
 
I have many posts in many threads all on this topic. I reviewed your posts in this thread and don't’ find any info from you what specifically was going on. Is there another thread when you explain what happened to you?
 
Thanks for any info. This whole experience has been unnerving. In the past when I run into a problem I can always revert back to an earlier C drive image when things were stable.

Actually I started by communicating directly with tech support. Sonar would crash when I first opened. I had to open more than once. Also I had to stop using my ASIO driver, it wouldn't work at all. And I just had other weird problems. Like when I bounced to a stereo track sonar would add two more tracks a left and right channel track. Also couldn't get sound from my midi controller or virtual controller. Crazy, I have been using cakewalk almost from the very beginning. I still have disk 1.1 and never seen anything like it. So it was hard for me to look at anything else sense I wasn't having any problems with anything else. And now everything is fine. And believe me I've tested it, it's been fixed. I was sure it was the cakewalk update that resolved the issues. Now after reading your post I don't know what to believe. But I'm happy that me and you; are back to work!

robert@gmwmusic.com
Actually I started by communicating directly with tech support. Sonar would crash when I first opened. I had to open more than once. Also I had to stop using my ASIO driver, it wouldn't work at all. And I just had other weird problems. Like when I bounced to a stereo track sonar would add two more tracks a left and right channel track. Also couldn't get sound from my midi controller or virtual controller. Crazy, I have been using cakewalk almost from the very beginning. I still have disk 1.1 and never seen anything like it. So it was hard for me to look at anything else sense I wasn't having any problems with anything else. And now everything is fine. And believe me I've tested it, it's been fixed. I was sure it was the cakewalk update that resolved the issues. Now after reading your post I don't know what to believe. But I'm happy that me and you; are back to work!

Thanks Robert for the update. What version were you using when all the problems started? 2016.09? or did it start right after updating to  2016.11? And was it 2016.12 that fixed everything?
 

It did start with me using 2016.09. I updated to 11 hoping it would fix it, didn't. I seen all the fixes for sure after 2016.12. However I'm not totally sure that's what fixed it. I was limiting my use of cakewalk, because of the problems. I turned back to my Roland 1680 so I'm not completely sure about the time frame when it was
completely fixed. I started testing again after update .12 and found all was well.