[WARNING] : MS VC++ 14.50 (v145) kill Vegas permanently !!!

W.O.L.F wrote on 9/24/2025, 2:29 PM

Hi ! I'm a developer and i installed Visual Studio 2026 Insider, containing Microsoft Visual C++ Redist 14.50, however, installing VS2026 with some workloads that update MSVC or just installing this MSVC permanently break Vegas, like, will never start again, and any versions of Vegas (so, including 23, 22, etc), and uninstalling Visual Studio, the specific workload, or even the MSVC version directly don't fix the issue, and restoring the files don't work at all, unfortunately, this version of VC++ will soon be used on other MS products or other software, if they do that, it will break any version of Vegas permanently, and downgrading MSVC doesn't work, maybe a specific file is edited, or maybe this version is corrupted, or maybe it's because of registry keys or other stuff, i will contact Microsoft as well to fix this issue, if the Vegas team see this, can you please check on a VM please (don't test this on your PC except if you have a restore point) ?

You can't fix this for now, i'm working on a tool that completely revert MSVC v145's installer's stuff so i can use Vegas again, for now, i can't use it at all, i start Vegas, and it crash directly after finishing loading, and i don't have a restore point to revert this, so, don't install VS2026 with a workload that add MSVC (.NET Desktop workload work fine) and use VS2022 instead for now, or don't install latest MSVC, remember that only a restore point made prior MSVC's installation can fix this, if you already have this issue, you can contact me (at least a day or two after i published this post), idk if i can publish my mail here, so if needed, ask here, and if you want, you can try in a VM and send the errors to Microsoft so they can fix their MSVC .

Comments

Weegeepie wrote on 9/24/2025, 2:31 PM

I have this problem too, pls fix

Luigiplier wrote on 9/24/2025, 2:34 PM

Yep, can confirm got the same problem a couple of days ago!

VEGASDerek wrote on 9/24/2025, 6:10 PM

We are investigating.

VEGASBalazs wrote on 9/30/2025, 3:42 AM

It's an issue with the redist, already reported just recently: https://developercommunity.visualstudio.com/t/omp_set_dynamic-causes-OMP-loops-to-cras/10967413
Contrary to the "resolution" there, the latest VS2026 insider doesn't yet have the fix. The affected DLL is vcomp140.dll version 14.50.35503.0

VEGASBalazs wrote on 9/30/2025, 11:09 AM

One possible solution is to uninstall the "Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.50.35503.0" item through the Windows settings "Apps & Features" section and then install an earlier redistributable.

W.O.L.F wrote on 9/30/2025, 11:32 AM

Thank you, but i don't think it will work for everyone, i deleted it from Apps & Features and it didn't worked at all, the files in System32 and SysWoW64 with 140 in the name are still there after deletion, and installing an older version don't override more recent files, it just add stuff in some directories and in the registry, it's why after uninstalling, installing is nearly instant compared to first install or update, i had to roll back system files myself to make it work, managed to do that while Windows is running, but can be hard for some people, this was tested on Windows 10, a custom Windows 10 edited to look like 7, and on Windows 11, haven't tried to repair on Windows 11, so maybe it can depend on the Windows version, i don't know, but if deleting it from the settings don't work, try replacing system files from System32 and SysWoW64 (to restore 32b version too of MSVC) with 140 in the name, you may need to do a takeown on the ones with "clr" inside, you can use a software called Everything and put (140 "C:\Windows\System32") for example to list every files in System32 with 140 in the name, and then delete them and replace them from the one you got from a working Windows install that work fine with Vegas .

GaryX wrote on 9/30/2025, 12:07 PM

i am on win 10 pro also, i had a working vegas 20 pro, it stopped working after installing Visual Studio community 2022, so after investigating the crashes and dump i uninstalled all VC++ + .net redistributables and it didn't help. So i thought ok, get vegas 23, might be a bug which won't get fixed and bam, vegas 23 also doesn't start. Not had it running once :( hope there is a fix soon!

W.O.L.F wrote on 9/30/2025, 4:13 PM

Hi GaryX, like i said, uninstalling don't help, updating or installing MSVC actually edit system files, and uninstalling or downgrading don't put the old versions back, contact me at wolf@hubaxe.fr, i will help you fix your Windows installation .

If you think you can do it alone, you can try getting every files from System32 and from SysWoW64 having 140 in their name from a Virtual Machine with Visual Studio 2022 and C++ workload installed and then put them into your main installation, may need to close every software that use MSVC, or using safe mode can be easier, also, delete the files before replacing them to be sure you actually replaced them, if you don't want to do the VM thing, i can give you a zip with the files to put into System32 and SysWoW64, they are from the MSVC that come with VS2022 .

GaryX wrote on 10/3/2025, 4:00 PM

Hello and thanks for the infos.

I've uninstalled all vc++ redists in revo, uninstalled the debug redists from VS also in revo, ran in CMD: wmic product where name="MSVCRT Redists" call uninstall

clean installed abodis 0.92

still not working.

 

Magix has to fix that, short or long more other users will be "infected", repairing a system because of a microsoft package, is not the users fault!

I have email contact with magix and till now they did not provide any help, all they did was linking the new beta to me. I have NOT had one successfull run of vegas 23 since i bougtht it!

 

btw: in safe mode i am able to get the UI opening, but also crashes when a window openes in fron of the UI.

W.O.L.F wrote on 10/3/2025, 4:32 PM

Hi again GaryX, sorry to hear that Vegas support wasn't able to help you, i know i'm not part of Vegas's official team, but i can still provide unofficial support, feel free to contact me at wolf@hubaxe.fr so we can talk directly, i know how to fix this, i'm the one who resolved the issue first .

I will write a basic guide here, if you don't know how to do it or don't want to mess up everything, we can talk directly so i can guide you into the process, i can even give you the system files if you really want (and check the hashes & signatures), but taking system files yourself can be better .

Basically, you will need the Everything software by Voidtools (not an obligation, but it's easier this way) on the broken Windows install and on a clean VM (or any Windows 7+ install with a recent MSVC that doesn't break Vegas, installing Vegas or it's trial can update MSVC to a good version, doing that make sure you have a correct MSVC that isn't too old, try Vegas 22 or 23) . Also, after making this, installing again MSVC 14.50 will not break your computer, it will install it, but won't replace the system files again since it think you're already using latest ones, meaning that you can continue with Visual Studio 2026 without any issues (in theory) .

NOTE : Restarting your computer and making sure it doesn't have anything opened can help with the process, this don't need a restart, but since a lot of stuff rely on MSVC, doing that and closing every startup program can make sure you won't have to close each process manually .
When you have Everything and a valid Windows install, you can then open Everything on the broken Windows install and then put [140 "C:\Windows\SysWoW64"] and delete every file with a 140 in it, it's files related to MSVC 14.X also called MSVC v14X (14.50 is v145), and do the same thing with 140 "C:\Windows\System32" and delete stuff that are in System32, not subdirectories, you may need to do a takeown on files with clr in their names .
After deleting the files, first, don't worry, they aren't essentials and deleting them will not break your computer if you restart Windows before putting the good versions in your system .

So, take the working Windows install (that work with Vegas), and put 140 "C:\Windows\SysWoW64" and copy everything to a new directory called "MSVC 32", and do the same with System32 (excluding subdirs) into "MSVC 64", then, open those dirs into your broken install, and copy MSVC 32's files to SysWoW64 (SysWoW64 is actually System Windows on Windows64, so 32 bits system files, not 64 bits), and MSVC 64's files into System32 (System32 being for 64 bits system files, still called System32 for compatibility) .

 

Simpler version .../

1) Backup every files with a 140 in them from SysWoW64 and System32 (excluding subdirs) from a good Windows install .
2) Close everything that use MSVC or restart your PC (with the bad Windows install) and stop every app that opened at startup .
3) Delete files with 140 in the name from SysWoW64 and System32 in the bad install .
4) Copy back your backup files into SysWoW64 and System32 on the bad install, make sure you put SysWoW64's backup in SysWoW64 and same for System32's files in System32 .

 

Hope this help !

GaryX wrote on 10/4/2025, 2:56 AM

i got it to work, the first time now!

 

i extracted the abodi 0.92 / 2022 / x64 files directly into the vegas folder, voila, works. Have to test it later, but NO CRASH! ich werd bleede... 🙃

W.O.L.F wrote on 10/4/2025, 1:08 PM

OoOoOOoOOoo, nice ! Yep, putting MSVC into the Vegas directory work since it search the specific DLLs in the start directory, then in System32, but this mean that it will only fix this Vegas installation, and not fix every other programs that have the same issue, if you don't have issues with other stuff for now, it's okie dokie, but if another thing is broken, try to replace those files in System32 and SysWoW64, this fix the issue for every programs .

GaryX wrote on 10/4/2025, 2:05 PM

it means EVERYONE can have this problem so MS has to fix it! I have a thread over in Vegas forum -->

Vegas Pro 20 / 23 Crash on start

 

VEGASDerek wrote on 10/5/2025, 7:07 AM

it means EVERYONE can have this problem so MS has to fix it! I have a thread over in Vegas forum -->

Vegas Pro 20 / 23 Crash on start

 

Gary is correct. This problem needs to be fixed by Microsoft. They have acknowledged the problem and supposedly have a fix which will be released in the future.

W.O.L.F wrote on 10/5/2025, 11:11 AM

Yep, hope it will be fixed, if they release MSVC 14.50 in a next Windows update, then Vegas will have a very very bad time, and only because Microsoft haven't made enough unit tests, it's nice that they try to fix it, but they really need to fix it quickly especially for Visual Studio 2026 since VS is very popular and already embed the broken version, maybe new builds of Vegas could do something like checking the dll version and instead of loading the DLL from System32 if it's 14.50, then it can load an older version compatible with the 14.50 DLLs so don't need to embed every DLLs, or maybe the installer can show a warning or just update MSVC to a fixed version .

pldev wrote on 10/22/2025, 7:19 PM

Can anyone upload those extracted dlls into a compressed file so we can download it?

rayk wrote on 11/12/2025, 7:17 PM

Can anyone upload those extracted dlls into a compressed file so we can download it?

Effectively, you will only need the vcomp140.dll in VisualCppRedist_AIO_x86_x64.exe\2022\x64\System64 from the VisualCppRedist_AIO_x86_x64_92.zip file released on https://github.com/abbodi1406/vcredist/releases/tag/v0.92.0

S. https://developercommunity.visualstudio.com/t/Calling-omp_set_dynamic-before-pragma-o/10973188#T-N10998079 why.

I uploaded it here.

Unzip it directly into the VEGAS installation directory.