When this issue first arose, as usual I went a-googling for additional information. And found none. No bulletins, no emergency patches, no discussion on gaming- or audio-related forums. Usually you can count on gamers to get vocal about even minor O/S inconveniences. But nuttin'. 
 
From reports on this forum, it seems to be specific to Win10. Folks who pre-emptively stayed on Win 7 or 8.1 (nobody stayed on 8.0) aren't seeing the problem. "Interoperabilty issue" is a good choice of words. It's what you say when two programs are fine on their own but cannot work together. Even though the problem isn't entirely within SONAR, my guess is the fix is still going to come from Cakewalk, not Microsoft.
 
I'd love for Noel to drop by and give us a technical explanation, but he's probably pretty busy right now.

bitflipper
When this issue first arose, as usual I went a-googling for additional information. And found none. No bulletins, no emergency patches, no discussion on gaming- or audio-related forums. Usually you can count on gamers to get vocal about even minor O/S inconveniences. But nuttin'. 
 
From reports on this forum, it seems to be specific to Win10. Folks who pre-emptively stayed on Win 7 or 8.1 (nobody stayed on 8.0) aren't seeing the problem. "Interoperabilty issue" is a good choice of words. It's what you say when two programs are fine on their own but cannot work together. Even though the problem isn't entirely within SONAR, my guess is the fix is still going to come from Cakewalk, not Microsoft.
 
I'd love for Noel to drop by and give us a technical explanation, but he's probably pretty busy right now.

thanks dave, i too would like a technical explanation (if only because i have win10, etc etc, but am not seeing the issue)  - "interop issue" is still rather vague as an explanation (a bit like "the key doesn't fit the lock")
(edit to add, i did read your debugging/troubleshooting posts)

I'd appreciate an update.. Will the fix be coming in a week, a month..?

pwalpwal

John

pwalpwal

John
What timing bug? 

how would you better describe it? (i'm assuming you weren't just trolling me)

I know of no Windows bug timing or otherwise. One could be there I just haven't heard of it. Hence the question. I still am not seeing any evidence of a bug. I don't troll. 

do you read these forums? check sander's link? you are a "host" after all, your input should be useful, shurely?

I asked the question before the "link" was posted. Further the link does not link to anything. I have read a ton of things about crashing and problems since the Sonar update. I don't know of any confirmed bug report about Windows. I have not had any problem with Sonar or Windows. 
 
There has been some speculation as to why this update is a problem for some and not others. But no one that I have read has reported a timing bug in Windows.  

oh ffs

quote from lance's post, linked by sander above, and discussed in other threads before lance posted, "We are able to reproduce the issue and it appears to only affect some systems since it is timing related."

I know all about interoperability issues. I'm a bass player.
 
On a good note AFAIK I'm on the latest Win 10 update and have not experienced any of the problems reported by other on this forum.

Here is what Lance said in a separate post:

Instability with certain Cakewalk plugins after recent Windows 10 updates

It has come to our attention that a recent Windows 10 update has introduced instability in a subset of our plug-ins and may cause SONAR or other Windows DAWs to crash. The problem is related to a change in the timing for thread initialization on Windows, which leads to intermittent crashing on project load, plug-in scanning, or adding these plug-ins to a project. We are able to reproduce the issue and it appears to only affect some systems since it is timing related. We are actively working on a resolution and will release fixes to the affected plugins as soon as possible.
 
So yeah, calling it a timing issue is entirely appropriate. 

John

pwalpwal

John

pwalpwal

John
What timing bug? 

how would you better describe it? (i'm assuming you weren't just trolling me)

I know of no Windows bug timing or otherwise. One could be there I just haven't heard of it. Hence the question. I still am not seeing any evidence of a bug. I don't troll. 

do you read these forums? check sander's link? you are a "host" after all, your input should be useful, shurely?

I asked the question before the "link" was posted. Further the link does not link to anything. I have read a ton of things about crashing and problems since the Sonar update. I don't know of any confirmed bug report about Windows. I have not had any problem with Sonar or Windows. 
 
There has been some speculation as to why this update is a problem for some and not others. But no one that I have read has reported a timing bug in Windows.  

I'm glad you're not experiencing any problems. That's awesome!  Unfortunately, some of us are seeing the issue so we're eager to see what the next steps are.. 

Please understand that is not confirmation of a bug. That is as it states speculation. "It Appears" is used. Jumping to conclusions about it is premature. As far as I can see CW is seeing an issue and is looking into it.
 
I fully understand the wish to have any issue solved as soon as possible but we don't know as fact what the problem is yet.