Vegas pro 20 wont open after new update

Comments

yoo-changyun wrote on 5/3/2023, 8:53 PM

I have to give you a guest video, but suddenly Vegas Pro 20 doesn't open. It's not just me, but all our partners don't open Vegas. Will you take responsibility if the customer requests a complaint? It's not just my problem. It doesn't open Hurry up and solve it

Former user wrote on 5/3/2023, 8:58 PM

For me an easier way then going to the modem,

Bottom right Open Network & Internet settings, disable whichever one is working.

 

Sandhill_Films wrote on 5/3/2023, 8:59 PM

It's the internet. Doesn't matter what version

Intel® Core™ i9-13900KF 3.00GHz

MSI PRO Z690-P DDR4 - ATX

(2) * 16GB DDR4-3200 Corsair Vengance LPX

NVIDIA® GeForce® RTX 3060 12GB GDDR6

500GB SAMSUNG 980 NVMe M.2 SSD - OS (Windows 11)

4TB SAMSUNG 980 NVMe M.2 SSD

CLX Quench 360 Closed Liquid Cooler

SET SAKARA Mid Tower Black

(4) * RAZER 120mm Case Fans

750 Watt EVGA BQ 80Plus Bronze

2x Asus ProArt PA278QV 27" WQHD Monitors

M-Audio AV32 Speaker Monitors

M-Audio BX8a Speaker Monitors

Windows 11 Home

MIJ wrote on 5/3/2023, 9:00 PM

I have same problem.... can't open....so I cut wifi and it was open....So funny situation..

Sandhill_Films wrote on 5/3/2023, 9:00 PM

Some that hits the web at Vegas launch is causing it

Intel® Core™ i9-13900KF 3.00GHz

MSI PRO Z690-P DDR4 - ATX

(2) * 16GB DDR4-3200 Corsair Vengance LPX

NVIDIA® GeForce® RTX 3060 12GB GDDR6

500GB SAMSUNG 980 NVMe M.2 SSD - OS (Windows 11)

4TB SAMSUNG 980 NVMe M.2 SSD

CLX Quench 360 Closed Liquid Cooler

SET SAKARA Mid Tower Black

(4) * RAZER 120mm Case Fans

750 Watt EVGA BQ 80Plus Bronze

2x Asus ProArt PA278QV 27" WQHD Monitors

M-Audio AV32 Speaker Monitors

M-Audio BX8a Speaker Monitors

Windows 11 Home

Brandon-Blackard wrote on 5/3/2023, 9:08 PM

See my thread or read this post. Disconnect from the internet and you should be fine.

Lol fixed this for me... odd

johnnyrr wrote on 5/3/2023, 9:11 PM

Same problem here. But idiot me, I just disconnected my ethernet connection for about 15 seconds, then re-connected it... then tried to open Vegas 20. It failed to open.

You need to leave your computer disconnected from the internet during the bootup of Vegas. That worked. Then once it was open, I re-connected the internet. Working like a champ now. Hopefully this (validation?) bug gets fixed soon though... this is certainly not a long-term "fix" I'm willing to live with.

Otherwise, the new update works much better than the previous version from what I could tell (during the hour I had it working). One of my major pet-peeves was how long it would take to get a project file to start working properly after I saved it... this was never a problem with versions 19 and before. And the more files I had in the Vegas 20 timeline, the more lag it took to start working properly again. This caused me to not save files very often anymore, so of course when it crashed, I'd lose more work. A terribly annoying bug that now seems to have been fixed. Thank you. Finally!

George-Abihider wrote on 5/3/2023, 9:23 PM

I am having the same issue.

After initially installing the upgrade to 402, it opened but only the top half of the screen. The timeline would not load. After loading a previous session, it seemed ok.

Today after working I shut it down and went to open it again and nothing. No error message, get splash screen but when it says its done loading it just disappears. I did notice within task manager it says its error reporting before it goes, but I don't get any window.

I reinstalled Vegas Post.but it did not bring it back. I read in this thread that it was related to the internet. So I unplugged my Ethernet cable and Vegas Started, showed the right Startup screen, I closed the program, plugged in my Ethernet cable and it will NOT start.

EricLNZ wrote on 5/3/2023, 9:26 PM

@George-Abihider Don't plug your cable back in until after Vegas is up and running.

Rachel-Dickinson wrote on 5/3/2023, 9:34 PM

It's not a windowd update issue - neither of my machines have had updates and it stopped working on both of them at the same time. What did just work was manually changing the date on my computer to 2nd May, at the suggestion that it had worked for someone else. It did work...I have no idea what error caused this, but give that a go. Very easy to do.

George-Abihider wrote on 5/3/2023, 9:43 PM

@George-Abihider Don't plug your cable back in until after Vegas is up and running.

Eric, Thank you, yes, I did that. Once Vegas was running I plugged in the Ethernet. BUT, I was curious to see if it would start with the Ethernet connected again. So, no. You MUST disconnect Ethernet to get Vegas running.

And, just as an FYI. In Windows 10, you can go to....

  • Settings
  • Network & Internet
  • Ethernet
  • Change Adapter Options
  • Click on the Ethernet device that connects you to the internet (Mine is called Ethernet2)
  • Click on Disable this network device.

Start Vegas Pro. Once it has started you can then "Click on Enable this network device."

Zaza17680 wrote on 5/3/2023, 10:24 PM

It's not a windowd update issue - neither of my machines have had updates and it stopped working on both of them at the same time. What did just work was manually changing the date on my computer to 2nd May, at the suggestion that it had worked for someone else. It did work...I have no idea what error caused this, but give that a go. Very easy to do.

bro it literally worked, I didn't imagine it was really a solution, i'm just amazed

richardpohl wrote on 5/3/2023, 10:31 PM

It worked here, too, I put Airplane mode, turned off Wifi and disabled Ethernet (even though I do not use it at all). VEGAS started now.

VEGAS Pro 20 Edit novice user.

ASUS Legion Y540-15IRH, Intel Core i7-9750H ,GeForce RTX 2060 6GB, 32 GB RAM, Windows 10 64bit, Logitech Brio webcam + CAMO (Huawei P30 Pro)

Audient id44 audio interface + Aston Origin (vocal mic) + Aston Starlight (stereo paired piano mics)

Or

Yeti Pro

VEGAS Pro 20 Edit + SoundForge Pro 14 Microsoft Store Edition + Acon Acoustica 7.4 Premium Edition

Also using Reaper and OBS frequently, VideoRedo TV Suite 6, now also HandBrake, thanks for the tip!

Audio plugins by Acon, iZotope, Waves, etc.

Googly-Smythe wrote on 5/3/2023, 10:41 PM

It's not a windowd update issue - neither of my machines have had updates and it stopped working on both of them at the same time. What did just work was manually changing the date on my computer to 2nd May, at the suggestion that it had worked for someone else. It did work...I have no idea what error caused this, but give that a go. Very easy to do.

bro it literally worked, I didn't imagine it was really a solution, i'm just amazed

This worked here, too. Set date to 2nd May, VEGAS runs. Quit it, set date to correct date, VEGAS doesn't run, stops at "Initialising Script" something or other.

The internet fixes didn't work for me.

Computers are weird, these days. Why, when everything was hunky dory on the 3rd May, should VEGAS stop on the 4th? The developers don't like Star Wars, maybe?

A 100% amateur, making ham-fisted music with my guitar since 1969, soon after seeing Pink Floyd at the Festival Hall, the Albert Hall and the Fairfild Halls.

My main software is Cubase, but I use VEGAS to make videos to post on BitChute and, rarely, on Youtube.

My first computer was an Atari STE 1040, because it could run Cubase and had built-in MIDI ports.

Currently using an i9 12900/Radeon 6700XT machine, 64 gigs RAM, 2 x 32" 1440p monitors, Win 10, VEGAS 20.

Former user wrote on 5/3/2023, 10:56 PM

May 4th so it must be the Midi-chlorians messing with the internet force,

Antbric wrote on 5/3/2023, 11:04 PM

I'm experiencing the same thing, won't launch unless I disable the internet adapter on my Windows 10 PC. This is so anti-consumer, I paid top dollar for this crap not to happen.

DStiles wrote on 5/3/2023, 11:45 PM

Changing the year to 2022 worked for me without unplugging the internet. You have to do it while it starts up and then you can set it back when you're in the application. This workaround works, but it's an inconvenience as well, so hopefully Vegas Pro fixes this tomorrow.