Exchange 2010 Update Rollups and Error 1603

You download and begin to install an Exchange Rollup Update only to find after waiting ages for it do the NGen stuff it fails, and on watching it closely you notice it fails on stopping services.

In the event log you are pointed at a website with information on verbose logging for MSI installations.

But you can forget that – the fix is easy! Start and administrative command prompt and run the rollup update from the command line! It will work first time (as long as the update msi file is actually copied to the local machine, it will typically not run from a copy on a network drive.

Comments & Responses

5 Responses so far.

  1. Anonymous says:

    I got Error 1603 in my Rollup 3 installation. Do you mean I need to extract the files locally and run the setup in command line?

  2. Brian Reid says:

    No, you just need to start the Command Prompt as an administrator. That is right-click the Command Prompt shortcut and choose Run As Administrator. From here you need to just run the MSI download – nothing else to do. If you run the download with /quiet at the end then there really is nothing else to do.

  3. Anonymous says:

    thank you!

  4. Anonymous says:

    Simple and stupid (that it’s necessary) and oddly undocumented anywhere in MS support collateral.

    Thanks lifting the kilt on this one.

  5. Brian Reid says:

    On the old version of this blog, hosted on Blogger, there were lots of other comments that did not get migrated across. These included:

    Neil Natic, Sept 2013: “Thanks for this. huge help!”

    Thomas Nielsen, Sept 2013: “I know this is a old post, but this solution also solved my issue installing Exchange SP3 Rollup 2 :-)”

    Diem Silvan, Aug 2013: “Wow – works fine now : Exchange 2010 SP1 Rollup 8 Thanks a lot!!!”

    Jerry Locke, May 2013: “Wow, that’s amazingly stupid behavior on the part of the patch installer. Even stupider that it’s not properly documented over two years later.

    Thanks for the tip, I can verify it working correctly for Update Rollup 1 on Exchange 2010 SP3 (KB2803727). Strangely, this is the first time I’ve encountered this particular behavior, previous rollups have worked fine”

    Frits Luten, May 2013: “The other option is to set the UAC (temporarely) to nothing … after that you can install the Rollup without having to use the command prompt and from any networkshare. Had the same problem with installing Rollup 6 for Exchange 2010 SP2 this morning ….”

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>