Comments

John wrote on 2/14/2026, 8:04 AM

Same here. Tried clearing cache first, no help. Tried re-installing Vegas. No help. Rolled back the recent display adapter driver for my Intel Arc 140V GPU - that also didn't help. I've run out of things to try.

also - I assume it was the recent graphics driver update because that was the only major thing that happened between "working" and "not working" but I have no actual data or message to prove that. Don't know what else it could be though and Vegas dies immediately on launch without even a splash screen so the graphics update seems most likely.

finally, when I re-installed it did get as far as registering the S/N but just crashes after that.

john_dennis wrote on 2/14/2026, 10:01 AM

Have you looked in Reliability History to see what Windows thought happened?

jimingo-1 wrote on 2/14/2026, 10:20 AM

I checked it and no errors. It was definitely the A770 update though because I was using Vegas right up until I performed the update. Then I shut off my computer, came back an hour later to use Vegas again and Vegas wouldn't start up.

I've tried unplugging my A770 and using my Radeon RX 6900 XT and I still get the error and Vegas still won't start.

john_dennis wrote on 2/14/2026, 12:09 PM

Is it possible this could be part of the mix?

https://www.vegascreativesoftware.info/us/forum/warning-ms-visual-c-14-50-v145-kill-vegas-download-the-fix--150332/

Howard-Vigorita wrote on 2/14/2026, 2:31 PM

I just updated the Intel Graphics drivers for my Nuc (Core Ultra cpu) from 101.8425 to 101.8509. After which vp23 and vp22 both gave a crash screen immediately after loading. Same drivers as for A770. I had to then reinstrall the C++ redistributables and reboot. I ran both the x86 and x64 permalinks partway down the page. This fixed both vp23 & vp22 for me.

John wrote on 2/14/2026, 2:46 PM

I just updated the Intel Graphics drivers for my Nuc (Core Ultra cpu) from 101.8425 to 101.8509. After which vp23 and vp22 both gave a crash screen immediately after loading. Same drivers as for A770. I had to then reinstrall the C++ redistributables and reboot. I ran both the x86 and x64 permalinks partway down the page. This fixed both vp23 & vp22 for me.

wow - thanks. I would not have thought to do that but it fixed my problem as well. And, apparently, thanks to Intel for breaking the C++ library? Which explains why rolling back the driver didn't help

Howard-Vigorita wrote on 2/14/2026, 3:33 PM

Might require one further step... after I did all that, Windows Update installed yet another Intel Graphics driver. 101.6129 which is much older. I didn't bother to test it. I just went into Control Panel, Display Drivers, Intel Graphics, Properties, and rolled back the driver. It went back to 101.8509.

anthony-chiappette wrote on 2/14/2026, 3:53 PM

Might require one further step... after I did all that, Windows Update installed yet another Intel Graphics driver. 101.6129 which is much older. I didn't bother to test it. I just went into Control Panel, Display Drivers, Intel Graphics, Properties, and rolled back the driver. It went back to 101.8509.

The first thing I do when installing windows is to disable driver updates via Windows update.

ASUS Prime Z590-A Motherboard with Intel Core i7 11700 8 Core / 16 Thread 2.50GHZ, 64GB Crucial DDR4 3200 (4 x 16GB), nVidia GeForce RTX5060 8GB GDDR7, SoundBlaster X AE5 soundcard, 3 x 4TB Samsung 860 EVO SATA 3 SSD, 2 x 8TB Samsung 870 QVO SATA 3 SSD, 1 x 2TB Samsung 980 Pro NVME PICE4 SSD, 2 X WD 4 TB NVME PCIE3 SSD, 2 X Viewsonic HD monitors, LG Blu-Ray writer. Windows 11 (latest build), currently using Vegas Pro 22 latest build, and limited VP23 use to gauge performance and ease of use differences. Videos come from 2 x Sony HDR CX-405 Cameras, XAVC-S MP4 @ 50Mbps 1080P 60fps video files. (Previously: 2 x Canon HFR800 cameras, MP4 files at 1920 x 1080 60p 35Mbps).