Hey @Marc-Gold... hopefully you have the same success I eventually did.

Launched 3 times on that laptop with same error.. on 4th launch it started without issue, and has been loading OK since. Still unnerving but happy it's working on the laptop, and seems more stable than 18 was on this project which was being troublesome before.

Installed OK on my desktop too and so far it is performing well.

Thanks. No such luck. What could it be with VP 20 that prevents it from working on the same computer that VP19 works perfectly?

@RedRob-CandlelightProdctns @Marc-Gold Hi, there is one move i sometimes do, Windows - Settings - Storage - Temp files - tick all boxes & delete, this clears out all the old crap Windows keeps, it gets rid of thumbnails with fx red x's through them etc.. You don't loose any settings but all files thumbnails/files etc' take a bit longer to load the first time you open them, it's a little bit like starting afresh, don't know if this will help in any way but if your PC has temp files & is used to looking for V19 stuff n now it's looking for V20 stuff .... 🤷‍♂️🤷‍♂️🤷‍♂️

Thanks, again. I did do exactly that to no effect. I still have V19 on my computer and all its associated files. I can't imagine that's causing the problem though. Thoughts? If I delete 19, I'll be left with no working version of Vegas.

I also ran malwarebytes which found no problems and did a Windows file repair which supposedly fixed 4 issues, but 20 still won't work. It's strange that the computer just all out freezes in a matter of seconds of opening 20. So disappointing. I love delving into the new software. Fingers crossed. Hopefully there's an answer. Where else can I post this?

I still have V19 on my computer and all its associated files. I can't imagine that's causing the problem though.

That's not a problem. My newest laptop has VEGAS Pro 14, 15, 16, 17, 18, 19, and 20 installed and all work fine.

If you're error is the same as I was originally getting (openvino_intel_gpu_plugin.dll) then I'd not think this is any kind of cache issue but one related to support for that .DLL. I still don't have an answer but am trying to steer the dialog towards the reported problem specifics.

@Marc-Gold What exactly does it says in your error report?

@RedRob-CandlelightProdctns, Yes, it is due to a conflict with that specific .dll file..... If you temporarily remove that file and say, store it in your documents file, you will not have that issue at start up again.

@Steve_Rhoden yes -- but moving it could break anything else which is using that DLL

Hello gentlemen, and thanks for your help. I have not ever seen an error message related to the VP20 freezing issue. The screen just freezes up and the only thing I can do at that point is close VP20. After VP20 is gone off screen I can click on other things at will. When VP freezes and I try to click on anything at all, the screen goes white-ish and that's it. It's over at that point.

The program says 'not responding' whereupon the screen turns whitish and is frozen.

@Steve_Rhoden yes -- but moving it could break anything else which is using that DLL

@RedRob-CandlelightProdctns I think that dll is part of the Vegas 20 Deep Learning Module and is only used if you are loading a project that uses one of the three ai-powered fx that vp20 comes with. If you temporarily remove the vp20 Deep Learning, that dll would be removed. Maybe then you'd be able to at least get into Vegas with some kind of error message. I imagine that it is only loading that dll on startup because you're set to open the last project used on startup and that project uses one of those 3 fx. If you can get into Vegas without a crash, you might also want to not load the last project automatically. Maybe renaming that project will also get you in. Fwiw, I've only seen issues with the Style Transfer FX on some systems but not when just loading a project that uses it.

Both me and Steve were getting the error (he still is) after first installing VP20 and launching it. No other prior project is loaded when VP20 launches the first time. (and FWIW, I don't use any of the deep learning FX)

My comment about renaming it breaking something is that something else on the machine could be using that DLL besides Vegas.