Well, it may not be Vegas' fault, but Vegas could help out a lot. There are two things that would really be nice. One is to show the plugin name as it's being loaded, as ACID (sort of) does. This way when you see it get stuck you know what one it's stuck on. The other is to have a timeout function on plugin initialization. If a plugin doesn't complete loading in a certain number of seconds then Vegas skips over it and moves on to the next. That plugin won't be available, but at least Vegas will be. And of course, it should pop up a dialog box telling you which ones it skipped, including the full pathname to the .dll.