Was there anything significant worth mentioning done on or to the host system in the time frame after you uninstalled and then re-installed it again and it appeared working? Like adjusting any system settings, adding/removing system components, turning off possible offending services,etc...

 

No, nothing. My DAW box is a quite static system. It amazed me that re-autorizing SPL Hawk Eye worked immediately, but not the AMEK M.C. - which required a full deinstall/new-install to work. For now i'm happy as both plugins work again and i hope it stays that way...

 

IMO you probably put an older version of the license on the plugin after deauthorizing (maybe for demo/legit/other teams versions installed at the same disk as R2R), that's why Hawkeye worked and the amek comp not. After reinstalling you did generated a license with an up to date keygen, that's why Amek Mastering Compressor worked only after the reinstall, because you generated a license with the keygen that came with that install.


The whole diagnosis and the fact the OP didn't changed any OS settings don't leave with another option than that. It's not a timebomb if it's happening only to you, at the very beginning.

 

100%

thats all

 

I don't think my problem is a timebomb, but it IS a real problem. I load a PA plugin, and sometimes it works fine, and other times it says I need to auth. It is apparently almost random. I have to constantly remove instances and re-instance them until I get an auth version (which is faster than running the keygen). I have done everything right on the install, blocking, etc., and I am on a new comp running the latest windows with a full normal installation. It worked fine for a while but this started happening when I re-authed with a more recent keygen while installing plugins released after the bundle.

 

Interesting, though the title could be less bombastic. (More like Articstorm's: problems, fixes, workarounds <- that's useful IMO)

I did not install any plugins from the mentioned release (I was just thinking to give it a go..). I have quite a lot of legit PA plugins installed and now and then I have problems with "dead" channels because of the de-authorisation. Have the license on ext USB, and the culprit may be the USB itself, the power management on ports etc etc..

Anyway it's a super popular release, installed by thousands I guess.. any problems will become obvious quickly.

 

No timebomb here....Never had that with PA stuff. I'm on Windows 10 and use Reaper/Studio One

 

This sounds like more a function of interactions between plugins and their respective licensing/activation b.s.'s rather than a host system thing. Especially when all the outside forces working against you (i.e. the internet) are eliminated and these kinds of things are cropping up. Of course elimination of the outside forces doesn't mean there aren't local forces (i.e. win10/11 OEM) working against you, but at least those local forces are ones you can control much easier.

Although there are enough reports of other similar instances that are of concern here I would say just install the stuff with utmost attention to detail and expressly keep the auth schemes that came with each one, with that one, and only that one. Mixing this stuff up doesn't seem to fare well.

 

No time bombs here, Win 10, Ableton 11.