I ran into this yesterday ... ProChannel GUI not redrawing properly after inserting the new Style Dials, but only in the bus section of console view, not in the track section ... of course, instant reaction: d**n ipswich ... but after doing win7 updates (which surprisingly found a pending graphic driver update) it's all back to normal ...
 
so I reckon there is truth in what the doctor says and windows needs those updates eventually ...
 
https://www.dropbox.com/s/62btrgstc4650cz/Capture-BusReDrawProblem.JPG?dl=0
 

 
 

And that could be coincidence, I myself go a couple of years (2 give or take) between computer rebuilds, never update anything Windows or graphics drivers, mother board drivers, bios update or anything like that past what is there at build and install, never had a trouble, always run as solid and fast. Only install program and plugin updates, that type of thing.
 

Not every issue is a Sonar issue
 

and on flip side not every issue can be attributed to non Sonar things as some like to suggest. Some yes, some no. It's just software, not a girlfriend, no emotional attachment, I find better I go there. But been with Sonar a few orbits round the sun, Sonar 7 Producer.
 
Richard

Agree with both post...

Of course not, but this forum is awesome at trouble shooting even old guitar strings. ;-)

Richard Cranium
And that could be coincidence...
 

... and that might well be (despite being reproducible before and not after) ... but many things in life are coincidences (and that's a good thing) ...
 
anyway, I just dropped that initial post because every time there is an upgrade people (me included) think that everything worked better before, sometimes not even trying hard enough to check thoroughly (guilty here as well) before using inappropriate words ...
 
BTW: I try to limit win update intrusion to 3-4 times a year and other updates to slower periods

Its a common assumption that the most recent change to a system is the direct cause of any adverse event. While this is true and a good start for troubleshooting, its just that - a start. You have to go through a full process of elimination to detect the root cause. As engineers we go through this process pretty much every time we fix a bug so its second nature to us.
With DAW's its a complex ecosystem of dependencies, so sometimes a harmless or even positive change in the DAW can expose a problem elsewhere, in a plugin or even in an unrelated feature. Regression testing finds a percentage of these issues but some may not be visible until very specific operations. And sometimes like you said, its simply coincidence that a problem occurred after an update and completely unrelated. Everytime we release an update there are some cases like this.

Noel Borthwick [Cakewalk]
Its a common assumption that the most recent change to a system is the direct cause of any adverse event. While this is true and a good start for troubleshooting, its just that - a start. You have to go through a full process of elimination to detect the root cause. As engineers we go through this process pretty much every time we fix a bug so its second nature to us.
With DAW's its a complex ecosystem of dependencies, so sometimes a harmless or even positive change in the DAW can expose a problem elsewhere, in a plugin or even in an unrelated feature. Regression testing finds a percentage of these issues but some may not be visible until very specific operations. And sometimes like you said, its simply coincidence that a problem occurred after an update and completely unrelated. Everytime we release an update there are some cases like this.

This! Basic example. Take a DAW that put in some workaround code because some MS code is buggy. In the pure sense this should not happen and is bad practice (MS should fix it), but DAW manufacturers often have to help along otherwise they will lose customers.

Now MS fixes the issue and the DAW no longer works. Why, because the DAW manufacturer still has that workaround code, the DAW is now bugged. So now they have to strip that code out.

Then consider some users haven't run windows update so some of the DAW userbase experience the issue and some don't. Then consider some people are offline only but still update their DAW (they are going to get it worse).

Ditto copy/paste/repeat with DAWs/drivers/plugins.

Well written, Doktor