Cimco Edit 8 not starting due to missing MSVCR100.dll

[[email protected]]

Hi all, I have an issue with my Cimco Edit 8 not starting up. I worked with my IT support twice to try and resolve this. They installed more visual studio files and Microsoft files they even reinstalled Mastercam and all we did was get the error message to change to "The application was unable to start correctly (0xc000007b). Click OK to clost the application" The original error message was "The code execution cannot proceed because MSVCR100.dll was not found. Reinstalling the program may fix this problem."  Please let me know if you have ever encountered something like this or if you know how to fix. I might try to reinstall MCAM again considering the first reinstall was done before some of those visual studio files were installed. 

[JParis]

Seems to me I saw that same error a LONG TIME ago in a galaxy far, far away....

If memory serves me right it has to do with the .net installations....

May need to uninstalled the .netframewrork and reinstall it....but it's been awhile

[[email protected]]

We haven't tried that yet so it's worth a shot, thanks!

[ajmer]

these need to be installed

https://www.microsoft.com/en-us/download/details.aspx?id=26999

 

[Jake L]

I had this problem back in March. I ended up contacting my reseller and this is what the solution ended up being for me.

Go to - Program Files -> Mastercam 2022 -> Mastercam -> common -> Editors -> CIMCOEdit8 -> Sys (I assume this folder is in the same file path for everyone)

In this folder there are some .exe files that need to be run:

vcredist_x86.exe

vcredist2010sp1_x86.exe

vcredist2012_x86.exe

vcredist2013_x86.exe

vcredist2015_x86.exe

If memory serves me right, once these have all been executed, it should be all set. Also, I was told that sometimes the 2015 file will just throw an error. If this happens, that particular file can be ignored. It did not throw an error for me, but it may for others.

Hope this helps!

[[email protected]]

It's finally working, the msvcr100.dll must have been corrupt or incorrect. Our IT guy just renamed my msvcr100.dll to msvcr100.dll.bak and then uploaded his and voila! I'm back comparing files the way I'm accustomed. Thank you all for helping us find the solution as well.