AD worked yesterday. This morning there was an automatic Windows update, after which AD came up with a "wrong computer ID" dialog.
 
It suggested running the Online Installer, but when I did it told me "everything is up to date". I attempted to re-register it, but it just told me "This Product Key is already registered to your account".
 
But after that the "wrong computer ID" message mysteriously went away. I did not re-install or re-authorize AD. It just got over it on its own somehow.
 
Just thought I'd pass this along in case anybody else runs into the same issue.

I found this on the XLN FAQ page:
 

If a product suddenly goes to trial mode, it means that something in your computer triggered a change in the Computer ID (perhaps a software or hardware update). This in turn deauthorizes your product. This is easy to fix:

Login to your user account and go to My Account -> My Computers

 
So I did, and it shows two computers registered, both identical. And it warns that "You currently have your maximum amount of active computers. Remove old unused computers if you need to register a new computer."
 
There was no indication which "computer" was current, so I click the Edit button to see if maybe there was a datestamp. There isn't, but they do show different computer IDs. I was able to match one of them to the current computer ID (click on the Addictive Drums logo for the About page) and delete the old one.


I hate this kind of copy protection. A few years ago I had to replace my computer's motherboard, and half of my instruments and plugins had to be re-authorized. I'm sure glad hardware synths don't work that way.
 

Bitflipper,
 
Several of us here have had that problem after performing MicroSoft updated in Windows,  mine happened in Windows 10, but never in Windows 8.    I was glad I saw that same resolution while searching XLN FAQ page too.  I posted the resolution in the forums somewhere so folks could find, now I'm not sure if I added tags to the post, hhhmmm.
 
I'm glad it all worked out for you.

XLN is one of the more painless with this actually, as you can willy nilly deauthorize and authorize up to two machines. Even with numerous installations, it would merely limit to 2 computers at a time.

Just go to your XLN account and delete your old computer and add your new one... reinstall

mettelus
XLN is one of the more painless with this actually, as you can willy nilly deauthorize and authorize up to two machines. Even with numerous installations, it would merely limit to 2 computers at a time.

Yes.  I've always found XLN a breeze to work with.
 

Same thing happened to me after the Windows update yesterday. AD2 is now working OK, but I'm still tracking down the other changes Windows made without asking me; e.g., changing my default audio device.

bitflipper
I hate this kind of copy protection. A few years ago I had to replace my computer's motherboard, and half of my instruments and plugins had to be re-authorized.

I believe Microsoft/Windows uses a similar technique.
I build a new pc every 2 years and switching windows 8 to new PC was confusing.
IMO, The Mobo Security Protection function is not user friendly.

Yeah, I just got smacked with this too. I have several 3rd party plugins and virtual instruments and I'm hoping that AD2 is the only one that's been affected by this "anniversary" Windows update. Haven't had a chance to thoroughly test everything else yet.

Yes, I see that after the update my onboard audio interface had been re-enabled. However, I can't say that was the system change that caused XLN to calculate a different computer ID, because I re-disabled the integrated audio and AD came up without complaint.
 
I'm surprised at how forgiving all you guys are toward XLN. Yes, they do make the process painless (if your DAW is on the net) but I still fault XLN for basing their ID on components that Windows Update can alter. That's not a good design!