共用方式為


Possible workaround for MSI uninstall failures caused by an error opening the installation log file

Recently, I was investigating a strange uninstall issue on a co-worker’s computer.  They tried to uninstall a build of an MSI-based product we are working on by using the entry in the Programs and Features control panel.  When doing so, an error dialog with the following text appeared almost immediately:

Error opening installation log file. Verify that the specified location exists and is writable.

Further investigation showed the following additional data:

  • Manually uninstalling the MSI manually by using msiexec.exe succeeded
  • Attempting to use the Programs and Features control panel to uninstall any other MSI that was installed on the computer failed with the same error message, so we knew that the problem was not specific to our installer.

After a bit of investigation, I found the knowledge base article at https://support.microsoft.com/kb/2564571.  That article lists a simple workaround for this error – stop and restart the process named explorer.exe using Task Manager.  We tried it out, and it ended up working.  Hopefully this will be useful in case others run into this error message in the future.

Comments

  • Anonymous
    May 25, 2013
    Thanks!

  • Anonymous
    July 14, 2013
    You rule man!

  • Anonymous
    October 16, 2013
    IT does not work for me. I have tried the same solution. The error still exist. Please Help !

  • Anonymous
    October 16, 2013
    Hi Yanamuse - You might need to restart the computer to resolve this error.  I've seen a couple of cases in the past where restarting Windows Explorer wasn't enough.

  • Anonymous
    December 03, 2013
    This did not work for me either and I have done a complete reboot of the server.

  • Anonymous
    December 03, 2013
    Hi Karyn - Can you uninstall the .msi directly instead of using the control panel as a workaround?

  • Anonymous
    April 14, 2015
    I am getting the error only after installer a particular msp on existing msi. Restarting the explorer or machine solves the problem temporarily. After installing the patch file again same problem occurs.