Get it from the official source
We don't host files. These links take you straight to the genuine, safe installer on the developer's website.
Error 1603 is the Windows Installer's blanket way of saying "a fatal error occurred during installation" without telling you which one. It's a generic MSI failure code, so it appears for many different apps, from Java and .NET to enterprise software and games. The message looks alarming, but it's rarely fatal in any real sense; it just means the MSI couldn't complete one of its actions and rolled back.
The realistic causes are a manageable set: insufficient permissions, a half-removed previous version, a full or low-space drive, the Windows Installer service misbehaving, or a folder the installer is trying to write to that already exists with the wrong permissions. Microsoft even documents that 1603 frequently occurs when the installer attempts to install to a directory that's encrypted or that the SYSTEM account can't access.
Because 1603 is generic, the most powerful troubleshooting move is to read the installer's verbose log, which names the exact action that failed. This guide shows you how to generate that log and walks through the fixes that resolve the overwhelming majority of 1603 errors. Start with an official copy of the installer, since a corrupt download produces confusing 1603 failures too.
Helpful tools
Program Install and Uninstall Troubleshooter
Microsoft tool that removes orphaned MSI entries blocking reinstalls
Visit official site ↗
Windows Installer (msiexec)
Built-in tool for verbose logging and service re-registration
Visit official site ↗
Sysinternals Process Monitor
Traces exactly which file or registry access the installer was denied
Visit official site ↗
CrystalDiskInfo
Confirms drive health and that the disk isn't failing mid-install
Visit official site ↗
Windows PowerShell
Set folder permissions and manage services while troubleshooting
Visit official site ↗Step-by-step fix
-
1
Right-click the installer or MSI and choose Run as administrator.
-
2
Free up disk space on both the target drive and the drive holding your TEMP folder.
-
3
Uninstall any partial or older version of the software, then reboot to clear locked files.
-
4
Re-run the MSI with logging: msiexec /i "setup.msi" /L*v "%TEMP%\install.log".
-
5
Open install.log, search from the bottom for 'return value 3', and read the lines just above to find the failing action.
-
6
On the install folder's Security tab, give SYSTEM and Administrators Full Control and remove EFS encryption if present.
-
7
Open services.msc, ensure Windows Installer can start, and if needed re-register it with msiexec /unregister then msiexec /regserver.
-
8
Run Microsoft's Program Install and Uninstall troubleshooter to clear orphaned entries, then retry the install as administrator.
What Error 1603 Really Tells You
1603 is a top-level MSI result code meaning the installation ended in failure and rolled back. It doesn't identify the underlying cause on its own, which is why the same code covers permission problems, leftover registrations, and disk issues.
The most reliable way to find the true cause is the verbose MSI log. The installer records every action; searching the log for "return value 3" lands you right before the action that actually failed, turning a vague 1603 into a specific, fixable problem.
Most Common Fixes First
Before diving into logs, try the quick wins that resolve most 1603 errors:
- Run as administrator. Right-click the installer or MSI and elevate.
- Free up disk space. 1603 is common when the target or temp drive is nearly full.
- Remove the old version. A partially installed or broken previous version frequently blocks the new one.
- Reboot and retry. A pending file-rename operation or locked file can cause it; a restart clears those.
If one of these doesn't fix it, the verbose log will point you to the rest.
Generating and Reading a Verbose Log
To capture detail, run the MSI from an elevated Command Prompt with logging enabled: msiexec /i "path\to\setup.msi" /L*v "%TEMP%\install.log". After it fails, open install.log and search from the bottom for return value 3.
The lines just above that marker name the failing action, often a file copy into a protected folder, a service that wouldn't start, or a custom action that errored. That single clue usually tells you exactly which permission, folder, or dependency to fix.
Permissions and the Windows Installer Service
Many 1603 failures come down to the SYSTEM account lacking Full Control on the destination folder, or the target folder being encrypted with EFS. Right-click the install folder, open the Security tab, and ensure SYSTEM and Administrators have Full Control; remove encryption on that folder if it's set.
If the Windows Installer service itself is the issue, open services.msc and confirm Windows Installer is set to start. You can also re-register it by running msiexec /unregister followed by msiexec /regserver from an elevated prompt.
Clearing Out a Broken Previous Install
Leftovers from a failed or partial uninstall are a leading 1603 trigger. Use the app's own uninstaller first, then Microsoft's Program Install and Uninstall troubleshooter to remove orphaned registry keys and MSI registrations that block reinstallation.
For stubborn cases, deleting the leftover program folder (after taking ownership) and clearing the related entry from Programs and Features lets the fresh install proceed cleanly. Then reboot and run the installer again as administrator.
Frequently asked questions
Questions & answers
No questions yet — be the first to ask!
Ask a question
Please sign in with your email to ask a question.
Comments (0)
No comments yet. Share your experience!
Leave a comment
Please sign in with your email to comment.