Vegas Pro 20 never launches correctly

Musicvid wrote on 11/20/2022, 11:21 AM

Which build of Vegas 20? The latest is build 214.

Here is a free utility to end all running Vegas processes. Just put it on your desktop.

andyrpsmith wrote on 11/20/2022, 11:28 AM

Are you launching Vegas as administrator?

Richvideo wrote on 11/20/2022, 2:26 PM

I have had this issue in both Vegas 19 and 20

I end up having to run a 2nd instance of Vegas and then shut it down in task manager then the first instance of Vegas will start to load up

Musicvid wrote on 11/20/2022, 6:51 PM

Yes, it is a known issue.

RogerS wrote on 11/20/2022, 9:59 PM

Is it a plugin blocking proper shutdown? Haven't seen this behavior myself.

daniel-t wrote on 11/23/2022, 10:29 PM

…They seriously haven’t fixed this yet? Happens to me now and again on 19 (used to be really bad, but is now relatively rare, but did happen today).

Thanks for the link to the utility, I’ll give it a try.

paul-marshall wrote on 11/25/2022, 5:08 AM

Same here (V20 -214) - except I woundn't say 'never launches correctly'. Maybe 1 in 5 starts require a visit to the task manager to end Vegas Pro task. Then it'll start ok next attempt.

Bob07 wrote on 11/27/2022, 5:00 AM

I have recently bought Vegas Pro 20 and I have same issue - I simply can not start it and I can always see the process in the task manager. O tried all hints above and nothing works. I use win 10 pro and I am out of ideas how to make it work :-/ Any advice will be appreciated.

Reyfox wrote on 11/27/2022, 6:18 AM

I bought VP20 a few days ago. Installation was without event. And it starts every time for me. My computer specs are below in my signature. I had the trial version and that too started without issue.

Have you tried resetting? Uninstalling/reinstalling? I use Revo Uninstaller the paid version. But the free version is very capable and hunting down registry items and folders left after using Windows to uninstall.

If all else fails, there is tech support....

ColdHardDrewth wrote on 11/27/2022, 2:51 PM

Ever since I updated to Vegas Pro 20 the program almost never launches correctly, I always end up having to do the following:
Launch Vegas -> nothing happens -> go into task manager and end any Vegas Pro tasks -> attempt to launch Vegas Pro again

It's incredibly annoying as sometimes I have to repeat this procedure multiple times and scrolling through all the tasks to end Vegas Pro gets tedious when you have to do it so many times. I haven't found any fixes on the forums for this other than having to go into task manager and ending the task, and surely that cannot be normal behavior for this software?

Been having this issue with 19 for years. Think it's Windows 11 related just because that's what I'm on... You're right.... lots of lost time in the Task Manager locating and shutting down the "frozen" instances of VegasPro

BTW, thanks. You just saved me an upgrade. Not upgrading if that's not fixed. That, and the fact that they still aren't making it more accessible for 4k monitors with options for larger icons.

Howard-Vigorita wrote on 11/28/2022, 9:45 AM

I have the problem of Vegas delaying exiting from memory by about a minute on my laptop but not on other systems... on my laptop I start Vegas with the powershell script linked in my signature. Mainly so I don't have to wait the minute when I make changes that require a restart. But this problem isn't confined to Vegas 20. It's always done it on my current laptop as well as previous ones going back to vp16... all with built in Nvidia plus Intel gpus.

I also get the startup problem on occasion on all my systems. But only on the 1st startup after booting up. Vegas loads into memory but no Vegas screen opens up. I find reversing the sort-order in task manager (z to a) so vegas200.exe shows near the top without scrolling makes for a quicker kill. Seems to happen more on my amd+intel gpu systems than my laptop and only with vp20. Curiously, Vegas Sound Forge 16 acts similarly but if I wait long enough, its screen eventually opens up. VP20, however, needs to be killed before it will open up on the next attempt. I always kill it by ending its process tree.