Ciao a tutti. ho avuto lo stesso problema ieri. 😫

Dopo averci sbattuto la testa per una giornata intera alla fine ho risolto in questo modo:

Ho scaricato la precedente versione di Visual Studio 2013 (VC++ 12.0) (non più supportato) e l'ho avviato per rimuovere la versione (avvio setup disinstalla)

poi ho scaricato e installato nuovamente la più recente Visual C++ Redistributable v14 e ho riavviato Win11

Tutto funziona perfettamente 😍

la pagina dove ho scaricato tutto se non dovessero andare i suddetti link è questa: https://learn.microsoft.com/it-it/cpp/windows/latest-supported-vc-redist?view=msvc-170#visual-studio-2013-vc-120-no-longer-supported

As a non nerd with a new Win 11 installation that could not open Vegas Pro 23, I followed W.O.L.F.'s advice on syswow64 and system 32 file swapping and ran into a lot of permissions issues, a few of which I couldn't solve, so I tried JUST replacing the syswow64 vcomp140.dll with the syswow64 vcomp140.dll from a working Windows 10 and the system32 vcomp.dll with the system32 vcomp.dll from the working windows 10. Rebooted and Vegas Pro 23 finally for the first time got past the startup hang. Seems to be working now although I haven't done a project yet. If you have an old Win 10, the old dlls will work.

Since a lot of people have troubles with this, i will soon make a software to fix everything automatically .

(Forgot to say here, but software need to run in admin to work with Vegas installations that are in the Program directory, same for the default install path .)

Thank you @W.O.L.F for helping making this small app fixer for the community 🙂🙏

Yw ! Hope it worked, i automated the easiest fix i made, also had some fun making the software (like in the images, lel), i never tested the software under real conditions, but files are copied successfully while testing, so i think it's fine, i tried to make it simple to use, the thing that took most of the time was making my servers work with the new SSL, it was in remote control and it was so laggy i had to wait to be back home to set up the website, lel !

Anyway, if the community need another softare, i'm ready to help !

Hi @W.O.L.F, many thanks for the tool - which worked great on Vegas Pro 19. In my case Vegas 19 died following the installation of the V8.0.9.10 update to TMPGEnc Video Mastering Wizard 8, which also installed .Net 10.0 Desktop Runtime (V10.0.0). I spent many hours unsuccessfully trying to fix it and ended up creating a dual-boot system with a clean copy of Windows 11 into which I installed Vegas Pro 19, as I had some video I needed to edit urgently. I'd removed Vegas Pro 19 completely from the original OS so I re-installed it and, as expected, it failed to start. I tried your tool which sorted the problem and Vegas 19 worked OK, so I then removed Vegas (again) and upgraded to Vegas Pro 23. Although the installation went OK Vegas Pro 23 failed to start, and on running the tool again it came up with a "Failed Successfully" message and didn't fix the issue. As I now have a dual-boot setup I followed @ahb's post and booted into the working OS, then copied the two known-good files vcomp140.dll (...Windows\System32) and vcomp140.dll (...Windows\SysWOW64) into the faulty OS (**note that despite the filenames, these two files are different**). I rebooted into the original OS and Vegas Pro 23 now seems to work fine. When Vegas 19 failed there were no error messages in the Windows logs but with Vegas 23 there were two error messages, which I can post if you need them. Hope this helps!

Yw ! If you had issues with the tool, it's mostly because you haven't opened it in admin mode, i did it really quickly, so i haven't made proper error messages, so it can be because it's not in admin (you need admin to allow the software to write to the Vegas directory), or because files are locked, i guess you haven't opened it in admin the second time, glad this helped and thank you for your review !

Yw ! If you had issues with the tool, it's mostly because you haven't opened it in admin mode, i did it really quickly, so i haven't made proper error messages, so it can be because it's not in admin (you need admin to allow the software to write to the Vegas directory), or because files are locked, i guess you haven't opened it in admin the second time, glad this helped and thank you for your review !

Hi @W.O.L.F I thought I did open it as admin, but to be honest I *really* needed to get Vegas running again so I might have missed that.... Thanks again though!

Wow. WOLF, thanks so much. I hadn't opened Vegas in a few months but needed to do some work on an old project. Much to my surprise, none of the 5 versions of Vegas I have installed would open. Hadn't been on the Forum for a while either so I was a bit dumbfounded. downloaded your fix and voila, back in business. Great job, really generous of you. Thanks again.

THANK YOU W.O.L.F. !!!!
Thanks a million.

Until last week, everything was working fine with Vegas Pro 23, but last Wednesday, I ran into a hell of crashes, not even able to get to the UI. Either ntdll or kernell.dll errors all the time, although nothing had changed on my PC.
The ticket I sent to support only got me answers from the AI assistant, which proved to be completely inefficient. Are there no human beings left in the support team?
And what the hell caused this nightmare out of the blue?

Anyway, it's working again so far, thanks to you, W.O.L.F.

It was Microsoft.

Yw ! ^-^
And yes, this mess was caused by Microsoft, something in the MSVC runtime was shipped broken, meaning that installing VS2026 with some workloads, software depending on this MSVC, and even maybe Windows updates could just have installed the broken MSVC, breaking Vegas and maybe other software, i guess they haven't did proper unit testing, on very important SDK, you must do unit tests for everything, i hope they already fixed that, else, well, R.I.P .

Hi ! I made the software and finally published it, feel free to check it if your Vegas still have the issue !

 

https://hubaxe.fr/random/vegas.html

 

Of course, it's a little software, i haven't really finished it but it work as-it, so, i think it's fine, if you have any feature request or question, feel free to ask here or by mail .

Wow. I was a beta-tester for 'Sony' Vegas since whenever they first bought it from the Sound Forge guys back in the late 90's, can't remember the exact timing of all that. Anyway, I battled away with legends like Grazie for decades putting up with endless effing Vegas crashes and just a nightmare a lot of the time. It hasn't been so bad since Magix took over thank goodness, the point is, I could usually fix any crashes with various DLL issues and whatever, but this particular crash (not a Vegas error obviously, a microsoft issue) had me stumped, tried everything, all the msvc 'older versions' and do this and do that and bulldust, nothing worked. Your FIXER program FIXED it W.O.L.F. Thank you so much! Really appreciate it. Now I can finally finish that video I started in 2001. Cheers.

Hi ! I made the software and finally published it, feel free to check it if your Vegas still have the issue !

 

https://hubaxe.fr/random/vegas.html

 

Of course, it's a little software, i haven't really finished it but it work as-it, so, i think it's fine, if you have any feature request or question, feel free to ask here or by mail .

Wow. I was a beta-tester for 'Sony' Vegas since whenever they first bought it from the Sound Forge guys back in the late 90's, can't remember the exact timing of all that. Anyway, I battled away with legends like Grazie for decades putting up with endless effing Vegas crashes and just a nightmare a lot of the time. It hasn't been so bad since Magix took over thank goodness, the point is, I could usually fix any crashes with various DLL issues and whatever, but this particular crash (not a Vegas error obviously, a microsoft issue) had me stumped, tried everything, all the msvc 'older versions' and do this and do that and bulldust, nothing worked. Your FIXER program FIXED it W.O.L.F. Thank you so much! Really appreciate it. Now I can finally finish that video I started in 2001. Cheers.

Funny that Vegas Pro 23 is still creating a path to the Prerendered files folder C:\Users\darren\AppData\Local\VEGAS Pro\21.0\

Nice.

It's odd that this problem persists, since Microsoft maintain that the latest releases of MS VC++ 14.50 fix the vcomp140.dll compatibility problem.

Certain apps may be installing older versions.

Perhaps so - but then simply downloading and running the latest Visual C++ Redistributable, running it and selecting "Repair" should fix it.

I appreciate, though, that this isn't something a typical end user should be expected to do ...