Magix still not responded after 12 days after their suggestion to install the beta. Getting very frustrated.. I have contacted them twice since.

I am having the same issue as you but only since Build 302. When I rolled it back to the original install version the application would run and I was able to move the project back to Vegas Pro22 which meant that I could at least continue with my work. I had a problem with it not display the video on certain mov file that I created using Apple Motion which is why I was asked to try the Build 302 beta. The mov file worked in Vegas Pro 22 but not in VP23. I as well have not heard anything from support for days. They could at least acknowledge the problem rather than just ghosting us.

@DCrowe here is a suggestion. First, I would hazard to guess that support would need an actual problematic file(s) to test to see if this is a "global" issue, or an individual issue.

Start a new post, and include all the necessary detailed information from this POST specifically "B" and "C". Right now, your User Profile is blank. Add your computer specs to your Signature like mine below. No generalities, but specific make/model/etc..

Upload to the cloud a sample of a file that doesn't work for others to test. You will get faster results/possible answers from the forum than from Support. Then, if there is an issue with the actual file (also include what created it), a Moderator can help to escalate it.

I've had issues in the past and current issues, but I've never contacted Support. I'll ask here is someone else can verify the issue first. Then "nag" a Moderator if it is an "everyone" issue to possibly get it moved up the bug "food chain".

An hour after I posted Magix responded to my message from end September not last week. They asked for my msinfo report which now sent. I have offered the latest crash reports for both v16 and v23 so will see what they say.

So Magix have once again not responded to their own support system messages. They asked me for logs etc which I sent them 10 days ago and still no answer despite chase ups. It has now been a month since I last managed to run any version of VP. I have downloaded Resolve and going to have to learn that if they don't answer soon.

I'm unsure if you've tried resetting Vegas Pro back to its default (factory) settings, but to do is straightforward as outlined in https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

II that doesn't work, the next but more aggressive possibility is to do a clean uninstall of Vegas Pro which includes deleting many entries in the registry, and then re-install Vegas Pro - please see https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-do-a-clean-uninstall-of-vegas-pro--111205/

The latter approach completely clears Vegas Pro from the computer and thus hopefully clears any registry corruption that may have previously existed.

Yes reset everything. Deleted the apps, folders and registry (ones I have found) either manually or using BCUninstaller. Removed NVIDIA via clean tool and reinstalled. Reinstalled earlier VP versions. All of them crash just as the main window appears. It is not a project as that is turned off for auto-start.

I will go through the clean uninstall thread again but sure I have already done that. I am totally up to date with Windows updates through Oct 2025 as well. Ta.

Did the uninstall again and cleaned everything. No sign of vegas or sony anywhere in registry. Rebooted, reinstalled VP23 beta (which Magix sent me to try) and still crashes as soon as you get to the main window with the welcome screen. Whatever VP is doing at that point it does not like it and affects all previous versions as well.

@jxb You aren't one of the people affected by Visual Studio are you?

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

RogerS. This is perfectly possible so thanks for pointing this one out. I have told Magix that I run Visual Studio in the msinfo files they have had.

I do use VS2022 and VS2026 (in it's beta format). Those systems work OK of course but first I have heard of this. I tried running the MSVC installer in the link but made no difference. I do read in the threads about manually replacing v140 of MSVC from a working system (I have a VM system that is working without NVIDIA) but this seems like may only be a stopgap. Both VS2022/26 and Windows 11 are being updated regularly. This does seem to be a Magix problem they need to fix and surprised beta 302 does not include it.

Does anyone have the working MSVC 140 files mentioned in the link I can put in the VP folder so it reads from there instead of the system folders? There are no MSVC files in the Vegas folder.

Roger. You are a star!!

This worked perfectly - I had realised from earlier threads linked from here that it was loading an incompatible version of MSVC but was not sure which files it was complaining about as the logs did not identify them and "processmonitor" was just chucking 100s of files at me. By following that thread by Nick Hope it fixed the problem that Magix seem incapable of fixing even though I suspect they must know about it from reports here and elsewhere.

Thanks for following up on this. Really appreciate it.

John

So glad this worked for you!

Their engineers are aware of this as they commented in these threads and support should be as well, though it's on Microsoft to provide a permanent fix.

@jxb  ... it would be good if you would tag RogerS's comment as the 'Solution' as his comment led you to overcome the problem.