-
Vegas 13 Missing .dll Files
OK, I went to launch my Vegas 13 and got this error message “missing MSVCR110.dll. WTF??? Why does it suddenly not work and how did this .dll go missing? More important, how do I get back to work ASAP?
Sony wants $$ from me just to talk about it. WTF?
Help.
Ken Bennett
Video Adventures
Capturing Your Life’s Adventures! -
6 Replies
-
MSVCR110.dll is a Microsoft C runtime Dll. Vegas is written in .NET which is a form of C. I would make sure your system drive or memory is operating well before blaming the vegas application. You system RAM or Storage could be in error, or something that was uninstalled recently has screwed with the operation of that dll.
I would verify your .NET versions are still loaded and installed versions do not need an update in Windows Update.
If that does not work, verify the file exists in C:\Windows\SysWOW64\MSVCR110.dll
If the file exists, you have executed all the updates and restarted, run SFC /scannow from an admin command prompt. Repair any of the file issues noted in the CBS.log, windows will give a message that it did not find problems if all is well.
Make sure you have a clean system by running Malware bytes and window defender scans.
Run MemTest86 through one pass of 10 tests to verify your memory is good.
Run chkdsk /R from an admin command prompt and set for reboot check, then reboot. Then check event log for issues found from the chkdsk scan.
Then if the app still does not operate, reinstall Vegas 13 B453.
-
Thanks Aaron.
Ken Bennett
Video Adventures
Capturing Your Life’s Adventures! -
Maybe just try uninstalling, rebooting, and reinstalling Vegas Pro 13.0 as a first test. That should re-establish a runtime files that Vegas Pro needs to operate.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
You can do that too.
I always try and figure out why a system file like that would go corrupt, disappear, or not be found before just re-installing. Bad memory blocks in ram can sometimes look like disk failure, disk errors from a failing drive can start making windows files like that not accessible. Malware and virus do their own things. Reinstalling may only temporarily repair a bad situation.
I keep my .NET packages up to date for development and security reasons, that’s why I advocate doing updates on .NET from MS. Consider how many security patches there have been since the 453 installer was released in June.
-
I did and that fixed the problem. Thanks John.
Ken Bennett
Video Adventures
Capturing Your Life’s Adventures! -
[Ken Bennett] “I did and that fixed the problem.”
That’s good to know. if it happens again, then I agree with Aaron that perhaps there is some failing hardware that’s causing software corruption but for now, just enjoy the fact that it works again. 😉
~jr
http://www.johnrofrano.com
http://www.vasst.com
Reply to this Discussion! Login or Sign Up