Noel Borthwick [Cakewalk]
>>VSTSCAN: Previously scanned - NOT a VST plugin


This means that during one of your scan's the plugin load itself failed. When that happens VstScan process flags the plugin as not a VST plugin. It does this so that we don't repeatedly waste time trying to scan DLL's in the scan path that aren't actual plugins. Most likely what happened is you had a bad install or plugin that was not yet authorized at one time. This is a common problem and the normal way to solve it is by setting the "rescan failed" flag in the vst preferences and rescanning to pick up the plugins.

Thanks Noel...

That makes sense... but i tried the rescan and nothing changed.

I also noticed that this plugin (which is x64) didn't show "is64" in the registry. Maybe that changed after the fix and rescan i did... i'll have a look!

A quick update iLok confirmed, by email, they had server issues over this previous weekend i.e. 19-20th May 2018, this may explain why it appeared not to be authorised.  What I was seeing in the iLok Licence Manager was that I had the Hybrid available but could not activate the licence. 

Wookiee
A quick update iLok confirmed, by email, they had server issues over this previous weekend i.e. 19-20th May 2018, this may explain why it appeared not to be authorised.  What I was seeing in the iLok Licence Manager was that I had the Hybrid available but could not activate the licence. 

Glad to hear yours is fixed too!

Yes?