D
danwalshnitro
Guest
We're running into an issue where quiet install of our product is causing machines to reboot without warning shortly after install. We can reproduce the issue using the following command-line:
msiexec /I installer.msi /qn
The installer log is showing this:
MSI (s) (38:F4) [11:45:04:543]: Verifying accessibility of file: msvcp140.dll
Info 1603. The file C:\Windows\SysWOW64\msvcp140.dll is being held in use. Close that application and retry.
We are attempting to install the 2017 runtime and this issue seems to happen when a user has installed the 2015 runtime and a program is using one of the associated DLLs.
We are using WiX to create our installer and we are using the following merge modules:
We have some 32bit components so we need to ensure that x64 and x86 runtimes are installed.
Is there any way to keep the merge modules from triggering an uninstall without warning? We have a strong preference toward an msi installer so we would like to avoid creating an exe installer bundle that chains the runtime exe installs and our own installer if at all possible.
Continue reading...
msiexec /I installer.msi /qn
The installer log is showing this:
MSI (s) (38:F4) [11:45:04:543]: Verifying accessibility of file: msvcp140.dll
Info 1603. The file C:\Windows\SysWOW64\msvcp140.dll is being held in use. Close that application and retry.
We are attempting to install the 2017 runtime and this issue seems to happen when a user has installed the 2015 runtime and a program is using one of the associated DLLs.
We are using WiX to create our installer and we are using the following merge modules:
- Microsoft_VC141_CRT_x64.msm
- Microsoft_VC141_MFC_x64.msm
- Microsoft_VC141_OpenMP_x64.msm
- Microsoft_VC141_CRT_x86.msm
- Microsoft_VC141_MFC_x86.msm
- Microsoft_VC141_OpenMP_x86.msm
We have some 32bit components so we need to ensure that x64 and x86 runtimes are installed.
Is there any way to keep the merge modules from triggering an uninstall without warning? We have a strong preference toward an msi installer so we would like to avoid creating an exe installer bundle that chains the runtime exe installs and our own installer if at all possible.
Continue reading...