Windows 10 has updated and I am unable to use Addictive Drums or Keys what now?

How do I get around this issue?
 
Thank for advice...

This just happened for the 3rd time in a a week. Go to your XLN account and delete all your registered systems. Load the XNL installer and authorize your computer.

Had the same issues too and same fix's. But I had one 'extra' unwanted hassle. Win10 update did not complete the install flagging a system partition failure. And my PC ground to a halt with all sorts of errors and SONAR crashing on opening any project, driver failures etc. After finding some answers, I downloaded a free partition management app that allowed me to decrease the disk usable partition size and increase the system partition size, which fixed everything, but left the drive with a new ID, and having to re-authorise everything. All good now. Just posting this in case someone else comes across it. Make sure you backup before going down this route. cheers. Dave.

1. It's not an xln issue it just uses the unique I'd for the computer that Microsoft creates, as Windows 10 gets updated with a new build version the Id changes incorporating the version hence the issue. The same problem will occur if for instance you changed your motherboard that's how Microsoft track pirated versions of Windows.

Thats because other software uses iLok or other methods to license software. You cannot blame XLN for not knowing that microsoft would release new build versions of windows 10 instead of just updates like previous windows, alhough 8.1 was perhaps a warning of what was to come,thus invalidating the hardware key.
It only takes a minute to reset on XLN and personally I prefer it to ILOK which presumably would be there alternative.
 

I wish I would of had some warning of this update I thought they had done all the updates.. Yet I do not know what is new for this update all I know is that Cortana is more intrusive than it was before I turned it off. Now that it is off it still resurfaces asking me questions wish it would just Pee Off!!!

 My issues are usually network related. Turn off password protected sharing is broken.  I usually have to do the network credentials again and so far I've been lucky remembering those passwords.  Eventually you find other things that was reset.   The evolving OS was an Apple thing and now Windows users get screwed as well. I got an email alert from some developer not to use the latest Mac OS because of compatibility issues.

tenfoot

kitekrazy1
 Eventually you find other things that was reset.   The evolving OS was an Apple thing and now Windows users get screwed as well.

Indeed. It really isn't too much of a mystery why many people are desperately clinging to Win 7 for their professional DAW's despite the slight performance improvements in Win10.

Well, to each their own I suppose. I vastly prefer W10 to W7 and feel it MS is generally in a good place and going in a good direction with it. It's been more stable and fluid and clean to work with for me than any previous Windows, and that's on multiple machines. Older machines, for that matter, that were never designed to work with it - but even my old unsupported hardware is still ticking merrily along. The updates have been low-impact, easy and free. Not sure what's to complain about really. 
 
Mind you, I was also one of the rare strange folks who liked W8, and 8.1 even more. But I like 10 more than any of them. For me it's been consistently pretty pleasant and rewarding with iterative improvements - kind of like my Sonar experience at this point. So I'm always a bit mystified when people go off on MS like they're some terrible company with incompetent coders and an awful product (why do they keep using it then? there are alternatives!)... Sure there are hiccups along the way, as with anything, especially an OS of such mindblowing complexity, that needs to run on a functionally infinite range of hardware and software that is out of the company's control. So the fact that it works as well as it does is, to me, almost miraculous. Not to mention that the amount of money I've actually paid MS for all of this, over the last 20 years or so, is vanishingly small compared to what I've spent on other software that I use less and that does less, and is buggier much of the time into the bargain. 
 
So for me the minor inconvenience of updating my XLN authorization on two machines, which took about 5 minutes total, is a rather small price to pay for keeping current with what is now a clean, robust and modern OS. I'll happily do it again next time MS posts a major update!