Addictive Drums: "wrong computer ID" after Windows Update

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.

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.

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

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.

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.

Blame Microsoft for delivering Windows Upgrades disguised as "security updates". AD honestly thinks you've upgraded your PC.
 
This is one of the reasons I have disabled Windows Update completely on my Windows DAW. I'm not particularly proud of that, but Microsoft's behavior with respect to Win 10 just makes me fume. I can't trust them not to release an update that removes features from the OS.
 
Seriously considering moving my DAW to a Mac when SONAR supports it.
 
 

I just hit the same problem today, thanks to Windows 10 update 1607.  I went to my XLN online authoriser and see that it's happened before as my existing '2 only' authorisations were for W10, when I went from W7, and a previous W10 update that knackered AD2.  I de-authorised the first one and requested authorisation for my new computer: 'Build 1607 Sep 16'!
 
I wonder what else has been broken....
 

I was also running into issues with Pianoteq audio dropouts (it's just a sim, no samples or anything) and although SONAR was running everything through my interface as usual, it turns out that Pianoteq had disabled my ASIO drivers and was instead running the standard Windows drivers. I'm assuming this was also due to the Windows update. 
 
I agree that Windows shouldn't be updating things that are going to mess up existing hardware/software configurations, so that is frustrating. But on the other hand, none of my hardware changed and my computer ID remained the same, so you'd think AD2 wouldn't be recognizing it as a different computer. 
 
Frustrating all around. I was really digging Windows 10 up to this point, now I'm a bit more concerned about what the future holds if they continue to do updates like this. For people just using a PC to surf the web, watch YouTube and check email, I'm sure there are no issues. But folks like us who've invested a bunch of money into hardware, plugins, virtual instruments, etc. and have to keep everything talking together...man. We need OS stability.

bitflipper
 
 
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!

This.  No reason an update to the OS should stop the software in its tracks, not related to a total hardware overhaul.

the Win Anniv update was not good to me when I did it a few of months back.  I'm a Windows Insider (current build 1607 1493.187) so I get some early updates.  I've had to install many programs and VSTs, some had to be reregistered.  My XLN account had that glitch, but it also corrupted some installer files that took them a week to fix the issue.  I've had some Win updates since then that required some form of authentication or registration to repeat, but they work fine afterwards... just a pain to manage all of the licenses for waves, XLN, cake, IKM, and others that are not a permanent user authentication.  I won't even buy anything with ILok... just one more thing to deal with.  

fret_man
Moving to a Mac? That's even worse. There are quite a few VSts that stop working when a new OS comes out. At least you have a work around instead of 1) upgrading and waiting until the manufacturers update  or 2) don't upgrade yet. Then again, at least you have the choice to not upgrade.

Not my experience. Put Sierra on my DAW Macbook yesterday, the last of three different spec Macs I've upgraded. There are problems with plugins from certain developers, including some very big ones that seem to have not being paying attention, but none that affect me.

A bit to my surprise, everything works. Needed to disable the pestilential Siri and switch unwanted "store loads of stuff in the cloud" settings off and that was pretty much it. At least unlike Win10 it didn't let me disable functions, including privacy-related one, during the install process only to quietly switch them on again at first boot and again after updates, Aqua looks and works like it did before and everything's where I expect it to be.

I've used MS operating systems from MSDOS6 onwards, but Win10 as it currently operates is the step too far for me. The last time I recall Windows updates causing as many problems as Win10 updates seem to is XP service pack 2 when MS finally bit the bullet and clamped down on the security and user account permissions stuff, which broke quite a lot of software that had been developed outside MS's recommended guidelines.

Apple have it relatively easy of course, because they only have to code for their own limited range of (expensive) hardware, not for a myriad of combinations of third-party components. And they still have security issues at times and bugs and compatibility problems, but the law of large numbers means that once any software is rolled out over tens of thousands or millions of computers stuff the developers and testers missed is 99.9% likely to turn up. In the end, just as with cars, instruments and washing machines it comes down to what you prefer, what you need a computer to do and the available budget.

I gave up using Waves because of these issues. And I bought something with iLok which, upon the first time it caused me issues, I have not touched since.

It can be bearable if the fix is simple, but the moment the steps get convoluted or don't react the way you expect then I just move on to something else.