This seems to fix the problem, but only been using for 30mins.

https://www.majorgeeks.com/files/details/runasdate.html

Try using defaults, I adjusted some options and vegas would detect 'something is up' and shut it's self down after a while. I think trial version must be programmed to detect such software, but Paid version is also checking for date anomalies.

One of the things involving both the internet and the time of day is "certificates". If a program accesses a service securely, it will check the servers certificate, which is a a proof of who they are. Certificates are stamped with an expiration date. If that date passed, the connection is considered insecure. But if the program can't access the service at all, maybe it doesn't care so much as it does about an insecure connection.

It is the most logical answer, thanks for the information.

Freaky! The problem began on May 3rd, Central US time/ was using Vegas in morning no problem on my main PC, Windows 10. By the evening, the program would only partially load and quit before GPU initialization. I had just downloaded Zoom and thought that might be issue, so uninstalled Vegas and reinstalled. No resolution. Tried installing Vegas on another system, Windows 11, same issue, would only partially load, then close down. Came here and was glad to see this thread. Disconnecting Wi-Fi solved the problem on both computers. Hope a detailed explanation follows as to what the exact issue was. Kind of freaked me out that program would not load and initialize esp since I was in middle of a big editing project. But at least it is running now. But to clarify issue happens on Windows 11 too.

thanks for the contribution, I tried with vegas pro 18 and it works normally

i've dorked about with a bunch of stuff, and i am certain it is crashing somewhere in the scripting engine. i believe the scripting engine uses microsoft edge webview; a new version of that seems to be included with a recent update.

can one of the devs or support staff please chime in here, this is a pretty bad one!

Moderators have been told that the VEGAS team hope to have this resolved in the next few hours. It's likely that new builds of VP19 and VP20 will be required.

Thanks to all for providing this information.

Due to my distrust of Windows; I reinstalled Vegas 19 and then recovered my C drive from 5 days ago before thinking of looking here.

I am old but still able to learn!

Thanks to all for providing this information.

Due to my distrust of Windows; I reinstalled Vegas 19 and then recovered my C drive from 5 days ago before thinking of looking here.

I am old but still able to learn!

@dennismf vp19 still worked, what build?

Thanks for this help, cut of internet and start Vegas... its work

Several users are reporting problems opening Vegas Pro. Not just version 20.

Possibly a recent Windows Update is causing the problem. Until it's resolved the following work around has been posted by several users.

Disconnect from internet > Open project > Reconnect to internet.

Alternatively Manually change your pc systems date has worked for some. See posts below.

Thank you very much Sir, it definetly worked, I had to finish eding my video and you saved my day.

Version 17 starts without problems, version 19 and 20 not. The date trick did the job.

Glad for this workaround. THIS WORKED FOR ME! WHEW!

I don't like it either but at this point I just wanted to get the program up and running so I can work. I don't have time for all these recent problems. Vegas Pro has been super inconvenient the past few months and its just not cool. Consistent issues like this cause users to consider other software. I really hope they figure this out soon and have a good run of consistent smoothness with the next release.

But THANK YOU for this. I needed this. So grateful.

Same here. I am on the edge of getting another program more stable to be able to keep working flawlessly. 😐

To be disconnected from the internet does not work here. Or to be more precise: I had to disable the WLAN on my laptop, only then it worked. As long, as my laptop "saw" the WLAN, even if it was not connected to the internet, it did not work.

The updates history shows on my system, that the Update for Windows 11 version 22H2 for x24 based systems (KB4023057) has been installed yesterday (3.5.2023). I assume that this causes the problem.

Thanks to all for providing this information.

Due to my distrust of Windows; I reinstalled Vegas 19 and then recovered my C drive from 5 days ago before thinking of looking here.

I am old but still able to learn!

@dennismf vp19 still worked, what build?

I am using VP 19 build 648. Turning off my WiFi connections allows me to start Vegas.

The suggestion regarding service certificates and some sort of licence validation / revocation service seems very plausible to me.

 Turning off my WiFi connections allows me to start Vegas.

same here.

It appears to be a certificate issue and probably unrelated to the recent update, except that they should have caught it. The previous build would have died too most likely.

Right click on one of the DLL's in the Vegas directory and check the certificate date. It expires on 5/3/2023. I checked Vegas Pro 18 and it too has he same expiration.

I tried to start VP 19 with WiFi on but with my WAN connection disabled at the router. Vegas still did not start. It appears to fail (not start) if there is any type of network / LAN connection.

It appears to be a certificate issue and probably unrelated to the recent update, except that they should have caught it. The previous build would have died too most likely.

Right click on one of the DLL's in the Vegas directory and check the certificate date. It expires on 5/3/2023. I checked Vegas Pro 18 and it too has he same expiration.

Same here - the certificate is expired. BUT why is it possible to start Vegas, if you disable the wifi/internet router? This is open.

Vegas Edit 20 Steam edition (version 20.0 build 370) doesn't launch also on Windows 10.
I've changed system time to 2022. After that the program have launched.

It looks like the certificate expiration date is exactly May 3, 2023 4:59:59PM. It's easy to wind back a year but presumably as long as your clock is set before this date, it should probably launch. I wonder how many versions they will have to go back and fix. I'm sure 2023 seemed like a very futuristic date whenever it was originally chosen.

It appears to be a certificate issue and probably unrelated to the recent update, except that they should have caught it. The previous build would have died too most likely.

Right click on one of the DLL's in the Vegas directory and check the certificate date. It expires on 5/3/2023. I checked Vegas Pro 18 and it too has he same expiration.

That may well be part of the cause BUT VP17 certificate has the same dates and opens without issue. VP14 certificate expiry date has long since passed and that also opens without issue. So I guess this must be something to do with the way VP19 and VP20 connect to the internet during startup to check for updates, news, license etc..

 

Same here - the certificate is expired. BUT why is it possible to start Vegas, if you disable the wifi/internet router? This is open.

I don't know if it was ever stated how often you must allow Vegas to communicate with the server, It was once said about once every couple of weeks, if that's true, the software won't load offline in about 13 days if the server problem isn't fixed.

I am thinking because Vegas is failing the authentication process with the server Magix defaults to seeing Vegas as not having a license and remotely shuts it down... something like that

It think it must be checked by the development team.

If the certificate on 3rd May would be the issue - why was it possibel to start Vegas here, after disabeling the WiFi? (I have here the local time of 9AM, on the 4.5.2023 - and disabling the WiFi allowed me to start Vegas one hour ago).

But we will see what is the outcome of that check. In the meantime, we have some workarounds:

- to disable the WiFi at all/to disable the router

- to set the time back on Windows.