VP23 crashes at Creating Windows on startup

jxb wrote on 9/24/2025, 4:41 AM

I thought this was just VP23 r278 but also now occurs in VP22 & VP21 which has never been the case. The program starts and gets to the "Creating windows" part then crashes out. I have sent Magix the crash dump but not heard anything back yet.

I have uninstalled & reinstalled VP23. Updated the NVIDIA drivers, run scansfc & DISM, cleared as many temp folders etc. I can find, reset the settings at startup, and now at a loss. I see others had this error many versions ago but nothing recently.

It sound to me like a faulty Windows file. The basic info returned is:

Application Name: VEGAS Pro
Application Version: Version 23.0 (Build 278)
Problem: Unmanaged Exception (0xe0434352)
Fault Module: C:\WINDOWS\System32\KERNELBASE.dll
Fault Address: 0x00007FFC3EDA66CA
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-04 (Thu Sep 04) 16:43:08

The event viewer is showing this error every time the crash occurs.

The attempt to locate the Open procedure "OpenLsaPerformanceData" in DLL "C:\Windows\System32\Secur32.dll" for the "Lsa" service failed with Win32 error code The specified procedure could not be found.. Performance data for this service will not be available.

Followed by these warnings:

The Open procedure for service "MSDTC" in DLL "C:\WINDOWS\system32\msdtcuiu.DLL" failed with error code The system cannot find the file specified.. Performance data for this service will not be available.

The Open procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed with error code The device is not ready.. Performance data for this service will not be available.

Windows 11 Pro 24H2

Any thoughts please as unable to edit anything?

Thanks - John

Comments

RogerS wrote on 9/24/2025, 9:48 AM

Did something else change on the system that could be affecting all of them? Do a rollback to an earlier state?

Otherwise the official support might have an idea what these codes are referring to as I don't know and never saw them.

jxb wrote on 9/24/2025, 4:47 PM

I got a bit further by deleting the autosave.veg.* files in the AppData folder which brought up the main screen further than the "creating windows" part. It then crashes when the startup welcome window appears with the same error. The crash dialogue appears which even stops me turning off that welcome screen in case that is what is causing it.

I then completely wiped VP23 and the AppData folder, reinstalled, but still same error at same position.

So playing with ChatGPT and the event log error messages to see if they can help.

jxb wrote on 9/25/2025, 4:54 AM

Tried all kinds of suggestions from ChatGPT but to no avail including removing all add-ons etc. plus audio & video drivers. v21, 22 & 23 all are crashing with what looks like the same error. Now going to try creating a new Windows profile which a pain considering all my other systems are working perfectly. Have not yet contacted Magix as wanted to exhaust all options first.

jxb wrote on 9/25/2025, 5:02 AM

And no, using a brand new profile still crashes so not profile related. Now trying ChatGPT suggestion of removing the NVIDIA driver (which has not been updated for weeks) and trying a basic graphics driver.

RogerS wrote on 9/25/2025, 7:08 AM

Not sure ChatGPT has enough data to make meaningful recommendations.

For the NVIDIA driver you can wipe all traces of the old one here and install the current studio driver: https://developer.nvidia.com/downloads/cleanup-tool

jxb wrote on 9/26/2025, 7:03 AM

Thanks for that link.

ChatGPT came up with all kinds of suggestions none of which worked. But as I'm having same problem with older versions of VP, and notepad fails a dependencies check, it suggest there is some sort of Windows corruption at root level. I have run all the usual tools though and even tried an in-situ Win11 upgrade (which itself failed to complete for reasons I am still investigating) it is rather annoying. As mentioned I am only having a problem with VP so think next thing is the NVDIA side of things as exremely reluctant to do a clean Win11 install as have a ton of programs data (and backups) that would need reinstalling as well.when all those systems are working perfectly.

jxb wrote on 9/26/2025, 8:28 AM

Cleaning, testing VP23, reinstalling NVIDIA, and testing VP23 still fails as does VP21 & 22. In the latter crashes at Initialising UI. Tried repairing Net Framework 4.8 but would not allow me to as says already installed even through the repair tool.

I suspect an update to 24H2 which occurred on 11th Sept is the culprit. Prior to that 24H2 was installed so this was just an update. I was able to use VP22 on 9th Sept without any problems. Windows Restore will not allow me to go back to the earlier date as, despite allocating enough space, it has removed the restore point.

Reyfox wrote on 9/26/2025, 9:53 AM

If Win 24H2 is an issue, I wonder if others are experiencing the same thing? I am still on 23H2 and VP18-23 open just fine on my computer.

andyrpsmith wrote on 9/26/2025, 10:23 AM

I'm on 24H2 with all the latest updates after pausing the updates after the ssd failure scare. V20/21/22 and 23 are opening fine. You could try and see if the Uninstall Updates option covers the update of 9th Sep.

jxb wrote on 9/26/2025, 11:10 AM

I have not had a problem with anything else and only that latest update is possibly a reason. Believe 25H2 is imminent.

EricLNZ wrote on 9/26/2025, 10:22 PM

I suspect an update to 24H2 which occurred on 11th Sept is the culprit.

@jxb Is that KB5065426? It installed on 10 Sept my time and hasn't caused any problems with my VP21.

On the same day the following NET updates were installed, and I wonder if they are relevant to the problem although you say you've tried repairing NET Framework 4.8:.

Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 24H2 for x64 (KB5064401)
.NET 8.0.20 Update for x64 Client (KB5066233)

jxb wrote on 9/27/2025, 3:06 AM

I have uninstalled and reinstalled KB5064401, Also repaired 24H2 via System Recovery as KB5065426 cannot be removed/reinstalled. Don't have the Net 8.0 update installed as using Net 9.0.

Currently setting up a VirtualBox environment to test it it. Resolve works OK. All very weird. Thanks.

jxb wrote on 9/27/2025, 7:52 AM

Well it works in VirtualBox using same 24H2 from a brand new ISO installer. So now doing some clever things with that update forcing Windows to rollback KB5065426. Fingers crossed this time.

Reyfox wrote on 9/27/2025, 10:49 AM

I've used Windows Sandbox (using Win11 Pro), but there is no GPU accessed. Does VirtualBox access the GPU?

Eric-Weichhart wrote on 9/28/2025, 9:18 PM

I had the same error last week with Vegas 22.

Re-installing the Nvidia Studio driver with clean settings did fix it for me. Not doing the clean install did nothing though

jxb wrote on 9/29/2025, 7:14 AM

Not sure about VirtualBox and GPU (probably not the NVIDIA) but is a means to test it works outside the primary windows setup.

I did a clean of NVIDIA and reinstalled latest Studio driver but still no joy. Even downloaded latest Win11 ISO and ran that last night but nothing.

I'm waiting for Magix to come back to me as sent them a support request on Friday.

Thanks - John

Reyfox wrote on 9/29/2025, 8:17 AM

@jxb just a suggestion, add your computer specs to your User Profile>Signature like mine below. It is one area where those trying to help will look.

GaryX wrote on 9/29/2025, 9:20 AM

Not sure about VirtualBox and GPU (probably not the NVIDIA) but is a means to test it works outside the primary windows setup.

I did a clean of NVIDIA and reinstalled latest Studio driver but still no joy. Even downloaded latest Win11 ISO and ran that last night but nothing.

I'm waiting for Magix to come back to me as sent them a support request on Friday.

Thanks - John

I also wait for further info from magix, im on win 10 pro, vegas 20 stopped working, no splash screen, just ms crash report. So i bought v23 and it crashes the same way. did everything i knew to fix, dism repair with fresh 22H2, sfc /scannow, uninstalled all .net & VC++ runtimes and only installed the latest.. nothing helped. I've debugged the crash with procdump and analyed with Windbg. When i run vegas in safe mode i come to the UI and then it crashes too. I am a vegas user since v11, so not new to vegas. Also tried to run with software rendering, all the same. Also for me it looks like a Windows update can be the problem, seen the .net 4.8 update but also another one. Hope Magix comes back to me, as they are quiet after i send my msinfo text file.

Reyfox wrote on 9/29/2025, 9:29 AM

@GaryX nice computer. I've been on Win11 Pro for several years now. I did it because it was supposed to handle the multicore/thread better. I know you might not want to hear this, but it is an experiment. Get an NVME drive and install it in the other slot on your motherboard. Install Win 11 Pro along with all drivers. Then Vegas Pro. you can dual boot easily. I still have my Win 10 Pro installed, but to make sure I've migrated everything I will use.

GaryX wrote on 9/29/2025, 9:56 AM

@GaryX nice computer. I've been on Win11 Pro for several years now. I did it because it was supposed to handle the multicore/thread better. I know you might not want to hear this, but it is an experiment. Get an NVME drive and install it in the other slot on your motherboard. Install Win 11 Pro along with all drivers. Then Vegas Pro. you can dual boot easily. I still have my Win 10 Pro installed, but to make sure I've migrated everything I will use.

Thanks for the reply. I will upgrade when i get a new GPU. As i also do VR in MSFS 2024 and MS removed WMR with the 23H2 update and the latest AMD 25.9.2 driver is the first one which supports the Oasis VR driver i will wait. As Nvidia shifted the 5080 super to next year that was my plan. If AMD comes around with something >16gb Ram i might stick to AMD. But as i said, i will upgrade when my time window is ready. Won't do it because someone decided to remove support for something that worked very well.

jxb wrote on 10/12/2025, 6:46 AM

All Magix have asked me to do is try the next beta but that still failed as well. Went back to them with crash logs etc but still no response after a week. Tried v16, 18, 22 & 23 - all crash even after using BCUninstaller to remove anything related. Resolve works fine.

Howard-Vigorita wrote on 10/12/2025, 11:22 AM

... uninstalled all .net & VC++ runtimes and only installed the latest.. nothing helped.

@jxb Did you try following the Microsoft permalinks to run both the X86 and X64 Latest Supported Redistributables?
https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

jxb wrote on 10/12/2025, 1:43 PM

Yes I did and have again with no change. Thanks

Does anyone know where the option is stored which tells v23 to not display the welcome screen? It crashes every time that it appears. Probably nothing to do with it but if I can stop that appearing then can dismiss that as a cause. Obviously in v16 there is no such thing but crashes at a different point so nearly 100% certain not that but worth a try.

Reyfox wrote on 10/12/2025, 1:51 PM

Have you run sfc /scannow as administrator in the Command Prompt? Also here is a LINK for it along with DISM