The solid fixes has been released.
https://www.vegascreativesoftware.info/de/forum/emergency-downloads-look-here--140837/
Is there an update for v18 - its the most stable release on my system and the one I use for everything :S
Vegas 19 patch was successful. Thank you for quick turnaround on this fix!
Vários usuários estão relatando problemas ao abrir o Vegas Pro. Não apenas a versão 20.
Possivelmente, uma atualização recente do Windows está causando o problema. Até que seja resolvido, o seguinte trabalho alternativo foi postado por vários usuários.
Desconectar da internet > Abrir projeto > Reconectar à internet .
Editar: o VEGAS Pro 20 build 403 resolve esse problema. Veja aqui .
hello, I hope this whole problem is solved as soon as possible, like me many people have projects that depend only on the operation of sony vegas.
I had Sony vegas 20.0 (Build 214) installed here, when I try to open it, with internet or without internet connection, it stops at the same place "Scanning for VST plug-ins..." and nothing happens.
Analyzing the comments here on the forum, yesterday I downloaded and installed "VEGAS Pro 20 Build 403"(VEGAS_Pro_20.0.0.403_DLV_DE-EN-FR-ES-BR_230504_07-19_FAF9119E.exe) but it is not opening either, even without connection there internet, it does not open.
I also tried to change the date to 2022 and without internet connection, in both attempts, it didn't work either.
I don't know what else to do as I have ongoing projects
The link to the solution is some postings above.
Silly idea but ...
If its a certificate issue or DLL can we just take the new fixed DLL / cert file and drop it into the old install?
Would this fix my VP18 issue ?
Silly idea but ...
If its a certificate issue or DLL can we just take the new fixed DLL / cert file and drop it into the old install?
Would this fix my VP18 issue ?
I didn't catch that VP18 was experiencing the same thing as well. That's unfortunate for anyone who bought it in the Humble Bundle less than a few months ago.
But yes, due to the fact that changing the computer's date is enough to fix it tells me there's probably a server-side security certificate that expired and should be an easy fix for someone that knows what they're doing (not that I am one of those people; I just know they exist). Would love for someone to officially explain what went wrong.
Their Twitter talks about it, but boils it down to a "conflict", not to be confused with what's going on in SE Europe right now: https://twitter.com/MAGIX_INT
We have been informed that the Magix download servers has been updated so now you can expect faster download speed:
VP19b651: https://www.vegascreativesoftware.info/us/forum/patch-vegas-pro-19-build-651--140801/
VP20b403: https://www.vegascreativesoftware.info/us/forum/vegas-pro-20-new-build-403--140782/
Thanks to few users who also helped sharing temporarily yesterday. By request, these temporary links are now hidden.
Silly idea but ...
If its a certificate issue or DLL can we just take the new fixed DLL / cert file and drop it into the old install?
Would this fix my VP18 issue ?I didn't catch that VP18 was experiencing the same thing as well. That's unfortunate for anyone who bought it in the Humble Bundle less than a few months ago.
But yes, due to the fact that changing the computer's date is enough to fix it tells me there's probably a server-side security certificate that expired and should be an easy fix for someone that knows what they're doing (not that I am one of those people; I just know they exist). Would love for someone to officially explain what went wrong.
Their Twitter talks about it, but boils it down to a "conflict", not to be confused with what's going on in SE Europe right now: https://twitter.com/MAGIX_INT
Yes - it loads up and says error 72 there is no license and stops running.
If I set the date back its ok but that isnt the answer long term.
If folks paid for it months ago they need to fix 18 too.
Tested VP18b527 here and no issue.
VP 18 b 527 still opens OK here as well.
VP 18 b 527 still opens OK here as well.
re error 72, this comment.
Nothing to do with that - if I set the date back to the start of the week it loads fine.
Let me check version number...
VP18 (434)
@djrikki2, Then try update to latest: https://www.vegascreativesoftware.info/us/forum/vegas-pro-18-update-5-build-527--129047/
Re error 72, this comment.
And would that be a copy licensed by MAGIX? See your MAGIX Account > My products for the download link of the last update/build. (Or try the link @set mentions.)
Greetings. Is there a new build out for Vegas Pro 19 that fixes this problem? I'm still using the work-around. Thank you! I'm on build 648.
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.
Edit: VEGAS Pro 20 build 403 solves this issue. See Here.
But what happens if you wanna render into high quality mp4? i cant seem to do that because it requires internet connection, and just crashes when i tried to do that.
But what happens if you wanna render into high quality mp4? i cant seem to do that because it requires internet connection, and just crashes when i tried to do that
@Draven-Winstead Download and install the Build 403 for Pro 20 and you won't need to disconnect from the internet. Then if you are still having a problem it's a different issue to this thread so start a new thread with your problem.
Late to the party and opened up both Vegas 19 and 20 tonight which of course did not work, so luckily found this thread and quickly downloaded the fixed versions and now 19 and 20 load fine. Thanks to all but must say this kind of thing has never happed to me and I have been using NLEs since 1992. Yikes. Please someone post a detailed explanation of exactly what happened to edify us all. If server certificates, exactly what Dlls and why. And if it was a problem with Magix server side startup validation please rewrite the program so this never force closes paid software again. When we're billing clients by the hour and facing deadlines the software should default to assuming we own it when we start it rather than closing it like we're running some sort of cracked version.