How to Shutup Live 11 Plugin Startup Scan?

[Klangraum]

After testing several scenarios, it was obvious, that the Qt runtime, which is Live build on, is very slow at first start/initialization/cache. So, the script does not much performancewise. This behavior led to wrong assumptions.
Here is a quote from the Qt-developer forum: "Only the first application startup will be slow, since that has to populate the cache. All further apps start faster." This means that the Qt runtime libraries must first be loaded into the cache, but are then still available for other apps. I hope that explains things.

Sorry for that, Ableton can't do much, and we can't do much to speed up Live, when it is started after Windows reboot. The question still remains why Live is doing these scans at startup, which makes the situation even more problematic.

My latest test: (script does minimal changes)
Live start after full reboot: 4 min
Live start after starting it once before: 15 sec

I'm out on that problem-solving. It's a mess.

[FurkanTopal]

This is frustrating problem and the another one is plugin scanning. Right now I just downloaded two new plugins but Ableton can't scan it. I'm trying to do it again and again, showing the folder but Ableton can't understand. Ableton is one of the worst DAWs as for plugin scanning. Wack.

[FurkanTopal]

Finally now after waiting for a very long time, it saw the plugin and now finally it's updated. Jesus. I set up the plugins much way faster than Ableton's scanning. I really hate when this happens. We humans should be way further than this. Approximately I lost one hour for scanning two plugins!

[Sau6on]

who thought this was a good idea to forcefully scan plugins every single time Live starts without giving user an option to opt out of this messy start

tbh this makes live look weak when you just want to open a light session to show someone, and this scan just interupts not only audio, but also display/video