1603

What it means

The most generic failure Windows Installer can return. It means the install ran and then something inside it failed. The code itself tells you nothing about what failed, which is why it shows up on almost every failed deployment. The real reason is always in the MSI log, never in the code.

Real causes

• A custom action inside the MSI failed and rolled the install back.
• The account running the install does not have rights to a target folder or registry key.
• The product is already installed, or a newer version is present.
• The target directory does not exist, is on an unavailable drive, or is encrypted.
• Not enough disk space on the target volume.

What to do

1. Re-run with verbose logging: msiexec /i package.msi /l*v C:\Windows\Temp\install.log /qn
2. Open the log and search for "Return value 3". The action immediately above that line is the one that failed.
3. Also search for "Note: 1: 2262" and "error status" for secondary detail.
4. If a custom action is failing, check whether it needs a user context that a SYSTEM-context deployment does not have.
5. Confirm the target path exists and the deployment account can write to it.

Where to look

• The MSI verbose log you generated with /l*v
• %windir%\Logs\CBS\CBS.log when 1603 comes from a Windows update

Checked against Microsoft documentation. Last reviewed 2026-08-20.

Decode another code