Solved Massive X (or any other plugin) blacklisted by Cubase

It usually happens upon installation, cache cleanup, or after a big preset kit install.
Massive and other plugins/programs (Komplete itself) scan for new presets upon launch, and especially on the first run it may take time. Apparently this causes Cubase to go on alert because the plug-in is taking too long to respond, thus blacklisting it. I suppose it's just a matter of running the plug-in standalone before adding it to Cubase, so it'll have scanned all presets when Cubase is run, but it's really something that NI should work on to prevent the issue in the first place - Massive shouldn't stop responding while scanning or whatever it is.

In the case of Massive X, we're at a loss as it still doesn't have a standalone version, otherwise it could, say, be run silently upon installation just to scan presets and create its database. For the same reasons, I advise everyone to run all programs and plugins right after installing before adding them to Cubase. I did it to all of mine and the only that had an issue was precisely Massive X.

Either way, if Cubase deactivates it, just re-enable it and it'll work. If not, you may have added the 32bit instead of the 64bit version.
I'm not NI, but I'm curious as to whether this will work for you guys, so please let me know if it helped. Cheers!