none
How to avoid restart when installing with MSVC merge modules? RRS feed

  • Question

  • 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:

    • 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.


    Friday, August 16, 2019 9:41 AM

All replies

  • Hi danwalshnitro,

    Thank you for posting here.

    According to your description, we recommend you could try to close the process of msvcp140.dll manually before installing.

    If you do not know which process is using a DLL file, you could try to use this command: tasklist /m msvcp140.dll to check which process is using msvcp140.dll. Please follow the steps below to close the process of msvcp140.dll manually.

    1. Use Win+R -> type cmd to call command prompt.

    2. Type command: tasklist /m msvcp140.dll and the processes that use the dll modules will be listed.

    3. Try to close the application that uses the dll modules and then install your product.

    Hope this could help you.

    Best Regards,

    Dylan


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Monday, August 19, 2019 9:45 AM