You can enable MSI logging for every installation action that happens on your system.
You may need to create the Installer key.
A. Insert Debug as a REG_DWORD, and set its value to 7.
B. Insert Logging as a REG_SZ, and set its value to voicewarmup.
Once the registry strings above have been created, every time you install, repair, modify, or remove, a log file will be created in the directory identified by your TEMP environment variable.
Creating an MSI Log for one specific installation
Turning on MSI Logging from the command line is a last choice effort.
It is highly preferred to use the registry key above to enable MSI logging because it allows you to use your standard install, uninstall, and repair workflows. The workflow below should only be used in special circumstances, for example, if you are not allowed to update the system registry, or you really only want to create the one MSI log, and you are confident you can reproduce your exact problem on the command line.
You can request a log for one specific installation if you know the specific command-line parameters that are required to reproduce your problem. You must be quite careful because entering wrong parameters (like omitting the ACCEPT_EULA switch required by the Install in Silent Mode process) can cause your command-line installation to fail for reasons unrelated to the problem you are investigating.
Logging the Installation of Product XYZ
msiexec /l*v "C:\1LogInstallation\logs\InstallationXYZ.log" /i "C:\msi\XYZ.MSI ACCEPT_EULA=1"msiexec /l*v "C:\1LogInstallation\logs\InstallationXYZ.log" /i "C:\msi\XYZ.MSI AC-CEPT_EULA=1"
Logging the Patching of a Product that Already Has Been Installed
It is also possible to log the installation of an MSP (a patch or hot-fix).
msiexec /l*v MyProdMSP.log /p MyProduct.msp REINSTALL=ALL REINSTALLMODE=omus /qbb