VEGAS Pro 23 crashes on startup after splash screen (Build 302, Window

edward-lopez wrote on 12/30/2025, 9:32 AM

Hardware:
- Desktop: Alienware (custom configuration)
- CPU: Intel Core Ultra 9 285K
- GPU: NVIDIA GeForce RTX 5080 (16 GB VRAM)
- RAM: 64 GB DDR5
- Storage: 4 TB Gen4 NVMe SSD
- Power Supply: 1000W Platinum

Operating System:
- Windows 11 Home (64-bit), fully updated

VEGAS Version:
- VEGAS Pro 23
- Version 23.0 (Build 302)

Graphics Configuration:
- Discrete NVIDIA GPU (no hybrid / integrated graphics in use)
- NVIDIA drivers fully up to date
- No external GPUs or capture devices connected

Crash Behavior:
- VEGAS Pro splash screen loads normally
- Progress bar completes
- Main VEGAS window briefly appears
- Immediate crash with “VEGAS Pro has stopped working”
- Crash occurs during application initialization
- No project is loaded; crash happens before user interaction

Note: Crash appears to occur during initialization / plug-in or graphics subsystem loading, not during project access.
This appears to be a startup-level crash related to VEGAS Pro 23 Build 302 rather than project media, plug-ins, or user configuration.

Comments

Steve_Rhoden wrote on 12/30/2025, 9:42 AM

@edward-lopez First, make sure you have the latest .net framework components installed for your specific system.

jetdv wrote on 12/30/2025, 3:20 PM

https://www.vegascreativesoftware.info/us/forum-search/?query=0xe0434352

Reyfox wrote on 12/30/2025, 3:50 PM

It is clearly a Windows issue. System 32\Kernalbase.dll

edward-lopez wrote on 1/1/2026, 4:20 PM

I wanted to share a confirmed fix for VEGAS Pro 23 crashing immediately on launch under Windows 11, often referencing KERNELBASE.dll and closing before the splash screen appears.

Reinstalling VEGAS, repairing Windows, updating GPU drivers, and installing standard VC++ redistributables DID NOT resolve the issue.

System

Windows 11

VEGAS Pro 23

NVIDIA GPU (NVENC capable)

Cause (likely)

VEGAS Pro 23 relies on MSVC v143 runtimes.
On some Windows 11 systems, the global MSVC runtime bindings appear to be mismatched or corrupted, causing VEGAS to fail during initialization.

VEGAS does not always correctly resolve the required runtime from the system path.

Working fix (non-destructive, VEGAS-only)

This fix forces VEGAS to load a known-good local MSVC v143 runtime, without modifying any Windows system files.

Step 1 – Install MSVC v143 (Build Tools only)

Download Visual Studio 2022 – Build Tools

During installation:

Select Individual components

Install ONLY:

MSVC v143 – VS 2022 C++ x64/x86 build tools

Do NOT install workloads, .NET, or SDKs

Reboot

Step 2 – Locate MSVC runtime DLLs

Navigate to:

C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Redist\MSVC\<latest version>\x64

Open the folders:

Microsoft.VC143.CRT

Microsoft.VC143.OpenMP

Step 3 – Copy required DLLs

From Microsoft.VC143.CRT, copy:

concrt140.dll

msvcp140.dll

msvcp140_1.dll

msvcp140_2.dll

msvcp140_atomic_wait.dll

vcruntime140.dll

vcruntime140_1.dll

From Microsoft.VC143.OpenMP, copy:

vcomp140.dll

Step 4 – Paste into VEGAS program folder

Paste all DLLs into:

C:\Program Files\VEGAS\VEGAS Pro 23

Replace files if prompted.

This does not alter Windows system files — it only affects VEGAS.

Result

VEGAS Pro 23 launches normally

No KERNELBASE.dll crash

No splash-screen termination

Stable across reboots

Conclusion

This appears to be a runtime resolution issue, not a corrupted VEGAS installation.
Providing VEGAS Pro 23 with a local, correct MSVC v143 runtime resolves the crash reliably on Windows 11 systems.

Hopefully this helps others experiencing the same issue.

Reyfox wrote on 1/1/2026, 4:36 PM

I have none of those .dll's that you mentioned that should be copied to C:\Program Files\VEGAS\VEGAS Pro 23.0

bvideo wrote on 1/1/2026, 6:54 PM

@Reyfox All those files are a solution for people who use Microsoft Visual Studio and got screwed when they upgraded to the latest.

https://www.vegascreativesoftware.info/us/forum/warning-ms-vc-14-50-v145-kill-vegas-permanently--150332/