Recent SONAR Issues with Virtual Instruments

Has anyone else experienced some unexpected behavior within the last day or two?  I have a project that's running Addictive Drums 2 and Pianoteq. Three days ago I was tooling around with the session, no hiccups whatsoever. Then today I loaded up the project and during playback, I was getting audio dropouts from Pianoteq. Pianoteq showed an error message stating my CPU was overloading. (Task Manager showed it peaking at 15%.) The CPU meter in SONAR was barely moving. I've got an i7 6700K processor so I'm pretty sure that's not really what's going on. Whether I'm playing back a pre-recorded MIDI track or playing live, Pianoteq keeps dropping out.
 
Then I noticed that Windows had an update for me, so I figured maybe that was the issue. So went through the update (apparently it's an anniversary version of Windows 10 and they put Edge back into my taskbar...sneaky buggers!) and relaunched SONAR. This time I got an error message from Addictive Drums stating "wrong computer id" and that I had reached the maximum number of computers. I've got AD2 installed on my desktop and my laptop, and I've never received this error before. Plus, I'm allowed to install it on two computers, anyway. When I launch the XLN Online Installer, I can't access anything because it takes me to a page prompting my to deactivate on of my computers. Logging into the XLN website, it too is only showing my two computers, so there's no indication that I've attempted to use it on more than two computers (which I haven't).
 
After acknowledging the AD2 error message, the project loaded fine and AD2 didn't seem to be affected (i.e. it was playing back audio as it should.)
 
I do have messages out to XLN Audio and Pianoteq, but considering that these two problems both popped up around the same time (and could possibly have been affected by the Windows Update) I'm wondering if anyone else has noticed similar behavior??

scook
The AD2 issue is not new. It happened to users when upgrading to Win10 and applying the anniversary update. These updates change the PC in a way that cause the AD2 copy protection scheme to think the program is on a new machine. The fix is dropping and adding the PC on the authorized list using the XLN installer.

Got it, thanks. Did just that and everything is back to normal as far as AD2 is concerned.