I had the Creator update done last week (12-5-17). I was running the latest Platinum. I did the AD2 stuff fixes, no problems there.
By last Friday I thought I was good to go, I backed up all of my SSDs for Win 7 and Win 10. The only thing that changed was Sonar started locking up after a few takes in the comping lanes. So I rolled back (all of my machines)
to the previous version of Sonar and re-backed up my SSDs.
  I`m not so sure that the "last Sonar" edition was the keeper I wanted for my backup drives.
 This week is going much better. My Win 10 and Win 7 (intel) machines and my 2 other AMD (machines) appear to be working flawlessly. I hope I can keep my favorite DAW in working order for years to come.
  If there is an update from MS, I do have backed up drives to go back to if needed.
( BTW: my restore point Win 10 made was over 25gig, UGH) MY SSDs vary in size, so I had to be a little careful.
 
 Do yourself a BIG favor, get some backup drive tools and save your current Windows and Sonar configurations externally. In the last 3 years, twice I had to refer to them (power supply died, Video card was junk, etc.)
 
 I still love our Sonar,

I did the updates on both my machines, and had to uninstall/reinstall my audio drivers to smooth playback on my desktop. And I had to reauthorize addictive drums because the computer ID changed. I don't know why MS does that... anyway, all good. 

No problems here. Just the AD2 prob. Using a Focusrite Saffire Pro 40 and everything OK. 

Update went smooth and all works.

I have had it running for almost a month. Smooth sailing other than the AD2 and AK Id fix.

Had to un/re ad2, and disable hd audio in dev man. Now all's well… 

Mine updated this morning. I hadn't started Sonar for a while but now it will not launch and gets an error complaining about msvcp140.dll not being compatible with windows. I know the file is not corrupt because it is the same as the one on my other computer.
 
I also changed my graphics card today (and I'm not changing back). I thought that might have been the root cause until I read someone's post in another forum with the same problem.

It messed up my 24/96 drivers I lost the ability to change the sample rate.
 
I have had this before but this time a repair did not work I had to uninstall and reinstall 6.0.8 now everything is alright.

it will not launch and gets an error complaining about msvcp140.dll
 
That's caused by a glitch in your C++ 2013 redistributable package. Just go Microsoft's website and download the latest version. It will give an option for repair on install, choose that for both the 32 and 64 bit versions, reboot and you should be fine.
 
 

W10 reconfigured the drivers for a Zoom interface automatically, so I didn't have to reinstall them. So far, so good.