The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →To enable Windows Installer logging in Windows 10, either turn on the machine-wide Logging policy with Registry Editor or Group Policy, or log one installation directly with msiexec.exe. Use policy logging for repeated troubleshooting, and the command-line method when you need a single, easy-to-find log. Disable policy logging when finished because persistent logging can reduce performance, consume disk space, and expose sensitive data.
Choose the right logging method
| Method | Scope | Typical log location | Best use |
|---|---|---|---|
| Registry policy | Windows Installer operations covered by the machine policy | Randomly named MSI*.LOG files in %temp% |
When Group Policy is unavailable or you need a direct local setting |
| Group Policy | Windows Installer operations covered by the computer policy | Msi.log in the Temp directory of the system volume |
Managed PCs and domains where policy administration is appropriate |
msiexec.exe /L |
One install, repair, or uninstall command | The exact path supplied in the command | A targeted diagnostic run with predictable output |
Policy logging is not a substitute for command-line logging in every situation. A command or program that explicitly enables its own logging can take precedence over the policy setting, and Group Policy options depend on the Windows edition and management environment.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Windows 10 For Dummies (For Dummies (Computer/Tech)) | $13.31 | Buy on Amazon |
| 2 |
|
Teach Yourself VISUALLY Windows 10 | $29.57 | Buy on Amazon |
| 3 |
|
Windows 10 For Seniors For Dummies (For Dummies (Computer/Tech)) | $12.95 | Buy on Amazon |
| 4 |
|
Windows 10 Made Easy: Take Control of Your PC | $15.99 | Buy on Amazon |
| 5 |
|
Windows 10 Inside Out | $32.99 | Buy on Amazon |
Enable logging with Registry Editor
Microsoft’s manual procedure stores the setting as a machine policy. You need administrator rights, and registry edits should be preceded by a registry backup. An incorrect change can cause serious Windows problems.
- Press Windows key + R, type
regedit, and press Enter. Approve the User Account Control prompt. - Navigate to
HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftWindowsInstaller. Create theInstallerkey if it does not exist. - In the right pane, create a new String Value (REG_SZ) named
Logging. - Open
Loggingand set its value data tovoicewarmup. - Close Registry Editor, then reproduce the installation or uninstallation problem.
The letters in voicewarmup select event categories. Microsoft permits the letters in any order. They represent verbose output, out-of-disk-space messages, status, initial user-interface parameters, errors, non-fatal warnings, action starts, action records, memory or fatal-exit information, user requests, and terminal properties.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
What does the asterisk setting mean?
In installer logging options, * requests all standard event categories except verbose (v) and extra debugging (x) output. If you specifically need verbose output, use the command-line form /L*V described below.
Enable logging through Group Policy
Use this route on editions and managed environments that expose the Windows Installer policy. The available policy interface can vary, so confirm that the setting exists on the target Windows 10 device.
Rank #2
- Open Local Group Policy Editor by pressing Windows key + R, entering
gpedit.msc, and pressing Enter, or open the applicable domain policy in your management console. - Go to Computer Configuration > Administrative Templates > Windows Components > Windows Installer.
- Open the Logging policy (also referred to as the MSILogging policy).
- Select Enabled, enter the required logging letters, select Apply, and then select OK.
- Repeat the failing install or uninstall.
The policy documentation identifies Msi.log in the Temp directory on the system volume as the output location. On a managed computer, policy refresh timing and domain policy precedence can affect when the setting takes effect.
Log one operation to an explicit file
For a single MSI installation, run an elevated Command Prompt and use:
msiexec.exe /i "C:example.msi" /L*V "C:package.log"/i installs the package, while /L*V requests the wildcard event set plus verbose output. Replace both paths with locations appropriate for your system. The command writes the log to the exact file path supplied, making it easier to attach to a support case.
Uninstall with logging
Use /x for an uninstall and retain the same logging switch:
msiexec.exe /x "C:example.msi" /L*V "C:uninstall.log"Other /L letters control status, warnings, errors, actions, user requests, user-interface parameters, memory or fatal exits, disk-space messages, properties, verbose output, extra debugging, appending, and flushing each line. Use only the detail level needed for the diagnosis; extra debugging can increase the amount of sensitive information written.
Find the Windows Installer log
Registry-policy logging
Open File Explorer, enter %temp% in the address bar, and look for a randomly named file beginning with Msi and ending in .log (for example, an MSI*.LOG file). Sort by Date modified and reproduce the failure immediately before checking the folder.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
Group Policy logging
Look for Msi.log in the Temp directory of the system volume. If more than one user or system context is involved, verify which account and system volume performed the operation.
Command-line logging
Open the exact path specified after /L*V. If the file is missing, check that the destination directory already exists, that the command prompt was elevated when required, and that the package path and quoting are correct.
Disable persistent logging after troubleshooting
- Open Registry Editor and return to
HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftWindowsInstaller. - Delete the
Loggingvalue, or remove the policy through Group Policy if that is how it was enabled. - Close the editor and verify that new installer operations no longer create policy logs.
Microsoft advises using this change only for troubleshooting rather than leaving it enabled: persistent logging can adversely affect system performance and disk space. Log files may contain confidential information, including passwords. Store them securely, redact sensitive content where possible, and share them only with trusted support personnel.
Quick Recap
Troubleshooting checklist
- No log appears: confirm the operation actually uses Windows Installer (MSI), verify the policy path and value name, and check the correct Temp directory or explicit command-line path.
- The log is too small: use
/L*Vfor a one-time verbose capture rather than relying on*alone. - Too many logs are created: remove the policy value after the reproduction and keep only the relevant file.
- Access is denied: use an administrator account for Registry Editor, Group Policy changes, and operations that require elevation.
- Logs contain secrets: treat them as sensitive diagnostic material and avoid posting the raw file publicly.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
