Install new Nvidia driver and cannot open Vegas 20

CrespoFTW wrote on 7/3/2023, 7:33 AM

I installed Game Drive 536.40 and after capturing some gameplay I went on Vegas Pro 20 and keep getting this error popping up. I reinstalled the old nvidia driver and that doesn't work. I reinstalled Vegas Pro multiple times and keep getting this message.

I purchased Vegas Pro since version 14 and can't open 18-20 but somehow I can open Vegas Effect but not Pro.

Please help, this is driving me nuts

Comments

Dexcon wrote on 7/3/2023, 8:18 AM

The recommended NVIDIA driver for Vegas Pro by many on the forum over many years is the Studio driver, not the Game Ready driver. Give the Studio driver a try but make sure to install it as a clean install.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

andyrpsmith wrote on 7/3/2023, 10:44 AM

As jetdv says try reinstalling Microsoft Visual C++ 2015-2022 Redistributable package, maybe your version of MSVCR110.dll is not the one Vegas needs.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

andyrpsmith wrote on 7/3/2023, 11:13 AM

I am also installing the studio 536.40 to see what happens.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

andyrpsmith wrote on 7/3/2023, 11:19 AM

Yeah, no problem with studio 536.40 and my guess is that the game driver did not cause your issue it is likely to be something else. In the past I have used game drivers with Vegas with no issues, but now use the studio which works fine with all my games.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

CrespoFTW wrote on 7/3/2023, 4:32 PM

https://answers.microsoft.com/en-us/windows/forum/all/the-program-cant-start-because-msvcr110dll-is/f052d325-3af9-4ae5-990b-b080799724db

Thank you! This worked...real question but why did c++ randomly do that I been through multiple drivers with no issues for 6+ years and it just did it.

I'm curious if the drivers was the cause or something else

CrespoFTW wrote on 7/3/2023, 4:33 PM

The recommended NVIDIA driver for Vegas Pro by many on the forum over many years is the Studio driver, not the Game Ready driver. Give the Studio driver a try but make sure to install it as a clean install.

Never had issue with Game Drivers before and I play games on PC then edit

CrespoFTW wrote on 7/3/2023, 4:35 PM

Yeah, no problem with studio 536.40 and my guess is that the game driver did not cause your issue it is likely to be something else. In the past I have used game drivers with Vegas with no issues, but now use the studio which works fine with all my games.

This is what I'm thinking. I haven't installed anything apart from the game driver and a few game updates. Just glad it working again