Can't even open my Vegas 23

Cokit wrote on 9/29/2025, 12:36 AM

I just bought Vegas 23 and installed it.
However, no matter what I do (I did clean reinstalling of veg23 multiple times), Vegas creates a window and crashes immediately.

Problem Description
Application Name: VEGAS Pro
Application Version: Version 23.0 (Build 278)
Problem: Unmanaged Exception (0xe0434352)
Fault Module: C:\WINDOWS\System32\KERNELBASE.dll
Fault Address: 0x00007FFD37DA66CA
Fault Offset: 0x00000000000C66CA

Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 23.0\vegas230.exe
Process Version: Version 23.0 (Build 278)
Process Description: VEGAS Pro
Process Image Date: 2025-09-05 (Fri Sep 05) 00:43:08

And no, I am not amd user. I've been solely using a GeForce graphics card and an Intel CPU.
Please someone help ; ;

Comments

Dexcon wrote on 9/29/2025, 3:41 AM

Another forum member has the same issue after installing Vegas Pro 18 on a new computer - https://www.vegascreativesoftware.info/us/forum/failure-to-boot-program-vegas-18--149815/ - but note the comment on that post:

That's a Windows issue. Google and see if you can find a solution to it.

A quick Google search results in:

https://www.bing.com/search?pglt=299&q=Fault+Module%3A+C%3A%5CWINDOWS%5CSystem32%5CKERNELBASE.dll&cvid=0bcb57eb887a4da580e42e18e9e4fc39&gs_lcrp=EgRlZGdlKgYIABBFGDsyBggAEEUYO9IBCDM1OTRqMGoxqAIAsAIA&FORM=ANNTA1&PC=EDGEDSE

Like the other post, you have not provided any specifics about your computer: GeForce - fine, but which one specifically; Intel CPU - again which one? A 3rd or 4th gen i3/15/17 or a much more recent i3/i5/i7/i9 - please be specific so as to avoid doubt. And which OS - W10 or W11?

When you say that you've 'clean installed' Vegas Pro several times, did you first clean-uninstall Vegas Pro as per the clean-uninstall instructions given in https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-do-a-clean-uninstall-of-vegas-pro--111205/ ? Merely uninstalling and re-installing Vegas Pro doesn't always fix problems especially if the problem lies in the Registry.