dotonemanband Posted February 11, 2019 Share Posted February 11, 2019 After the latest windows update (yesterday) I get this notice when opening Cakewalk … "Wrong Comuter ID. Possible problem with authorizantion. Please make sure that your host is not run in compability mode. If this is not the case run the XLN Online installer to authorize and likewise check that it is not run in compability mode. " What is compability mode and how can I correct this? Cakewalk wouldn't open Addictive Drums 2 as an example. Link to comment Share on other sites More sharing options...
msmcleod Posted February 11, 2019 Share Posted February 11, 2019 This is a known issue with Addictive Drums. Every time you do a major Windows update, you have to un-authorise and re-authorise your computer using the XLN installer. Link to comment Share on other sites More sharing options...
scook Posted February 11, 2019 Share Posted February 11, 2019 https://www.xlnaudio.com/support/my-product-is-suddenly-not-authorized-wrong-computer-id-or-this-instrument-is-in-trial-mode 1 Link to comment Share on other sites More sharing options...
Midiboy Posted February 11, 2019 Share Posted February 11, 2019 Melodyne used to do that too, but I think they fixed that. Link to comment Share on other sites More sharing options...
kitekrazy1 Posted February 11, 2019 Share Posted February 11, 2019 I had the same issue with Audiomodern Riffer. Link to comment Share on other sites More sharing options...
abacab Posted February 12, 2019 Share Posted February 12, 2019 Major Windows feature updates will change your computer ID, so anything that relies on that may need to be reactivated. Link to comment Share on other sites More sharing options...
AB99 Posted February 12, 2019 Share Posted February 12, 2019 It knocked out my SPLAT. Not sure that I care though! Link to comment Share on other sites More sharing options...
sealesb Posted February 12, 2019 Share Posted February 12, 2019 Are you guys running Win 10 and if so are you logged in on a local account or on a Microsoft account? Our studio PC had somehow reverted to a Microsoft account recently and we had this problem with a few plugins. It took me a while to notice it had changed over as I had arrived when it was already booted up and being used. My home PC, with exactly all the same plugins etc is on a local account and has had no such issues. I remember switching it to a local account as soon as I installed Win 10 and have never had to re-register anything since then. I also made sure that all audio, midi and Daw connected software had full write permissions and changed the ownership to me! Write permissions are crazy on a Microsoft account. Worth having a look at I think. 1 Link to comment Share on other sites More sharing options...
dotonemanband Posted February 12, 2019 Author Share Posted February 12, 2019 Thanks everyone for your assistance. Yes, I had to re-authorize addictive drums at the XLN site. Link to comment Share on other sites More sharing options...
abacab Posted February 12, 2019 Share Posted February 12, 2019 (edited) I have had this happen several times while using a local Windows 10 Pro account. This is an issue with the computer hardware ID (fingerprint) being changed, and has nothing to do with the user ID. This makes it appear as if you are running on a different computer than that which was used to originally authorize with. Normally your hardware ID should only change if you have swapped some hardware, but unfortunately the major Windows feature updates do this as well. Edited February 12, 2019 by abacab Link to comment Share on other sites More sharing options...
sealesb Posted February 13, 2019 Share Posted February 13, 2019 Sorry I think we need to clarify this, "and has nothing to do with the user ID". Lets leave the Microsoft updates out of the equation for the moment because we know they can cause this type off issue as abacab correctly stated. Changing from a Microsoft account to a local account most certainly can cause this issue of plugins needing to be registered again also and it all depends on whether you installed your VSTs under a Microsoft account or a local account in the first place I think! It is to do with permissions.... a mind boggling Windows invention. Note this: A day or two after the latest update, switching from a Microsoft account to a local account disabled our copy of Addictive Drums instantly on the studio PC along with a couple of Izotope plugins. Just re register them and we were fine. These same plugins worked fine after the update with us. It was changing to local account which de-registered them. So all we were offering here was another reason for plugins needing to be registered again. It seems Windows update caused the original problem for dotonemanband and that's fine as he has it sorted now. But.....what we found was another reason for this issue and it should not be so easily dismissed, with all due respect to those who have posted on this, as it may sort the issue for other people. After all we are trying help people sort problems and all "cures" should be taken into account. Link to comment Share on other sites More sharing options...
abacab Posted February 13, 2019 Share Posted February 13, 2019 7 hours ago, sealesb said: Sorry I think we need to clarify this, "and has nothing to do with the user ID". Lets leave the Microsoft updates out of the equation for the moment because we know they can cause this type off issue as abacab correctly stated. Changing from a Microsoft account to a local account most certainly can cause this issue of plugins needing to be registered again also and it all depends on whether you installed your VSTs under a Microsoft account or a local account in the first place I think! It is to do with permissions.... a mind boggling Windows invention. Note this: A day or two after the latest update, switching from a Microsoft account to a local account disabled our copy of Addictive Drums instantly on the studio PC along with a couple of Izotope plugins. Just re register them and we were fine. These same plugins worked fine after the update with us. It was changing to local account which de-registered them. So all we were offering here was another reason for plugins needing to be registered again. It seems Windows update caused the original problem for dotonemanband and that's fine as he has it sorted now. But.....what we found was another reason for this issue and it should not be so easily dismissed, with all due respect to those who have posted on this, as it may sort the issue for other people. After all we are trying help people sort problems and all "cures" should be taken into account. The topic at the top of the page is "Windows update changes". and the OP had stated that he had just updated prior to their trouble with authorization. The context of my statement here was meant to be taken in relation to the current thread, not as some global rule. I was not dismissing your suggestion, but it didn't directly relate to the OP's stated issue. Your observation is interesting, and that info will certainly be useful in a broader context for troubleshooting plugin authorization issues. But I truly doubt that many folks are frequently switching back and forth between local and Microsoft accounts. Although, as you have obviously experienced, it can happen. Link to comment Share on other sites More sharing options...
sealesb Posted February 14, 2019 Share Posted February 14, 2019 I totally agree that the topic was Windows update changes. I also agree that people rarely switch back and forth between a local account and a Microsoft one, especially us more savvy DAW users. I build and maintain audio PCs and laptops for friends so have come upon this issue of the actual Windows update causing a reversion to a Microsoft account on a few occasions. I was in touch with Microsoft about it when I first noticed it and they said it shouldn't happen but suggested that the Windows update catalog on a PC can become corrupt and the PC can revert to a Microsoft account to get the correct updates. So I ran one of their pieces of software for repairing/ replacing it on the offending PC at the time and the issue has never arisen since on that particular PC. Just an obscure issue but worth keeping an eye on then. Hey these DAWS are only as good as the OS they run on and how well it is maintained. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now