Komplete Kontrol can't find plugins

Yes this is an issue for me also today I tried to run it as a plugin in fl studio but it couldn't load the plugins only the internal sampler so I loaded the standalone - this scanned for plugins on startup but couldn't get midway through the plugin scan, always getting hung up I thought it may be due to how many plugins I had so I put some of the vst3s in sub folders but it is still getting stuck it almost seems like it wasn't built to handle scanning thousands of plugins. It just stops working after it gets through a 500-1000 of them.

I see that the plugin scan has been buggy for a long time now, it is really unfortunate as I think it works but it just freezes up rather than put up an error screen there is no way to bypass etc… I use a lot of software and errors during scans are not uncommon but this freeze up makes the whole thing useless as there is no way to finish scanning. The only real option is perhaps a registry change to change the vst3 folder or simply copying the contents of vst3 to another folder so it can quickly get past the scan process then dump them back in for my other software to use. So I renammed VST3 folder to VST3b and make a folder called VST3 that was empty and it seems to be scanning other folders now lets see if it makes it through. No Dice still got caught up. probably on some vst2 folder now not sure, it doesn't even show what directly it is scanning which is problematic for trouble shooting. VERY buggy scanner.

Hmm I know I had to select the mapping within the plugin for the fl key 49. It wasn't auto detected what controller was being used. There is a mapping tool also not sure if you would need to use that to do your mappings.

What I have found is in standalone it is possible to get through the scan by renaming the VST2 and VST3 folders to VST2b and VST3b. Currently the only real bug I have found is that it is incapable of making it through plugin scans. I am about fed up with attempting to get it to scan through the plugins so they can be used in Komplete Kontrol. I Noticed that once I got into the plugin by letting it scan the empty VST3 and VST2 folders rather htan the ones that were were renamed the scan does show popups for some plugin errors but they seem to back log the memfile and plugin info screens seem behind the scan process causing it to jam up. Its like it isn't able to keep up with providing the error popups because you have to close the last one for the next one to show like if you hold down a keyboard key until it makes noise and the buffer fills then it logs out.. it almost feels like the way the error popups are being dealt is filling a buffer and crashing the scan when it fills or something. Essentially no error popups are served when the plugin is loading. Its buggy. I am guessing there will be some service they don't say is required that is required, all these companies should be listing every single windows service their software depends on to run so it can be trouble shot.