VCRuntime error

Hey there. I am a huge fan of all my Blackmagic tools, (ATEM MiniPRo, HDR monitor etc.) Today i tried to add DaVinci Resolve to my portfolio and it broke a bunch of stuff on my rig. I now get a VCRuntime error that will not allow me to run any of the Blackmagic software. Any ideas?

[Peter Chamberlain]

Are you on W10?
Is it Resolve 17.0 or some other specific version you installed?
can you detail your system?
please see the faqs above and submit a link with your NFO and logs

OK, so i think i have traced it and have restored my switcher and all other elements. THe issue i beleive is that version 17 of resolve wants to install an older version of C++ the installer is carrying three older versions. When i install, it looks like the the older versions are conflicting with the newer version that is installed in the OS C++2015-2019. Does that resonate? NOTE: here are the system specs: Surface Studio Intel i7-7820HQ 2.90GHz 32.GB Ram x64

Add me to the VCRUNTIME140_1.dll list and it broke far more than just BMD code.

Just received Resolve 17 Studio (GA) today and installed it over my 17 Beta 8a and it trashed everything. Attempting to start Studio resulted in countless error dialogs stating:
"The code execution cannot proceed because VCRUNTIME 140_1.dll was not found. Reinstalling the program may fix this problem"

Reinstalling Resolve did nothing to remedy the issue.
It threw the error on boot when lots of apps that start in the background attempt to start, as well as when I attempted to start FireFox and other apps that don't auto-start. (Native Instruments, Adobe, etc. for instance).

Did BMD attempt to replace a DLL or C code runtime library in Windows' primary folder(s)?
And if so, WHY would they delete this DLL from a system folder?! This is totally bizarre and mind numbingly frustrating.

I found a copy of the VCRUNTIME140_1.DLL in
C:\Program Files\Common Files\microsoft shared\ClickToRun and copied it to C:\Windows\System and everything seems to have returned to normal.

This is a gross oversight/bug. I can see installing the library in a predictable location so you know it's there but removing it from a Windows system path?? C'mon folks...

If you get this error, do a search on your C: drive for the VCRUNTIME140_1.dll file (if you search for just 140, you'll find lots of instances most likely but apparently you need the "_1" version of the runtime library) and copy into C:Windows\System and you should be good to go.
I think... At least it seems to have worked for me. Time will tell, I reckon.

Saw this somewhere else too in relation to one beta version. Solution (if you can’t find the library from own computer somewhere else) was to install Microsoft Visual C++ 2015 Redistributables, which can be found from Microsoft downloads.

I had this issue too when I installed Resolve 17 Studio.
Resolve couldn't start and for example Firefox (the latest version) didn't start either.

Issue was fixed by the repair function of Microsoft Visual C++ 2015-2019 Redistributable (x86).
This can be found (in Windows 10) in Programs and features.

E D I T

This also happened with my laptop.
The fix was as easy as it was with desktop.
No biggie.

Add me to the VCRUNTIME140_1.dll list and it broke far more than just BMD code.


If you get this error, do a search on your C: drive for the VCRUNTIME140_1.dll file (if you search for just 140, you'll find lots of instances most likely but apparently you need the "_1" version of the runtime library) and copy into C:Windows\System and you should be good to go.
I think... At least it seems to have worked for me. Time will tell, I reckon.

I had this same issue when I installed 17 today. I copied the .dll file into the System folder as described above. Problem solved. Thank you for the tip!

Can anyone confirm if it's currently safe to install Davinci Resolve 17 on Windows 8.1? I already seem to have Visual C++ 2013 and 2015-2019 redistributables installed on my system, but the installer won't let you uncheck the boxes. If I let attempt to install these things again, will it cause trouble? Thanks!