Intel A770 driver update (2/13/26) causes vegas 22 & 23 to not work

jimingo-1 wrote on 2/13/2026, 10:57 PM

I just updated to the latest Intel A770 driver today (2/13/26) and I can no longer open Vegas 22 or 23. I will try rolling back to last version if I can but is anyone else having this issue? I'm getting a "Vegas Pro has stopped working" message upon Vegas startup.

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).

jimingo-1 wrote on 3/18/2026, 12:09 PM

Well another update and from Intel today and now Vegas 22 does not work again. The first time this happened, the fix was simple...I just took Howard's advice and reinstalled the C++ redistributables but that doesn't work this time. I also tried uninstalling/reinstalling Vegas 22 and I still get the error upon startup. Vegas 23 does work, but 22 does not.

Howard-Vigorita wrote on 3/18/2026, 1:32 PM

Got a similar situation when I just updated the driver of my Intel Ultra's igpu from 101.8509 to 101.8626. Vp22 crashed on startup but vp23 b356 was fine starting up and rendering qsv. Repairing c++ redistributables did not help vp22. My Ultra hdmi is internally wired to it's on-board 5080 so I was able to disable the driver for the Intel igpu, after which vp22 started up fine. Rolled back the Intel driver to 101.8509 and everything works again as before.

Looks like both Intel and Nvidia are now burning bridges to existing software. As the biblical might say, "A pox on all their houses."

RogerS wrote on 3/18/2026, 5:50 PM

Do report driver issues to Intel so they can fix it.

ac6000cw wrote on 3/23/2026, 4:00 AM

I've just had VP22 crash on startup after updating my Intel (13th gen 'Raptor Lake') UHD Graphics drivers from 32.0.101.7084 to 32.0.101.7085 (dated 2026-03-03).

Installing the latest x32 and x64 MS C++ redistributables (and rebooting) as Howard-Vigorita suggested fixed it for me.

This feels like Intel's latest GPU driver updates are updating the C++ redistributables to a version that can break VP22/VP23, but MS has fixed the issue in the latest version of those redistributables.

Howard-Vigorita wrote on 3/23/2026, 10:51 AM

I upgraded from 101.7085 to 101.7086 a few days ago on my 12900h laptop without having to fix redistributables again.

Joshua-Voights wrote on 3/25/2026, 7:55 AM

if you haven't already, I suggest reporting the Vegas Pro crashes at https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT for the Intel driver crashes, this will help Intel fix the bug on their end, since it crashes with newer drivers for Intel

IAM4UK wrote on 3/25/2026, 5:20 PM

The solutions in this thread have not worked for my VP22 installation on Windows 11 Pro with Intel GPU. Any other suggestions?

jimingo-1 wrote on 3/25/2026, 5:24 PM

To get mine to work again, I had to reinstall the C++ Redistributables and roll back the Intel GPU driver.

diverG wrote on 3/29/2026, 7:00 AM

Interesting> Just found the problem with V22 on an i9 286k based machine. Found this thread and followed the guidance. Rolled back the driver and the C++ redistributables. Thanks for guidance.

Out of interest I have an older machine based on on an i7 8086 chip running Vegas18 with no problems. Dropped in V22 and as expected Vegas ran perfectly. Looks like a problem with newer pcs.

Once again thanks. G

Sys 1 Gig Z-890-UD, i9 285K @ 3.7 Ghz 64gb ram, 250gb SSD system, Plus 2x2Tb m2,  GTX 4060 ti, BMIP4k video out. Vegas 19 & V22(250), Edius 8.3WG and DVResolve 20.2 Studio. Win 11 Pro. Latest graphic drivers.

Sys 2 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP19, Plus Edius 8WG Win 10 Pro (22H2) Resolve18

 

Howard-Vigorita wrote on 3/29/2026, 12:27 PM

Looks like Intel might have picked up on the problem with 101.8626 at least on my Ultra system... the 101.8509 driver now shows as "Up To Date" when I do an update check. I see there's also a recent 101.8515 pro update for Arcs & Ultras available for download but update check is not suggesting it and I'm not feeling adventuresome enough to try it yet.