Tried without fast boot - problem still the same: SONARPLT.EXE crashes on project load
 
@Bristol_Jonesey: to set/unset fast boot: go to Control Panel / Power Options / "Choose what power buttons do" / Click "Change settings that are currently unavailable" / (un)check "Turn on fast startup" / save

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?

In my setup I've now been able to reproduce the problem multiple times and have a workaround (may not work for others)
After a PC reboot: start Sonar: first project load fails.
Workaround: load project in safe mode and confirm every plug-in one by one - slowly (clicking "yes to all" crashes Sonar as well as clicking too fast) ==> this way the project loads and is fully functional (in my setup)
Further project loads of the same project are successful (not saved, just exited the project or Sonar).
Restarting Sonar: project still loads fine. Rebooting the PC: load fails again.
 
... pretty weird 

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.

DeeringAmps
Are these problems all unique to Win 10?
I don't seem to be having issues with Win 7x64 (studio) or Win7x86 (office).
 
T

I think that these issues seem to be unique to Windows 10, as far as the posts in these threads would indicate.  So far I have not seen one post from a Win 7 or 8 user having a problem with the latest Sonar update.  But some folks don't list their system specs in their sig, or in their posts, so it's not an absolute certainty.
 
But not all Windows 10 users are affected.  Some are running fine! 
 
I have seen issues posted from Win 10 users that are completely up to date with Microsoft updates, as well as those that stay offline and have not updated recently.

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...

...at least I do not have to wonder why since a few days Sonar, when opening the last project, first stops loading with a little popup saying "Sonar.exe doesn't work anymore", so I close it, and go again. Then it works, but sometimes it seems unstable. Hoping that the next updae will clear that. 
Meanwhile I am about a piece for which I use Sibelius, because I need the full orchestra, and precise notation. 

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

Been acting weird for me, too. Crashing inconsistently. Sometimes seems after one crash it does okay until rebooted. Up to date windows as of 11/9/2016 no problems until splat 2016.11

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