MSVCP140_1.dll not found

[Giterdun]

Hey guys,
I just downloaded the FreeCAD_0.19.24047_Win-LPv12.4.3_vc17.x-x86-64.7z from the link here here and unzipped the file to my desktop. When I try to run the FreeCAD.exe in the bin folder, I get an error. (see pic) Before I downloaded, I thought it was an exe installation file, but it is the installed folder structure. I know that during a normal install, some files are copied to various folders and there's registry updates etc.. But can someone please enlighten me on how I'm supposed to install it? This is on a new install of Windows 64-bit. Do I need install the .18.4 windows version first from that package and then just overwrite it with these new .19 files?? Please forgive my ignorance, but I'm fairly new to using FreeCAD and any assistance is much appreciated. Thank you.

[chrisb]

I have split this from the post about the AddonManager.

Normally it is sufficient to unzip the archive and then run FreeCAD.exe from the bin folder. There is no further installation needed.

[Giterdun]

Ok.. no problem.. I wasn't sure where my post went, but I just found it, so I wanted to post some feedback, as I got it to work.

I originally downloaded the FreeCAD_0.19.24047_Win-LPv12.4.3_vc17.x-x86-64.7z, as it seemed it had the higher version #.. but it gave this error when I tried to run FreeCAD.exe. I got that error every time when I tried to run this file. Then I decided to download the Conda version, FreeCAD_0.19.24012-Win-Conda_vc14.x-x86_64, which I also unzipped to a folder on the desktop. This version started up with no issue, which was great, but I wanted to know why the other version didn't work, so I had a look for the missing file MSVCP140_1.dll in the Conda version and found it in the \bin folder. There was also a MSVCP140.dll file and a MSVCP140_2.dll file. Then I searched the Win-LP version folders for these 3 files, and only the MSVCP140.dll was found, but it was in the \bin folder and also in the \bin\Libs\site-packages\scipy\.libs folder. These files had different dates and sizes.. The other 2 files were not found. So then I copied the 2 files (MSVCP140_1.dll and MSVCP140_2.dll) from the Conda package and put them into the \bin\Libs\site-packages\scipy\.libs folder of the Win-LP version and tried starting it again, but it still gave that same error. So I then moved those 2 files to the \bin folder of the Win-LP version, and then FreeCAD started up just fine.. Of course, I don't know if they are the correct files or even what they do, but obviously it's something that needs to be fixed properly. I also don't know if something will crash whenever the program needs to use those files..

[chrisb]

Thanks for the analysis. It may help the packagers.

pinged by pinger macro

[sgrogan]

Of course, I don't know if they are the correct files or even what they do, but obviously it's something that needs to be fixed properly. I also don't know if something will crash whenever the program needs to use those files..

Thanks for the analysis. It may help the packagers.

Thanks for the heads up should be fixed now
https://github.com/FreeCAD/FreeCAD/rele ... g/0.19_pre

[Giterdun]

No problem guys. I will download it and test the install again later on today. If you need any testing or whatever on Windows 10 64-bit, I can do that no problem. One small issue I came across is that when I open the FreeCAD files I created and saved in the older version (.18), and then save and close them again, they then show up in Recent files, but now they just have a generic blank icon, instead the the normal FreeCAD icon. Not sure if that is related to the files. I can post a pic later if needed..

[chrisb]

One small issue I came across is that when I open the FreeCAD files I created and saved in the older version (.18), and then save and close them again, they then show up in Recent files, but now they just have a generic blank icon, instead the the normal FreeCAD icon. Not sure if that is related to the files. I can post a pic later if needed..

I don't know how smart Windows is. Perhaps it realizes, that you edited with a non-installed program.

[sully9]

Thanks for the heads up should be fixed now
https://github.com/FreeCAD/FreeCAD/rele ... g/0.19_pre

Not sure if it will take some time for the fix to make it through to the 0.19_pre releases, but I just downloaded "0.19.24267-Win-LP" and it still generates the error about missing MSVCP140_1.DLL.

Cheers!

[GeneFC]

I just downloaded "0.19.24267-Win-LP" and it still generates the error about missing MSVCP140_1.DLL.

I am not sure just what you downloaded, but I have all three versions of 0.19.24267 for Windows, and each of them includes the MSVCP140_1.DLL file.

I also have that file in my Windows\System32 folder. It is a standard Windows file.

Gene

[sully9]

It's kinda moot now. At the time I just sync'd DLLs to get things going and all of the builds I've grabbed dated after 3/5 had resolved this. I'm guessing it took some time for the packaging to catch up. Maybe I just had bad timing. But...

I am not sure just what you downloaded, , but I have all three versions of 0.19.24267 for Windows, and each of them includes the MSVCP140_1.DLL file.

I had downloaded the 0.19.24267 LP build from http://github.com/FreeCAD/FreeCAD/relea ... -x86-64.7z
file date = 2/26/2021 2:16:14 PM, size = 272,164,028 bytes, SHA-256 = 9CB78CE88D1F082097D26C7756F9A3D2613AE290097486CEA89DD3963AE82419

I agree the "FreeCAD_0.19.24267-Win-Conda_vc14.x-x86_64.7z" release included the "MSVCP140_1.DLL" file, but the "FreeCAD_0.19.24267_Win-LPv12.5.1_vc17.x-x86-64.7z" included only the "MSVCP140.dll". It similarly lacked all the "MSVCP140_*.DLL" files.

I also have that file in my Windows\System32 folder. It is a standard Windows file.

I think it's more accurate to say it's a standard "Visual C++ Redistributable [2015?]" file. I've got 3 Win 10 x64 systems that are current with updates, only one of them (DELL) has the "MSVCP140_1.DLL" in system32. The other two (one RETAIL, one REFURB) only have MSVCP140.DLL. I only hit this because I needed to test this on a fresh Win 10 install, with current updates and patches.

Again, it looks like whatever was causing the omitted files has since be resolved.

Cheers!