Setup Wizard for Exchange Update Rollup ended prematurely

/

The issue is well-known, but I never got around to share it myself and just recently saw it once again at a customer, who experienced the problem.

This blog post will cover how to install and the Exchange Rollup Update successfully without getting the “Ended prematurely” error.

The Setup Wizard for Update Rollup fails with the error “ended prematurely”. It has been the same issue for Update Rollups for both Exchange 2007 and Exchange 2010.

The installer fails with the information:

Setup Wizard for Update Rollup 5 for Exchange Server 2010 Service Pack 3 (KB2917508) ended prematurely because of an error. Your system has not been modified. To install this program at a later time, please run the installation again.

The screen dump below also shows what error look like:

clip_image002

The reason for the error and why the Update Rollup installer is “ended prematurely” is because the server has User Access Control (UAC) activated on the server. For good reason, it is not recommended to disable the UAC.

The error is also shown in the event log, as Event ID: 1024 and with error code 1603.

image

 

How to Install the Update Rollup

The recommended process for installing Update Rollups on the server, is using an elevated command prompt (Open a CMD with Run As Administrator) and make sure the Update Rollup is located on a local drive of the server and start the installer using:

SYNTAX example: msiexec /update <UPDATE .MSP FILE>

How to Start Setup Wizard:

msiexec /update Exchange2010-KB2917508-x64-en.msp

How to install the Update Rollup unattended (silent) add the following parameter (/quiet):

msiexec /update Exchange2010-KB2917508-x64-en.msp /quiet

Example as elevated command prompt starting the Update Rollup installer:

image

This will start the Setup Wizard and you can now walk your way through the installer and install the Update Rollup and when it has been installed, you should see the following:

clip_image002[8]

 

Other reasons for failing

The above is the most obvious reason for why the Update Rollup fails with “ended prematurely”, but if you see error codes 1603 or 1635 in the event log, there could be other reasons. See the following KB articles on this, which might be able to help you in those scenarios:

Tweet
Share
Share
Pin
0 Shares

25 thoughts on “Setup Wizard for Exchange Update Rollup ended prematurely”

  2. Is it possible to just press the right button and execute it as an administrator?

  6. Hi peter ,

    i have problem , it is work to exchange server 2010 sp3 update rollup 11 ended prematurely ? because i try to elevate command prompt , error message “this patch package could not be opened, contact the application vendor to verify that this is a valid windows installer patch package” .. , please help me ..

    Thanks ,
    Randika

  9. kb3141339 package could not be opened. I cant able to install the patches.

    i have run as administrator in cmd i could not..

  10. getting below error while installing Rollup-14.

    “Product: Microsoft Exchange Server — The installer encountered an unexpected error while installing this package. This may indicate a problem with this package. The error code is 2771”.

    help Please.

  11. Hi,

    I am getting below error while installation Exchange 2010 Rollup-14.

    “Product: Microsoft Exchange Server — The installer encountered an unexpected error while installing this package. This may indicate a problem with this package. The error code is 2771”.

    help Please.

  12. This should be in the installation guide or as instruction when you download it!

  14. THANK you for this article. I had installed SBS 2011 from scratch on a new server. I was installing the Service Packs and updates. I worked with 2 Microsoft Techs over 2 days for 7 hours and we could not get Exchange 2010 SP3 CU16 to load. They made all kind of changes to permissions and settings and finally caused complete instability in the server and I had to reload the entire server. After reloading the server I could not get CU16 to load and I started looking on the internet for a solution. I found this post and went ahead and disabled the UAC and CU16 loaded flawlessly.

  15. It’s all bullshit it doesn’t work. I tried everything stated above and other methods. I had them all installed through Windows update from 12 to 17 but there was a problem in OWA deleting emails and the fix was to uninstall the UR and install manually and not through windows update. This is what was advised.

    “The best thing to do is to remove the latest Rollup that was just installed and that should resolve all your problems. Do this from Programs and Features > View Installed Updates. Once it’s working properly again you want to re-install the latest rollup manually instead of via Windows Update.
    Microsoft Exchange team actually tells you off the books to NOT use Windows Update when installing Exchange Updates as sometimes it won’t do it correctly”.

    LOL what a load of rubbish! this is coming from Microsoft themselves!! the Microsoft Exchange team!. How dodgy is all this… give me a break!! Unleash the hounds!!

  17. I had this issue and it wasn’t due to Administrator rights, but the domain login I was using, while full Domain Admin etc., was not the same Admin account used to install Exchange (or may have been missing Exchange group membership/etc). To fix I logged in as the original domain Administrator account and it worked fine.

Comments are closed.