Anytime there's a widespread bug that affects most or all users and completely breaks an important feature, the team does their best to go back and fix it... but they are a small team, so it's difficult for them to pull resources away from the current product to work on older ones. In this case, there was an HEVC bug that was causing so many crashes that most users of build 643 ended up having to roll back to build 550 to keep working... that was a bad note to close VEGAS 19's life cycle on, so once they figured out the cause of the bug and fixed it, they released another update to get it sorted so users of 19 can enjoy the features added in 643 without the crashes.

The corrupt 360 degree video renders was another long-time bug they finally squashed with this one.

For me, this B648 is an Install-wangdoodle! I go through the process only to be told it's installing VP20! Eh? I carefully proceed with the next screen and that finally brings me back to VP19, which then, Zombie-Like, informs me that there is, again, an update to my current VP19 Build. Well, install zombie there isn't, as when I View the Build it says Build 648. Gotta larf . . .

I'm now going to Reboot my MONSTA! just to see if the Install procedure DOES require this. So exciting . . .

Nope, Reboot PC I fire up VP19 B648 I still get this:

Here's proof of the installed NEW B648 being in place:

Annoying. I updated to get rid of the "Update Notification" - and it doesn't.

Any ideas, VegHeads?

It's annoying.

If you modify the cfg file in the Vegas folder to delete the update server URL it stops loading. I'd copy that file to the desktop, fix it, rename the original file in the Vegas folder and then copy from the desktop to the Vegas folder.

It's annoying.

@RogerS - Coooorrrect!

If you modify the cfg file in the Vegas folder to delete the update server URL it stops loading.

@RogerS - Erm, dear heart, this is Grazie here. You have great faith in me.

I'd copy that file to the desktop, fix it, rename the original file in the Vegas folder and then copy from the desktop to the Vegas folder.

@RogerS - While I thank you deeply for your intervention, why should I? Come to that, why should others have to do the same?

It would appear that the Update Routine needs to be updated too? Yes?

@RogerS ?

Do you mean this one?

There's no CFG file?

What do you mean by "fix it"?

In feature requests I requested it be possible to disable looking for program updates. I also gave that feedback on this build of 19. I didn't think I was alone in seeing this as a problem.

Anyway, the file is install.cfg in C:\Program Files\VEGAS\VEGAS Pro 19.0

Open in notepad.

[WEB]
UpdateURL=

Save it, copy it back to the folder and no more update nag window. No, we shouldn't have to do this.

No, we shouldn't have to do this.

@RogerS - Convergence of Sanity! Thank you 🙏.

@RogerS - And, of course, your instructions were perfect - thank you, Roger.

Glad it helped you- others suggested this file on the forum. I figured out you could just modify the URL and used the same fix for 550 as I was tired of clicking to disable on every single launch of Vegas! (sigh)

Glad for this thread: I assumed the update notices were for the last update---which I never installed 'cause of all the problems reported when it came out.

So...is this one worth installing?

So far so good; it fixes the issues I noticed with 643.

Yes, this was built and tested with the specific goal of fixing what broke in 643. Just bugfixes in this update.

So far so good.. But only for 2 hours.

I edited a new 4k-25p h264 project (files from ZV-E10 and DJI Osmo),
and everything looked fine finally, but after 2 hours of editing, when i only want
to move the top event just a few sec, Vegas doesn't respond :(

After 15 sec waiting window was greyed out, and i have to close it :(

Although it was not in HEVC format, i think some bug is still there.
I hoped i can just edit a day without any issue. What a nice christmas gift would be.

Anyone else any not responding issue after few hours editing with simple projects?

Win10 +1660Ti with latest driver, 16GB ram, ssd, i7-2600 (ok, it's a little old now, but this cant be the problem, when 2 hours was fine..)

I find NVDEC unstable with my GTX 1050; it works but crashes from time to time. A second generation CPU is too old to use an Intel iGPU instead. You could try turning it off but performance will suffer.

Will check also on my daughter's Ryzen 1600...

16GB ram ... i7-2600 (ok, it's a little old now ...

The i7-2600 was released nearly 12 years ago - it's more than 'a little old' and well and truly below the recommended specs for 4K in VP19 (same specs as VP20). The CPU is 5 gens below recommended and RAM is half of recommended for 4K. It's quite impressive that you got 2 hours of 4K editing done without a problem. But I wouldn't think that the Vegas team will be concerned about the problem given the aged CPU and low RAM.

But nonetheless, two suggestions:

1/ Without knowing the video recording method of your two cameras, is either or both recording in Variable Frame Rate (VFR)? If yes, try transcoding to Constant Frame Rate - Vegas Pro has never like VFR very much.

2/ In File I/O, try enabling legacy AVC decoding.

I knew that many answer will be about my old cpu :)

I'm 99% sure that issue will be exist on Ryzen 1600 too, and nothing wrong with my i7 cpu.
But will come back later. (my task manager show 30% cpu usage..)

1) VFR? Neither cam can record in VFR, both was in 25p mode of course.

2) Legacy? I like to edit with the help of my gpu power.. afterall i payed for this function.
Maybe RogerS has right and nvdec is unstable with Vegas :(

That's why i ask if anyone else has such not responding problem?
Or everybody can edit hours and hours without freezing?

Nothing's wrong with your CPU beyond it being slow. I used a 2nd generation i7 with Vegas up through VP 12. The iGPU is no longer compatible with Vegas due to its age however- it lacks critical functions. I also edited 4K with 8GB ram without issue for years though I now have 32GB.

I'm also curious if other 16XX users are having a better experience than you with NVDEC. I use all CFR media, mainly X-AVC S. Can't say I had a good experience with with a mobile 10XX but I stopped using NVDEC during VP 18's life so maybe it's better now and I don't realize it.

yes, i love my cpu..

Forget to say that memory usage dont go higher than 8GB..

 VFR? Neither cam can record in VFR, both was in 25p mode of course.

Unfortunately, not necessarily 'of course'. A progressive recorded video does not automatically decide whether the recording is VFR or CFR. For example, smart phones typically record video in 30p (and often with the choice of 60p) - but video is almost always recorded VFR. To make sure, check out your video footage via the free MediaInfo app - https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/ - it's merely just something to check in order to identify or eliminate a possible cause of a problem.