Error 1603
Fatal error during installation
Error 1603 is Windows Installer's generic failure code: it means the installation stopped, not why. The cause is almost always one of four things, and there is a log file that tells you which.
What it actually means
MSI returns 1603 whenever an install fails and no more specific code applies. Because it is a catch-all, guides that offer a single fix are guessing. The useful move is to read the log, which Windows can be asked to produce, and let it name the actual failure.
How to fix it, in order
Ordered by how often each one is the answer, not by how clever it sounds.
- 01Check whether the software is already installed, including a newer version. Installing over an existing copy is the single most common cause. Uninstall it first, then retry.
- 02Run the installer as administrator. Right-click, Run as administrator. Insufficient permissions on the target folder produce 1603 with no other clue.
- 03Make sure there is enough free space on the system drive, and that the destination folder is not encrypted or on a network path.
- 04Get the real error: run "msiexec /i package.msi /l*v install.log" and open install.log. Search for "return value 3", which marks the action that actually failed, and read the lines just above it.
- 05Restart and retry. A pending reboot from a previous install genuinely blocks the installer, and Windows does not always say so.
- 06If the log points at a missing runtime, install that first. Many installers assume a Visual C++ runtime is already present.
Search the log for "return value 3"
This is the single most useful trick with 1603. The verbose log is long and repetitive, but the failing action always logs "return value 3" immediately after it. The lines just before that tell you what it was trying to do when it stopped, which turns a generic code into a specific problem.
Common questions
- What does error 1603 mean?
- It is Windows Installer's generic fatal error, meaning the installation stopped without a more specific code. The real cause is in the installation log: run the installer with /l*v to produce one and search it for "return value 3".
- How do I fix error 1603?
- Uninstall any existing version first, run the installer as administrator, confirm there is free disk space and no pending reboot, then read the verbose log if it still fails. Those four cover the large majority of cases.
Before you retry the installer
If the package came from anywhere other than the publisher, confirm it is the file they actually shipped. Check its SHA-256 against our index, which settles in seconds whether you are debugging an installer or a damaged download.