Automatic account creation is now enabled. Captcha authentication required for account creation and editing unless you are trusted here.

From WiX Wiki at MindCapers

Verbose Logs

Though most of us run .msi files via the double-click-on-the-file method, these files actually launch with msiexec. When perplexed by a problem, it is sometimes helpful to run your .msi with a verbose log. To do this, run msiexec explicitly from the command line with logging options:

    <msifilename>.msi /l*vx <path to a text log file> 

or

    msiexec /i <path to msi> /l*vx <path to a text log file> 

Logging on uninstall

In the event that you get an error upon uninstall, if you have the original .msi file you can log with the uninstall flag:

    msiexec /uninstall <path to msi> /l*vx <path to a text log file> 

Fixing a broken uninstall

1. Build a fixed MSI.
2. Recache/reinstall the fixed MSI over top the busted installed MSI: msiexec /fv your.msi 3. Repeat 1 & 2 until MSI is fixed enough to happily uninstall. <smile/>

MSI Error Codes

MSI Error Codes

GUIDs vs. Compressed GUIDs

The log files generated by msiexec.exe show compressed GUIDs rather than the GUIDs used in your .wxs files. This link has information about converting these compressed GUIDs to something you can search for in your .wxs sources.