Note-to-self: enabling Windows Installer verbose logging via registry (while troubleshooting #FIM2010 hotfix installation fail)

Case

Trying to install the latest FIM hotfix (msp-file, 4.1.3496 on a Windows 2008 R2 machine). That installs fails without an error message on screen, and in the eventviewer neither.
When executing the msp file with msiexec, including verbose logging options, also that install fails. (Probably using the wrong parameters for msiexec…)

Goal

I need to quickly find out what’s going wrong on that installation without losing too much time. (Or, to put it differently, getting PEBCAC out of the equation..)

Solution

Check out this article: How to enable Windows Installer logging (http://support.microsoft.com/kb/223300)

It allows you to set the logging level (eg extra verbose logging with vx option) the registry.

Then the log file is (by default) stored in the %TEMP% folder (check it out by running a SET command in a command prompt).

Details

To have us enable or disable Windows Installer logging for you, go to the “Fix it for me” section. If you would rather enable Windows Installer logging yourself, go to the “Let me fix it myself” section.To fix this problem automatically, click the Fix this problem link. Then click Run in the File Download dialog box, and follow the steps in this wizard.

You can fix it with a automated config :
Enable Windows Installer logging Disable Windows Installer logging
    Fix this problem Microsoft Fix it 50380
    Fix this problem Microsoft Fix it 50381
Or you can fix it manually in the registry.
To enable Windows Installer logging yourself, open the registry with Regedit.exe and create the following path and keys:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

Reg_SZ: Logging Value: voicewarmupx (where only vx is used to enable extra verbose logging…)

Find all details in the KB article How to enable Windows Installer logging