It doesn't seem so, I'm using W10x64 (Build 14393.447) without any problems (so far).

Songroom

Bristol_Jonesey
Just to add to the confusion, I noticed in the CCC that ehre was an update to the "Cakewalk Loopmasters Content Collection"
 
I have tried to update it several times but keep on getting this message:
 

 
Does anyone have a clue what this means or how to fix it?
 
 
Cheers.

 
I found this on the Microsoft forum...
 
Microsoft Forum
https://goo.gl/PQ1L5L
 

Thanks Paul, I'll check this out later on

Well, my headaches continue. I've done 3 system restores to different dates and now Sonar won't open any projects. I've reset VSTs and rescanned as well. I can't roll back either. When I try, CCC tells me
 
"Setup has detected that your application is currently running. Please close all instances of it now, then click OK to exit."
 
There are no instances of sonar running in task manager. I've rebooted and tried to roll back several times with no luck. Sort of stuck on ver 10 after 1 successful roll back from ver 11. All the problems started after I updated to ver 11 in the first place. My faderport also craps out (no memory etc...I have 16 gigs!) Version 10 was rock solid before this last update (as were all the other updates since splat came out) At least I'm not alone in my misery but that's not much comfort. Hopefully there will be a magic patch and we can all get back to making music soon.

Bristol_Jonesey

Songroom
This is a long shot, but are any of the users experiencing issues using Windows 'fast boot' ?

I wouldn't know what fast boot is or how you would go about using it.
 
I just switch my pc's on and let them do their thing

'When Fast Startup is enabled, your computer doesn’t perform a regular shut down. Since applying new system updates often requires a shutdown, you may not be able to apply updates and turn your computer off. Restart is unaffected, though, so it still performs a full cold shutdown and restart of your system. If a shutdown doesn’t apply your updates you should use restart to complete installation'.  (howtogeek.com)
 
I've only mentioned this as 'fast start' causes plays havoc with my system, hence I've disabled it. It may explain why Windows update installation requires several restarts for some users. Saying that, I've just noticed that you're using W7 which, as far as I know, doesn't offer a fast start option.

Bristol_Jonesey
So far I've only installed it on my laptop.
 
I've now rolled back to the October release
 
Symptoms last night:
 

• Plugin Manager stalling during a Rescan (Yes I did a reset). Always seem to stall on either Rapture Pro, Rapture Session or Z3TA+2
• Failure to find existing plugins, even when on the rare occasions that the rescan "finished"
• Crashing when loading any 32 bit plugin (I get the "Sonarplt.exe has stopped" working message)

 
Rolling back has cured every problem.
I'm so glad I always install updates on this laptop which is purely for testing purposes
I might wipe SONAR entirely from it and do a clean install later on

You mentioned that you had only tried this new Sonar update on your laptop.  You sig shows that your DAW is running Win 7.  What Windows version is running on your laptop?

Songroom

Bristol_Jonesey

Songroom
This is a long shot, but are any of the users experiencing issues using Windows 'fast boot' ?

I wouldn't know what fast boot is or how you would go about using it.
 
I just switch my pc's on and let them do their thing

'When Fast Startup is enabled, your computer doesn’t perform a regular shut down. Since applying new system updates often requires a shutdown, you may not be able to apply updates and turn your computer off. Restart is unaffected, though, so it still performs a full cold shutdown and restart of your system. If a shutdown doesn’t apply your updates you should use restart to complete installation'.  (howtogeek.com)
 
I've only mentioned this as 'fast start' causes plays havoc with my system, hence I've disabled it. It may explain why Windows update installation requires several restarts for some users. Saying that, I've just noticed that you're using W7 which, as far as I know, doesn't offer a fast start option.

Just for sake of completeness, I have SONAR installed on 3 different machines:
 

1. My Daw which is Win 7
2. My laptop, Win 10
3. General purpose pc also Win 10

My problems yesterday were confined to the laptop under Win 10.
Today I ran the update on the general purpose pc without any of the problems exhibited by the laptop.
It did have a problem recognising Rapture Pro which need to be reinstalled before the VST scanner could pick it up.

Splat 2016 11 has been the best setup for me on my Win10 Pro laptop. I don't know why. I just ran a CA test and put it on many tracks in the ProCh and on the FX rack alone with many other plugins. its all running fine. The only thing that I can think of for me is that I'm using the WASAPI Exclusive setting with no interface to eat up my CPU.
 
also Win10Pro's last update was 11/9/16 and that was the last Win10 update. (I'm up to date) But I had updates off for a month so maybe there was an update that MS pulled that I didn't get.
 
If that helps anyone...

Today I haven't done anything (nor yesterday as I was very busy "away"), and everything seems fine, again!
How very weird.....
Michael

Updated, (on updated Win7x64-SP1),
No issues encountered with, loading Sonar, VST scan, opening projects older and newer, loading existing VI's and FX, (VST2 and 3), new synth rack (even loaded  a few CA-2A, in FX bins), CPU's run normal all seems to be functioning normally.
Not to intense but currently remixing an older project, currently 28 audio tracks, 4 VI's, 20 mix/fx buses, Neutron on 14 tracks and 10 buses, midi keyboards connecting/working, no functional issues encountered thus far mixing, but haven't really gone out of my way, to try new features or record anything yet, or in trying to find problems, but haven't run into any yet. 
 
So all seems well for me at this time.
 
Cheers  

If anything glad I bookmarked this forum location, LOL, I haven't ventured into the "kitchen" yet. 

OK, also did the MeldaProduction upgrades sometime after getting the LUFS Meter and today did the Cableguys updates..  Thought I had something amiss from all that, with more crashes and the audio engine stopping frequently. If things don't smooth out tomorrow, will roll back..

I was never able to get Sonar to work with Windows 10. I'm still using 7, and haven't had any issues.

I rolled back to 2016.10 and still am having the same problem. One project (which was created in 2016.11) in particular always crashes sonar while loading the first time, but then will load the second time. If I put ca-2a in the pro channel (or fx bin - just checked) sonar crashes.
 
I'm not getting crash report offers - not sure if they need to be enabled - I've gotten them at the studio before but not here at home. I'm referring to Sonar asking if you want a dump report etc. upon crash.
 
Once they open everything seems fine, and a simple midi project I created after rolling back opens and runs fine. But try to insert ca-2a in anything and crash...
 
Against my better judgement I will try to open the project I created in 2016.11 that still crashes the 2016.10 rollback at home, up at the studio today on my main rig which has yet to be 2016.11'ed but IS windows 10 current.

bitflipper
For me, it's easy and reproducible. All I have to do is 1) reboot the machine and 2) insert CA-2A into an FX bin (or open a project that already contains CA-2A in an FX bin).
 
Not everyone's experiencing the same symptoms, though. For example, I have no problem doing a scan.
 

Same results here.
 
(FWIW) Plugin count significantly increased after update.  Discovered the "C:\Program Files (x86)\Cakewalk\Vstplugins" had been added to VST scan path after update.  Deleted path, rescanned, plug count as expected.