The following may help. I spotted it in a web manual I'm reading:
You can enable 'verbose' MSI logging. This can be enabled on the client by creating the following Registry value:
Key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
REG_SZ: Logging
Value: voicewarmup
This will create log files in the %temp% folder (\Windows\Temp for standard Group Policy MSI deployment. The users’ own temporary folder for manual MSI deployment). This following document explains this in detail:
How to enable Windows Installer logging
After this setting has been enabled, reboot the PC, and allow Windows to attempt to MSI installation again. When this process has completed (or nothing has happened) log into the machine and check the log files created in the \Windows\Temp folder.
If this technique does not reveal the cause of the problem it may also be useful to enable ‘verbose’ logging for the Windows Group Policy engine. Please remember that this is an advanced technique and it may take some time to decipher the log files. You can enable this logging by creating the following registry value. It may also be necessary to create the Diagnostics key if one is not already present.
Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics
REG_DWORD: AppMgmtDebugLevel
Value: 0x4b
After this setting has been enabled, reboot the PC, and repeat the installation process described above. The Group Policy engine will create a file called Appmgmt.log in the C:\Windows\Debug\Usermode folder. This is further explained here:
Troubleshooting Program Deployment By Using Verbose Logging
NB: You may also need to create the Usermode folder if it does not already exist.
