Skype MSVCP140.dll missing
Hi,
we were having issues with the latest two Skype builds 7.34 and 7.33 where after deployment the program wouldn't start with the error message mentioned here:
https://community.skype.com/t5/Windows-desktop-client/MSVCP140D-dll-is-missing/td-p/4614575
Funny enough when installing it manually with the Skype web installer the error message did not appear. A rollback to version 7.31 did get it to work with PDQ Deploy, is there any way you could fix this for later versions as well?
Regards, JK
0
Comments
Hi JK,
there is a missing update in your OS: please try to deploy the "Visual Studio C++ 2015 Update 3 (x86)". You can create manually the package in PDQDeploy withe the exe from here:
https://download.microsoft.com/download/6/D/F/6DF3FF94-F7F9-4F0B-838C-A328D1A7D0EE/vc_redist.x86.exe
and with this parameter: "/q /norestart"
BR, Mattia
Hi Mattia!
Thanks for your input! I did think about that, but then I wondered why it did work with the manual installation. Did the Skype web installer install this update for me? If yes, would it be possible to add this as a step for future Skype deployments in PDQ deploy? That would be convenient. :-)
Regards, JK
Yes, I think that Skype install update for you. Im not an AdminArsenal employee so I can't modify their package. I also prefer create a separate package cause maybe this update is mandatory for another application so I prefer deploy it immidiately on all PC. In this order, I have it available for the future :)
The Skype web installer will pull down all the needed dependencies.
If you're doing an autodeployment of the skype package, I'd use a Pre-Step on the auto-deploy package that installs the C++ Runtime. You could check a system that has skype and the runtime and is working and look for a file included with the runtime, and use it as a condition so that the pre-step only runs if that file is missing, which would mean that the package needs installed.
Make sense?
Sure, makes sense, but wouldn't it make more sense if this would be included with the built-in deployment? I can't be the only one having this problem. :-)
I am also experiencing this issue. I submitted a support ticket.
I suppose they *could* do a dependency check. Just adds cruft to the package from the library though.
It would add a little weight to the package, but in this case it's necessary in my opinion. I have been experiencing the issue where the Auto-Update installation broke Skype on several fully patched Windows 7 clients, so Skype-wise PDQ Deploy at this time is non-functional.
Seems they added it now in latest package. Good decision.
Is there any way to view/edit the steps of Auto Deployment schedules? When I try to edit an Auto Deployment it seems that I can only add additional steps but not edit the ones that are already in the package.
I found this in the Package details by the way: "VC++ Runtime 2015 Update 3 (32-bit) will be installed on Windows 7 and 8.x computers. XP, Vista and 10 will not have VC++ installed." I have not noticed it until now. Seems that if the problem remains I will have to roll out VC++ as well (which isn't that much of a problem as there is a package for it already).
You can't edit the steps of an Auto Deployment package directly. The only way you can edit the steps would be to Import the package into your Library, and then edit the steps from there. The downside to that though, is the package is locked to the version of the software when you imported the package, it will no longer be automatically updated. You will at least be able to view the steps and see what they are doing though, and maybe that will give you enough insight into what is going on to build Pre/Post steps around it.
Hope that helps.
The msvcp140.dll is popular file that is used but sometimes this file is shows error to access some task so you need to download missing msvcp140.dll file easily and then after that you can access the file you want.