

Now try to install Microsoft Office 2016 to get the error message so that the log files get created.įollow the steps below to access the ‘Temp’ folder. Type reg add HKLMSOFTWARE\Microsoft\ClickToRun\OverRide /v LogLevel /t REG_DWORD /d 3.Note: make sure to turn off verbose logging after you are done.Įnable verbose logging before collecting the log files. Windows installer returns codes during the install which will indicate if a particular function was successful or not. When looking through the MSI logs we will typically want to look for a value 3 entry in the logs. Each time you use the Add/Remove Programs tool in Control Panel, a new Msi*.log file is created. Note This should be used only for troubleshooting purposes and should not be left on because it will have adverse effects on system performance and disk space. To include the v and the x option, specify “/l*vx”.

“*” – Wildcard, log all information except for the v and the x option. The “x” flag is available only on Windows Server 2003 and later operating systems, and on the MSI redistributable version 3.0, and on later versions of the MSI redistributable. M – Out-of-memory or fatal exit information Each letter’s actual function is as follows for MSI version 1.1: Each letter turns on a different logging mode. The letters in the value field can be in any order. HKEY_LOCAL_MACHINE\SoftwarePolicies\Microsoft\WindowsInstaller To enable Windows Installer logging yourself, open the registry with Regedit.exe and create the following path and keys: Note that Path is the full path of your Office source location.


Here’s a shortlist of some useful troubleshooting techniques, divided into two sections according to the two main types of MS Office Installations:Ĭlick-to-Run: Office 365 installed MS Office MS Office MSI Install Troubleshooting
