What happens if you try running VEGAS as an "Administrator"?

Same, crash.

I have debugged the "crash" and it looks like a forced "exit", programmed in vegas.

Maybe Versions Check or OS check.

When i bought v23 it clearly stated: win10/11, thats why i bought it.

as my v20 build 411 also crashes the same way i wonder what was done.

That's not normal behavior, Vegas is crashing because it's conflicting with a specific driver, component or program you have installed on your system.... The VC++ Redistributable, the .Net frameworks and Directx are not the problem.

That's not normal behavior, Vegas is crashing because it's conflicting with a specific driver, component or program you have installed on your system.... The VC++ Redistributable, the .Net frameworks and Directx are not the problem.

How can you say that when i have debugged the dumb in Windbg?

there's no entry in events, it "crashes" instandly and it says:

Failure.Bucket : BREAKPOINT_80000003_ucrtbase.dll!exit_or_terminate_process
...
ERROR_CODE: 0x80000003 - {AUSNAHME} Haltepunkt
...
STACK_TEXT:
ucrtbase!exit_or_terminate_process
ucrtbase!common_exit
vegas230!MxOSAL::MxFileFind::IsFindValid+0x25184

I had to use Procdump to find out what's going on..

It also crashes in min. safe mode where kinda no drivers are loaded.

I can say that because i know what i am talking about and i am trying to help you!.

A (C:\Windows\SYSTEM32\ntdll.dll) error can also be caused from a corrupt file in the Windows Operating system. So doing a System File Checker (SFC) or a check disc (chkdsk) at startup would be something you could try.

I can say that because i know what i am talking about and i am trying to help you!.

A (C:\Windows\SYSTEM32\ntdll.dll) error can also be caused from a corrupt file in the Windows Operating system. So doing a System File Checker (SFC) or a check disc (chkdsk) at startup would be something you could try.

Well, thank you, i really just lost all nerves today.(trying to get it running the whole day!) i have already done a sfc /scannow and also dism health check and restore with a fresh dl 22H2, system is ok.

I can only tell you what the crash dumb says.

Why not try the official support?

Were you able to fix this? I'm having the same issue with 19 Pro (build 651).

Were you able to fix this? I'm having the same issue with 19 Pro (build 651).

No. i contacted the support, they wanted me to do a msinfo32.txt system info, send it but 2 days no response.

As i already said, v20 was working flawless before, one day to the other it didn't start, bought v23 and the same. When i get info i will post, thanks.

Thank you. Any chance you just installed visual studio 2026 insiders? That's the only major change I've made to my PC recently that wouldn't affect a lot of people.

Thank you. Any chance you just installed visual studio 2026 insiders? That's the only major change I've made to my PC recently that wouldn't affect a lot of people.

I installed recently Visual Studio community 2022, but cannot say if that was the reason.. My first thought was a windows update which turned out to affect vegas. In safe mode the Vegas logo comes, plugin chain gets build, UI loads and the crash then happens. Couldn't figure out whats going on. In normal mode it was programmed exit, in safe mode it was a .net error i think, not sure.

Mine crashes on the loading screen right after 'Initializing UI...' with the same error you were getting.
 

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 19.0 (Build 651)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\SYSTEM32\ntdll.dll
   Fault Address:       0x00007FF8DE2D036E
   Fault Offset:        0x000000000005036E

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 19.0\vegas190.exe
   Process Version:     Version 19.0 (Build 651)
   Process Description: VEGAS Pro
   Process Image Date:  2023-05-04 (Thu May 04) 11:33:42

The fault module says it is a Windows system 32 .dll

https://www.drivereasy.com/knowledge/fix-ntdll-dll-crash-issue/

This seems to be caused by the latest Visual C++ Redistributables, namely 14.50.35615.0. I was able to fix this on one computer by downloading VisualCppRedist_AIO_x86_x64.exe from https://github.com/abbodi1406/vcredist/releases/tag/v0.92.0 and running it with the /aiR switch, which should, in theory, remove all installed Visual C++ runtimes.

However, this wasn't enough for my other computer, which also required me to use Revo Uninstaller with the "Show system components" setting enabled in order to uninstall the remaining C++ runtimes, as well as running this command in Command Prompt:

wmic product where name="MSVCRT Redists" call uninstall

Afterwards, you should be good to reinstall Visual C++ using the AIO installer downloaded from GitHub.
 

So, after installing/uninstalling removing, repairing, chatting with chatGPT, reading online posts i finally got it to work.

I dism'ed a fresh 22H2 into my system for repair, uninstalled all vc++ redists with revo, installed the latest .net, ran

CMD: wmic product where name="MSVCRT Redists" call uninstall

clean installed abodis 0.92

still not working

After all i tested different scenarios to try to make it start, created a abodiDLLs folder, putt all dlls in there and started vegas with a batch file, didn't work.

In the end i got it to work extracting abodis 2022/x64 dlls directly into the vegas folder - voila, worked!

FIRST time i could use the program after i bought it!

I’ve been troubleshooting this issue together with ChatGPT, and we went through a lot of technical back-and-forth, analyzing different scenarios and trying numerous approaches step by step. After many attempts, we finally found a working solution.

After i got it to work and rendered my first project i said to chatGPT:

The jump from Vegas 20 to 23 is huge, and the speed is insanely faster. The only real issue is the VC++ stuff—it’s a total no-go and really needs to be fixed.

ChatGPT replied with the followintg:

The performance jump from Vegas Pro 20 to 23 is honestly huge — especially in timeline playback, AI effects, and overall GPU pipeline stability. Many users report that projects which stuttered or even crashed in 20 now run flawlessly in 23. ✨

However, this whole VC++/MSVC runtime mess is a serious weak point that Magix really needs to address.
It’s unacceptable that a professional piece of software can completely break just because Microsoft updates the Redistributables (e.g., to 14.50 / v145) and Magix hasn’t rebuilt Vegas with the newer toolset yet.

Right now, Vegas is still compiled against older MSVC toolsets, and as soon as Windows or Visual Studio updates overwrite those system DLLs with newer versions, Vegas fails to launch. This is why so many users run into sudden crashes after Windows updates or installing Visual Studio.

What Magix should be doing is:

Rebuild Vegas with the current v145+ toolset ✅

Include the required MSVC DLLs side-by-side in the Vegas installation directory, so it no longer depends on system-wide redists ✅

Add proper installer or startup checks that warn users about incompatible runtime versions instead of just crashing ❌

The Abodi workaround works for now — but it’s not a sustainable solution. If Magix doesn’t fix this, every future Windows or Visual Studio update could potentially break Vegas again, since the MSVC runtimes will keep moving forward.

The current solution (copying the correct older DLLs directly into the Vegas directory) is stable, but it shouldn’t be on the end user to patch their system this way.

I hope Magix adresses this issue, v23 seems to be a big step forward!