Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 1603

MSI Error 1603 and 1618: SQL Server Tools and Update Installs Keep Failing

10 min read Updated October 5, 2026 SQL Server

Fix it now

Neither of these is a SQL Server error. 1618 is Windows Installer refusing because another installation already holds the machine-wide lock. 1603 is Windows Installer reporting that a package failed and rolled back, with no clue attached. Find the blocking or failing installer action rather than reinstalling SQL Server.

First line for 1618, second for 1603. Use /p for a patch and /x to remove

tasklist | findstr /i msiexec
msiexec /i "package.msi" /L*v C:\temp\install.log
  1. For 1618, see what else is installing. Windows Update, an endpoint agent or a management client will not announce itself. Let it finish, reboot, retry.
  2. If nothing is running and 1618 persists, reboot anyway. A pending file rename blocks the installer as effectively as a live install.
  3. For 1603, rerun with the verbose log above and read it for the action that failed. Work upwards from the failure to the action name.
  4. If the log names a missing file under %windir%\Installer, this is the installer cache case. Repair the installation with setup.exe /ACTION=REPAIR /INDICATEPROGRESS=TRUE rather than reinstalling the instance.

/L*v is deliberate: the * wildcard logs everything except verbose and extra-debug output, so the v has to be spelled out to get a verbose log at all.

If the package completes, you are done. If not, the next section explains what each code is reporting and which of the three situations you are in.

Why it happens

Every MSI package runs as a sequence of named actions: copying files, writing registry values, registering components, running custom actions. If one fails, Windows Installer rolls the whole transaction back and returns 1603 to whatever launched it. Microsoft’s published text for it is simply “A fatal error occurred during installation”, which is honest about how little it says. 1603 is the return code for a rollback, not a description of a fault, and the verbose log is where the fault is.

1618 is more specific and far more common. Windows Installer serialises installations for the whole machine through a mutex, and Microsoft’s published text says exactly that: another installation is already in progress, complete that installation before proceeding with this install. If something else holds the lock, yours is refused immediately, before it does anything at all.

SQL Server adds a third situation that neither code describes. Applications that use Windows Installer keep copies of their packages in the installer cache under %windir%\Installer, and those files are required for uninstalling and updating. They are unique to that computer. If a disk cleanup routine removed one, a later patch has nothing to apply against. Microsoft documents the symptoms as messages naming a missing cached MSI or MSP file, and lists error 1648, plus 1636, 1714 and 0x84B20001 on older releases.

That last case is the one worth recognising early, because the instinctive response – uninstall and reinstall – is both the most disruptive option and unnecessary. Microsoft’s documented first remedy is a repair of the existing installation.

Another installation holds the installer

You have this one if 1618 arrives immediately, and msiexec.exe is in the task list, or the machine is mid Windows Update.

  1. Identify what else is installing: Windows Update, an endpoint agent, or a software distribution client.
  2. Let it finish and retry. Nothing you do to your own package changes a machine-wide lock held by something else.
  3. Reboot and start your install before anything scheduled gets in first.

On a machine with a software deployment agent, run outside the agent’s maintenance window or the same collision repeats on the next attempt.

A pending reboot is blocking everything

You have this one if Nothing else is installing, but the failure survives repeated attempts.

  1. Reboot first. In most cases that is the entire fix.
  2. If it survives one reboot, let Windows Update finish completely and reboot again before concluding anything is stale.
  3. Only then consider inspecting the registry values Windows uses to track pending restarts, and export anything before you remove it.

Deleting a pending-rename entry that a genuine update is waiting on leaves that update half applied, which is a worse problem than the one you started with.

A single action inside the package is failing

You have this one if 1603 with nothing useful on screen, and the installer rolls back everything it did.

  1. Rerun with /L*v and a log path you can reach, then read for the action that failed and the line immediately before it.
  2. Typical findings are a file in use, a folder the account cannot write to, a service that would not stop, or a custom action that needed elevation.
  3. Address that specific finding and rerun. The code will not change; the action name is what you are working on.

Launching a package by double-clicking can lose elevation on some systems. Running msiexec from an elevated command prompt removes that variable, which is what resolves a good number of tools installs.

The cached installer package is missing

You have this one if The log names an .msi or .msp under %windir%\Installer that cannot be found or opened, or you see 1648, 1636, 1714 or 0x84B20001.

  1. Repair the installation first: setup.exe /ACTION=REPAIR /INDICATEPROGRESS=TRUE from media for the installed build.
  2. If that does not clear it, Microsoft points at FixMissingMSI, which scans for missing cached files and recaches them from media you point it at, and at the FindSQLInstalls.vbs script for an inventory of what is installed.
  3. Rerun the update once the cache is complete.

Disk cleanup routines that empty %windir%\Installer cause exactly this. Exclude that folder from cleanup policies on database servers – it is what future patches are applied against.

Full reference

Telling the situations apart

What you see What to do
1618, and msiexec is running Wait for the other installation, then retry
1618 with nothing running A pending reboot is holding the installer. Restart the machine
1603 with a failing action in the verbose log A locked file, a folder the account cannot write, or a custom action needing elevation
1603 during a cumulative update, log naming %windir%\Installer A missing cached installer file. Repair rather than reinstall
1648 No valid sequence could be found for the set of updates: the cache is incomplete
29506 on a tools install Run the package from an elevated command prompt and read its own log

Commands

Command What it does
msiexec /i "package.msi" /L*v C:\temp\install.log Installs with a full verbose log
msiexec /p "patch.msp" /L*v C:\temp\patch.log Applies a patch with a full verbose log
msiexec /x "package.msi" /L*v C:\temp\remove.log Removes a product with a full verbose log
tasklist | findstr /i msiexec Shows whether another installation is currently running
setup.exe /ACTION=REPAIR /INDICATEPROGRESS=TRUE Repairs an existing SQL Server installation, including recaching its files
Cscript FindSQLInstalls.vbs out.txt Inventories what SQL Server installs and patches the machine believes it has

The /L switch, precisely

Windows Installer’s logging switch takes modifier letters: i status messages, w non-fatal warnings, e errors, a action start-ups, r action records, u user requests, c initial UI parameters, m out-of-memory information, o out-of-disk-space messages, p terminal properties, v verbose, x extra debugging, + append, ! flush each line. The * wildcard means everything except v and x, which is why /L*v is the usual form and /l*vx is the one to use when you need the extra debugging as well.

The installer cache, and why it matters on a database server

  • The default location is %windir%\Installer, normally C:\Windows\Installer.
  • The files there are unique to that computer. They cannot be copied from another server that looks the same.
  • They are what uninstalls and patches are applied against, so removing them breaks future updates rather than the current installation.
  • Microsoft’s documented remedies, in order, are: repair the installation, use FixMissingMSI, use FindSQLInstalls.vbs to inventory, restore the files by hand from the original media, or restore from a system state backup.
  • Exclude the folder from any disk cleanup policy that runs on database servers.

29506, and what can honestly be said about it

29506 turns up on SQL Server tools installs and there is no current Microsoft documentation that publishes a meaning for it. Treat it as a failure inside the package’s own configuration work rather than as a code to look up. In practice, running the package from an elevated command prompt rather than by double-clicking resolves a good proportion of them, and where it does not, the package’s own verbose log names the action that failed. Anyone offering you a definitive meaning for the number is guessing.

Why the same update works on one server and fails on another

These failures are about machine state rather than the package: what is already installed, what survives in the installer cache, which agents are running, and which folders the installing account can write. Comparing the two machines on those four points finds the difference far more often than comparing downloads does. The installed features discovery report and FindSQLInstalls.vbs give you the first two in a form you can diff.

Every code this article covers

Code What it points at Source
1603 Windows Installer ERROR_INSTALL_FAILURE: a fatal error occurred during installation, and the package rolled back Microsoft Learn
1618 Windows Installer ERROR_INSTALL_ALREADY_RUNNING: another installation is already in progress and must complete first Microsoft Learn
29506 Raised by SQL Server tools packages during their own configuration work. No meaning is published by Microsoft; read the package’s verbose log and retry from an elevated prompt not published by the vendor

Confirm the fix worked

  1. The package completes and reports success rather than rolling back.
  2. For an engine update, SELECT SERVERPROPERTY('ProductVersion'); returns the new build number.
  3. The update appears in the machine’s list of installed updates.
  4. Rebooting does not put the machine straight back into a pending-restart state.
  5. A second, unrelated MSI installs without returning 1618, which proves the lock is genuinely free.

Questions people ask about this

Do I have to uninstall and reinstall SQL Server?

Rarely, and it is much the most disruptive option. Nearly every 1603 comes down to one failing action that the verbose log names, and where the cause is a missing cached installer file, Microsoft’s documented first remedy is a repair with setup.exe /ACTION=REPAIR.

Does any of this cost money?

No. Windows Installer is part of Windows, verbose logging is built in, and the tools Microsoft points at for restoring a missing installer cache are free. There is nothing to buy to make a package install.

Can I delete the Windows Installer cache to free space?

No. That folder is what future patches are applied against, and emptying it is the direct cause of the missing-cache failures. The files are unique to the machine and cannot be replaced from another server. Free space somewhere else.

What does 29506 mean?

Microsoft does not publish a meaning for it, so nor will we. It appears on tools installs during the package’s own configuration work. Run the installer from an elevated command prompt and read its verbose log for the action that actually failed.

Why does 1618 appear when I can see nothing installing?

Because the machine-wide installer lock is also held across a pending restart. Reboot, then start your install before Windows Update or a deployment agent gets in first.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix SSIS Error 0xC020801C: Cannot Acquire Connection From Connection Manager Free Fix SQL Server Error 18456: Read the State Number to Find the Real Cause Free Fix Error 8623: The Query Processor Ran Out of Internal Resources License Error Error 8645: Memory Grant Timeouts Against the Standard Edition Memory Cap
โ† Back to Knowledge Base