Skip to content

WINDOWS INSTALLER ERROR · ERROR_INSTALL_LOG_FAILURE

Error 1622: Error Opening Installation Log File

The setup asked Windows Installer to write a log, and the log file could not be opened. Microsoft's text points at the log's location, not at the program you were installing or removing.

WHAT WINDOWS SAYS

There was an error opening installation log file. Verify that the specified log file location exists and is writable.

Wording from Microsoft's documentation, linked under Sources.

TECHNICAL SUMMARY

Number1622
Windows nameERROR_INSTALL_LOG_FAILURE
Where it appearsExit code of msiexec.exe
In PC Tweaker UninstallerShows the exit code

What causes Error 1622

  • A log path was passed on the command line (Microsoft documents the /L options for this) and that folder does not exist or cannot be written to.
  • Windows Installer logging is turned on by policy. Microsoft documents a Logging value under HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer that makes Windows Installer post a log named Msi*.log to the Temp folder.

How to fix Error 1622, safest step first

Microsoft's message names the check: the log file location must exist and be writable. In order, with the read-only step first:

  1. See where the log is meant to go

    If the error came from a command, look at the path after /L. If it came from a normal setup, run the two checks below: they show whether the logging policy is on and whether your Temp folder exists.

    To undo: Nothing to undo: you only looked.

  2. Give the log a folder that exists

    For a command, point the log at a folder you can write to, for example msiexec.exe /i "C:\example.msi" /L*V "%TEMP%\install.log". If the Temp folder itself is missing, create it again at the path the check printed.

    To undo: Delete the log file, or the folder you created, when you no longer need it.

  3. Turn the logging policy off if nobody needs it

    Microsoft says this logging should be used only for troubleshooting and should not be left on, because it affects performance and disk space, and that removing the Logging value disables it. Export the key first, then delete the Logging value in Registry Editor. On a work PC the value may come from Group Policy: ask the administrator.

    To undo: Double-click the .reg file you exported to put the value back. Microsoft's article gives the value's data, voicewarmupx, if you need to recreate it by hand.

Check it yourself, without changing anything

  1. See whether the logging policy is on (Command Prompt)

    An error saying the key or value was not found means the policy is not set. Nothing is changed.

    reg query "HKLM\Software\Policies\Microsoft\Windows\Installer" /v Logging
    cmd

  2. Check that your Temp folder exists (PowerShell)

    It prints the folder and True or False. Nothing is changed.

    $env:TEMP; Test-Path $env:TEMP
    PowerShell

What PC Tweaker Uninstaller does with Error 1622

Shows the exit code

PC Tweaker Uninstaller removes a Windows Installer program with the command it shows you first in the Removal Brief, msiexec.exe /x {ProductCode} /qn /norestart, after asking Windows for a restore point when the removal needs administrator rights. That command contains no log option, so the Uninstaller never asks Windows Installer for a log file itself. If msiexec.exe returns 1622 during one of its removals, the report shows that exit code; the Uninstaller does not change the logging policy or the Temp folder.

PC Tweaker Uninstaller: see the exact command before a removal runs

Common questions

Did anything get installed when error 1622 appeared?

Microsoft's text describes a failure to open the log file. Check Settings > Apps > Installed apps to confirm the program's state on your PC.

Where does Windows Installer write its logs?

Where the command says after /L, or, with the logging policy on, in the Temp folder with a random name that starts with Msi and ends in .log. Microsoft's logging article describes both.

Is it safe to remove the Logging value?

Microsoft says the value should be used only for troubleshooting and should not be left on, and that removing it disables the logging. Export the key first so you can put it back.