Hello my friends:
Given Cakewalk is releasing monthly updates with new and or enhanced features. Do you wait to install these updates or do you immediately grab them? What are your thought process?

Usually with any updates, unless it is to fix a critical problem or security loophole, I like to wait to see what others are reporting.
And also, Are Sonar monthly Updates sometimes "Fixes for Fixes?" 

With that said, I understand nobody is compelling me to install updates but given the frequencies of these releases, are these updates, sometimes, not-every time, fixing issues caused by previous updates?

In a nutshell I think I have a stabled system and I always get a bit nervous with updates.

I wait until I see something compelling that makes a difference or sparks an interest in implementing it into my workflow.  Also try to resist the urge to update while in the middle of an important song/project etc.
With this method I end up updating about every 2nd or 3rd update, which in itself makes it seem like a pretty robust update at that point. 
This is just my method.

KingsMix
I wait until I see something compelling that makes a difference or sparks an interest in implementing it into my workflow.  Also try to resist the urge to update while in the middle of an important song/project etc.
With this method I end up updating about every 2nd or 3rd update, which in itself makes it seem like a pretty robust update at that point. 
This is just my method.

me too, exactly the same

Hi. I download each month, because I like to check out new features.
But as mentioned, not in the middle of a project.
All the best.

My experience is if you wait too long with the updates, there are features of previous versions that are not installed in the newer updates. For example, I have the last update installed. The Adaptive Limiter was not installed. This one i had installed extra. 
I wonder how is that when I install sonar completely new. do I have to start again with my first version and then install every single update?
Would be awkward somehow.

Ever since the melodyne 4.0 debacle? Of may 2016, where projects would crash upon load if there was a melodyne clip, all early access update first hits my dev. laptop, and I closely follow the problem reports board. When it seems safe ill put it on the daw.

I've found that it doesn't really require all that much caution, if you use the command centre, as the rollback feature works really well.
 
I'll typically wait for a sensible break point in whatever work I'm doing before installing, and I never install the early access versions. The way this shakes out is that I've usually installed the official release within a week of it coming out. Have had very few problems with this approach, and only had to roll back twice.

I've found that it doesn't really require all that much caution, if you use the command centre, as the rollback feature works really well.
 
I'll typically wait for a sensible break point in whatever work I'm doing before installing, and I never install the early access versions. The way this shakes out is that I've usually installed the official release within a week of it coming out. Have had very few problems with this approach, and only had to roll back twice.

I usually update soon after its available but I often find that I have to restart my pc 5-10 times before the program loads correctly andI 'll often have to set up my hardware again, which is a drag.

I install updates as soon as they are available.
Sometimes I haven't always liked the updates so I have rolled back to finish projects.
But I will update every month and more often than not download the early release.
 
I've never had an issue of instability or crashes but I have had features I just don't care for until I learned them. IE- The PRV enhancements were confusing at first but now I really like them.