So are other DAWs experiencing these problems? If not this being a Windows update problem doesn't really wash does it?

I sure hope so! I'm in the middle of a Christmas song and would like to get it done before Christmas!

AAS Player keeps crashing mid- recording usually. I try to protect things by freezing the track but then SPlat crashes completely while rendering.
Lounge Lizard LP-4 records nicely for about 30 seconds and then goes completely nuts! As you play your keyboard, the plugin starts to play odd weird notes way outside its normal range and then seems to get stuck playing a scale 3 or maybe more semitones lower or higher! You can sometimes save that take and just delete the rubbish and build that way. I have started to use stock CW instruments to record then swap in the plugin you need. Not good. Merry Xmas.

Again, an update would be nice from Cakewalk. The silence is deafening!

Win 7 is also showing some issues. Sonar is very slow, and sluggish...after both of the recent updates.

At this point in time, my entire music production is paralyzed. Maybe due to Windows 10 updates, or Sonar updates, or my Saffire Pro 14 audio interface.  I'm devoting today to trying different things on different equipment to eliminate possibilities. Symptoms are:
 
After closing Sonar, all sound from video or games is delayed.
Using Battery 4 in Sonar, all samples are delayed.
Opening 50% of my plugins causes the audio engine to crash.  Sometimes it can be restarted, usually requires restarting Sonar.
Bouncing clips causes the audio engine to crash sometimes. Starting playback can cause the audio engine to stop.
Sonar freezes at random.
 
Trying to use Sonar is very frustrating right now.  I hope I can get this worked out without buying a new interface or DAW.

I use the v studio 100  controller and since the update to nov. update the marker control does not work

I’ve never used 2016.11. I was using 2016.09 when this all started about 2 weeks ago. All of a sudden out of the blue, I got a runtime error, which I've not seen as far back as I can remember. I reverted my C drive back to a previous image file from 10/23 and to my surprise, the problem resurfaced again.
 
After much time and testing,  I traced it back to me having an internet connection. When I disconnected the internet and reverted back to an old image, I wouldn't get the runtime error. After reconnecting to the internet, I got the runtime error about 30 min later. Once you get the runtime error it’s like a virus, the only fix is to revert to an old image and stay off the internet.
 
Last Saturday and Sunday I did lots of extensive testing with some old image files and never had any runtime errors, even though I was connected to the internet. Yet on Monday the runtime errors came back. I have Win autoupdates turned off. What is MS doing to our computers?

This is exactly the scenario I've feared since Microsoft first instituted forced updates: a bug that cripples millions of users in one fell swoop.
 
It's happened before, but MS has always jumped on the problem and fixed it in short order. Unfortunately, like the power company fixing downed power lines after a storm, MS must prioritize by first addressing whatever issues affect the greatest number of users. Those of us running specialized applications are like the homeowner on a cul-de-sac who's last to get his power restored.
 
 

I just hate the forced update idea. I can understand some part of it, however, it should still be able to choose wether I want to update or not.... Annoying as FXXK! I really don't want to go back to a prevous version of Windows 10, to much hassle