mcdonalk
However, based on my observations both in this forum and with Sonar on my PC, I regret to say that I suspect that the monthly update model does not allow enough time for thorough regression testing.
Lance Riley [Cakewalk]
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.
I suppose this could imply the same thing for Microsoft's monthly cumulative update model.
If one fails to make a regular backup image, in order to have have something to fall back on, well ...
If one cannot afford any downtime or interruptions to your workflow, why update your main DAW with just released software, without testing it first. How could Microsoft or Cakewalk test every specific PC config for full compatibility? In the Windows ecosystem, there is a nearly infinite number of variables in end user setups.
In the business world it's referred to as disaster recovery. It's the customer's responsibility to be prepared for anything going wrong in their operational environment. Sooner or later something will break, no matter how well you are prepared.
The software development model has changed. It's called agile development, so it's time to accept that and protect yourself. Or live with the consequences.
https://en.wikipedia.org/...e_software_developmentAgile software development describes a set of principles for software development under which requirements and solutions evolve through the collaborative effort of self-organizing cross-functional teams. It advocates adaptive planning, evolutionary development, early delivery, and continuous improvement, and it encourages rapid and flexible response to change. These principles support the definition and continuing evolution of many software development methods.