Installing Update Rollup 2 for Exchange 2010 Service Pack 3 may fail or prompt for Installation Package Source

Installing Update Rollup 2 for Exchange 2010 Service Pack 3 may fail or prompt for Installation Package Source

  • Comments 6
  • Likes

[This post comes to us courtesy of Manish Kapoor from Microsoft Commercial Technical Support]

Update Rollup 2 for Exchange Server 2010 Service Pack 3 has been released and may be offered by WSUS on your SBS 2011 Standard server. The update is also available for standalone download and install here.

If you try installing the rollup from Control Panel – Windows Update, you may notice that it fails with the following error:

image

Additionally, if you have downloaded the Update Rollup 2, setup wizard may prompt you for path to the Installation Package:

image

You should be able to complete setup by downloading Exchange Server 2010 Service Pack 3 (available here), extract the installation files locally on the server and pointing the wizard to location of Service Pack 3 binaries. Here is a step by step on the above:

  1. Download Exchange Server 2010 Service Pack 3.
  2. Right click on “Exchange2010-SP3-x64.exe” and select “Run as Administrator”. This will prompt you to specify the location where you want to extract the files. Create a temporary folder where you want the binaries to be extracted and specify the folder path in this dialog box.

    image
  3. Once extraction is complete, specify path to this folder in the UR2 installation wizard.

    image

Update Rollup 2 Setup should complete successfully without any further issues.

Above issue is not seen if the folder containing Exchange Service Pack 3 binaries has not been deleted. If you want to confirm the location where Service Pack 3 installation files were stored at the time of installation, you could check the value of InstallSource at the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{4934D1EA-BE46-48B1-8847-F1AF20E892C1}

This workaround can be used to install Update Rollup 2 while we are still investigating the cause behind installation source prompt. This post will be updated as soon as we have an update on this issue.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Comments
  • I tried that workaround, but I still got a different error installing after doing this workaround. This update definitely needs more work...

  • I have Server 2008 Standard service pack 2, when i am updating microsoft .net framework 4.0 in available update, i could not able to update. Error found Code 13ec windows update encountered an unknown error

  • To Iwan this update should install with this sp3 folder in place.  If you are hitting something else, please post in the sbs forum to investigate.  As this update won't be worked on /rereleased.

    Please post here - social.technet.microsoft.com/.../home

  • Sorry to tell you, but it even prompts for the Installation file if the original files have not been deleted.

    I do have that on one of my Servers. And the original file is not accepted. I do have it in my Installation Folder. It tells me that it is not a valid file - even so it is the one I installed it from.

    THIS IS REALLY ANNOYING...

  • Testing in my lab, and it kept ending Prematurely with no specific errors in the GUI.  Checked the ExchangeSetupLog directory which showed I was getting "Access Denied" errors to all the Exchange services it was trying to stop at the beginning of the install on Exchange 2010 SP3 RU2.

    At first I was trying to run it from Windows Explorer using "Run As Administrator".  Validated all my permissions to Enterprise, Domain and Schema Admins along with Organization and Server Management - Still fails.  I still have the Exchange 2010 SP3 installation files, so that was not an issue.  Then I just tried running it from an Administrative Command Prompt... Installation completed successfully in the time it took to write this memo.

    Good luck!

  • Has anyone tested the following?

    1. create a share with those files in and give all the exchange servers read permission on it

    2. change the InstallSource value to the unc name of the share by group policy for those servers