1618 Failures during VS Setup

I was just going through the setup newsgroups and noticed some questions about 1618 failures. 

A 1618 failure occurs when another setup package using the windows installer is running.  Since the Windows Installer supports only one set up running at any given time, launching a second set up package will result in a 1618 error to the second set up package.  The first setup package will still continue to run.

Visual Studio's setup itself is a bootstrapper.  That means it chains in a bunch of MSIs (individual setup packages).  A 1618 error may occur during VS install because as VS finishes up one setup package and then launches another one, the gap in between the two setup packages may occasionally be enough time for Windows Installer to start installing a patch it just downloaded.  It's a race condition.

We saw a lot of these types of failures internally because our IT department pushes down patches when they're available.  If you happen to be installing VS at that time, the patches will try to install the first chance it gets which could be in that little windows when the setup packages finishes and a new one starts up.

The workaround for this is to wait a few minutes for the patch to complete and then rerun setup or install the failed component manually from the \wcu folder off the root folder.


Comments (3)

  1. RobertWrayUK says:

    Surely in the grand scheme of things, this workaround is a bit pants?

    I don’t claim to know anything about Windows Installer, but surely there should be some functionality to allow the following (for example):

    Setup Routine Starts

    -> Opens an MsiInstallerTransaction

    –> Gathers all the user input required

    –> Runs MSI Package 1

    –> Runs MSI Package 2

    –> …

    –> Runs MSI Package n

    –> Finalises

    -> Closes MsiInstallerTransaction

    Whilst this MsiInstallerTransaction (made up name!) is open, no Msi Package can start which doesn’t belong to that transaction.

  2. RobertWrayUK says:

    Erk – just wanted to point out that I didn’t mean " Surely in the grand scheme of things, this workaround is a bit pants? " to sound rude or bolshy! 🙂

  3. Quan says:

    One of the current limitations with Windows Installer is that it doesn’t "chain" multiple MSIs together (which is why we had to build our own infrastructure to do that).

    We’ve asked the Windows Installer team for an "MsiInstallerTraction" feature in future releases.

Skip to main content