I was suffering from extremely slow application startup with VEAI, even with the latest release, so I did some testing and found the cause.
If you have networked drives mapped in Windows, VEAI will try to poll/probe those drives on startup, and if the drives are not reachable, VEAI will hang until the poll request times out (this can be up to 30 seconds in my experience - very frustrating).
I’m not sure why VEAI has been programmed to try and reach all network drives but this needs to be corrected. The only drives VEAI should need to connect to on startup are it’s own installation directory and wherever the model folder has been set to.
Anyway the workaround for now is to delete any mapped drives that aren’t reachable when you are launching VEAI.