Enable MSI logging

kisspng-installation-computer-icons-computer-software-inst-setup-5b20bc73f07eb6.6739851615288720519851

 

Haven’t used this in a while, but i’ve stumbled across an exe installer that requires reboot, and after reboot it continues the installation of some user MSI. However, during reboot the MSI installation would fail. The MSI was afterwards deleted.

So how can i make a log to see what happend?

Microsoft offers a policy that forces every Windows Installer to make a log. Just add this reg file:

 

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmupx"

 

What does voicewarmupx actually mean? As Microsoft states:

  • v: Enable verbose output
  • o: Log out-of-disk-space messages
  • i: Log status messages
  • c: Log initial UI parameters
  • e: Log all error messages
  • w: Log non-fatal warnings
  • a: Log start up of actions
  • r: Log action-specific records
  • m: Log out-of-memory or fatal exit information
  • u: Log user requests
  • p: Log terminal properties
  • +: Append logged data to existing file
  • !: Flush each line to the log
  • x: Include extra debugging information in the logs

 

Now, Windows will monitor each MSI installation and output a log in C:\Users\USERNAME\AppData\Local\temp.

The names of the logs are random, but each starts with msi, for example MSI_12343.log

I would not recommend to leave this setting on.

Sharing is caring!

Leave a comment

Your email address will not be published. Required fields are marked *

sixteen − 1 =