Fix Windows Installer MSI Errors with msiexec Logs and Service Reset in Windows 10/11

Fix Windows Installer MSI Errors with msiexec Logs and Service Reset in Windows 10/11​

Difficulty: Intermediate | Time Required: 20 minutes
MSI installation errors can be frustrating because the message on screen is often too vague: “fatal error,” “another installation is already in progress,” or “Windows Installer service could not be accessed.” The good news is that Windows includes a built-in command-line tool, msiexec.exe, that can create detailed installation logs. Combined with a quick reset of the Windows Installer service, you can often identify the real cause and get the installer working again.
This guide applies to Windows 11 and Windows 10. The steps are the same on both versions, although Windows 11 commonly uses Windows Terminal (Admin) while Windows 10 may show Command Prompt (Admin) or Windows PowerShell (Admin).

Prerequisites​

Before you begin:

1. Sign in with an administrator account.
2. Make sure you have the original .msi installer file.
3. Close open installers, setup windows, software update tools, and app stores.
4. Save your work in case a restart is required.
5. If you are on a work or school PC, check whether your organization manages software installation through Group Policy, Intune, Configuration Manager, or another deployment tool.

Note: Windows Installer packages usually end in .msi, while patch packages often end in .msp. This guide focuses mainly on .msi installers, but several logging concepts also apply to .msp packages.

Step 1: Confirm the MSI file location​

1. Open File Explorer.
2. Locate the MSI file you are trying to install.
3. Right-click the file and select Properties.
4. On the General tab, confirm the file path and filename.

For this tutorial, the example MSI will be:
C:\Installers\ExampleApp.msi
If your MSI is in Downloads, Desktop, or another folder, replace the example path with your real one.

Tip: Avoid running installers directly from compressed ZIP files, network locations, or cloud-sync folders while troubleshooting. Copy the MSI to a simple local folder such as C:\Installers first.

Step 2: Create a folder for MSI logs​

1. Open File Explorer.
2. Create a folder named:

C:\MSILogs

1. Make sure your account can write files to that folder.

This keeps your troubleshooting logs easy to find instead of mixing them into the Temp folder.

Step 3: Open an elevated command window​

1. Right-click Start.
2. Select Terminal (Admin), Windows PowerShell (Admin), or Command Prompt (Admin).
3. Approve the User Account Control prompt.

You must use an elevated window because many MSI packages install files, services, drivers, or registry entries that require administrator rights.

Step 4: Run the MSI with verbose logging​

In the elevated command window, run this command, adjusting the MSI path and log filename as needed:
msiexec.exe /i "C:\Installers\ExampleApp.msi" /L*V "C:\MSILogs\ExampleApp-install.log"
What this does:

1. /i starts a normal installation.
2. /L*V enables detailed logging, including verbose output.
3. The final path tells Windows where to save the log file.

If the installer fails again, do not immediately delete or rerun anything. The log file is the evidence you need.

Warning: MSI logs may contain usernames, folder paths, product keys, server names, license data, or other sensitive details. Review and redact the log before posting it publicly on a forum.

Step 5: Read the MSI log correctly​

1. Open the log file in Notepad.
2. Press Ctrl + F.
3. Search for:

Return value 3
This is one of the most useful markers in MSI troubleshooting. It often appears near the action that failed.

1. After finding Return value 3, scroll upward 20–50 lines and look for:
   • A failed custom action
   • Access denied messages
   • Missing files or folders
   • Failed service creation
   • Registry permission errors
   • A pending reboot message
   • A prerequisite check failure

Also search for these common phrases:

Error
Failed
Access is denied
Another installation is already in progress
1603
1618
1719
1722

Common examples:

1. 1603 usually means a fatal installation error, but the log is needed to find the specific cause.
2. 1618 means another Windows Installer transaction is already running.
3. 1719 can indicate the Windows Installer service is unavailable or not working correctly.
4. 1722 often points to a custom action failure inside the MSI.

Tip: The first error is usually more useful than the final error. Installers often report a generic failure at the end after the real problem happened earlier.

Step 6: Check whether another installer is running​

If you see error 1618 or messages about another installation in progress:

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Select Processes.
3. Look for:
   • msiexec.exe
   • Setup programs
   • Software update tools
   • App installers

If you recently installed or updated software, restart Windows instead of force-ending processes. A reboot is safer and clears pending installer operations.
After restarting, try the logged install command again.

Step 7: Reset the Windows Installer service​

The Windows Installer service name is msiserver. Its normal startup type is Manual, and it should not be disabled because it is responsible for adding, modifying, and removing MSI/MSP-based applications.

1. Open Terminal (Admin), PowerShell (Admin), or Command Prompt (Admin).
2. Check the service status:

sc query msiserver

1. Stop the service if it is running:

net stop msiserver
If Windows says the service is not started, that is okay.

1. Reset the startup type to Manual:

sc config msiserver start= demand

Important: The space after start= is required. Without it, the command may fail.

1. Start the service:

net start msiserver

1. If the service starts successfully, rerun your MSI command with logging:

msiexec.exe /i "C:\Installers\ExampleApp.msi" /L*V "C:\MSILogs\ExampleApp-install-after-reset.log"

Step 8: Re-register Windows Installer if service reset is not enough​

If the service still behaves oddly, you can re-register Windows Installer from an elevated command window:

msiexec.exe /unregister
msiexec.exe /regserver

These commands usually do not display much output. After running them, restart Windows and test the installer again with a fresh log.

Note: Re-registering Windows Installer is a troubleshooting step, not routine maintenance. Use it only when the service appears broken or MSI installs consistently fail.

Step 9: Try a repair or uninstall log if needed​

If the application is already installed but broken, create a repair log:
msiexec.exe /fomus "C:\Installers\ExampleApp.msi" /L*V "C:\MSILogs\ExampleApp-repair.log"
If uninstall is failing, create an uninstall log:
msiexec.exe /x "C:\Installers\ExampleApp.msi" /L*V "C:\MSILogs\ExampleApp-uninstall.log"
If you have a product code instead of the MSI file, you may be able to uninstall using the product GUID:
msiexec.exe /x {PRODUCT-CODE-GUID} /L*V "C:\MSILogs\ExampleApp-uninstall.log"

Tips and troubleshooting notes​

• Restart before deep troubleshooting. Pending reboots are a common cause of installer failures.
• Run locally. Copy the MSI to a local folder before installing.
• Check permissions. If the log mentions access denied, test with an administrator account and confirm the target folder is writable.
• Temporarily avoid silent mode. Do not use /quiet while troubleshooting unless required. A visible installer may show useful prompts.
• Do not leave global MSI logging enabled. Registry-based Windows Installer logging is useful for advanced troubleshooting, but it can create many logs and consume disk space if left enabled.
• Look for prerequisites. Some MSI packages fail because a required runtime, framework, driver, or older version is missing.
• Be careful with cleanup tools. Avoid “registry cleaner” style fixes. They can remove installer registration data and make MSI problems worse.

Conclusion​

Using msiexec verbose logs turns a vague MSI failure into useful troubleshooting data. Resetting the Windows Installer service can also fix cases where installations fail because the service is stopped, disabled, stuck, or incorrectly configured. With a clean local installer, a detailed log, and a properly configured msiserver service, you have a much better chance of identifying whether the problem is permissions, prerequisites, a pending reboot, another installer, or a broken package.
Key Takeaways:

• Use /L*V with msiexec.exe to create detailed MSI logs.
• Search logs for Return value 3, error codes, and the first meaningful failure.
• Reset the Windows Installer service to Manual startup with sc config msiserver start= demand.
• Restart Windows when another install is pending or error 1618 appears.
• Treat MSI logs as sensitive before sharing them on WindowsForum.com.

---

This tutorial was generated to help WindowsForum.com users get the most out of their Windows experience.