Note: This article was originally published in 2012. Some steps, commands, or software versions may have changed. Check the current Exchange 2010 documentation for the latest information.

If you’re encountering this issue, this troubleshooting guide will help you identify the root cause and apply the appropriate fix. This applies to Exchange 2010 environments.

How to resolve (http://www.microsoft.com/WINDOWS “Windows”) Update Error 0x80070643 when installing an update (http://en.wikipedia.org/wiki/Rollup “Rollup”) for Exchange Server

Installation Failure: Windows failed to install the following update with error 0x80070643: Update Rollup 4-v2 for Exchange Server 2010 SP2 I am currently working on installing (http://www.microsoft.com/exchange “Microsoft Exchange Server”) 2010 into a Windows 2008 R2 Server box. As you can read from a previous post there is a list of steps posted by (http://www.microsoft.com “Microsoft”) on how to successfully install Exchange 2010 on your Windows 2008 R2 Server. I have followed diligently all the steps and just recently updated to Exchange 2010 SP2 manually as Windows Update was not displaying that as an option. After a few updates I got stuck with Update Rollup 4-v2 for Exchange Server 2010 (http://en.wikipedia.org/wiki/Service_pack “Service pack”) 2 (KB2756485) and Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2 (KB2785908) failing with Windows Update Error 0x80070643. After doing some research it turns out Windows Management Framework is the culprit behind this! But wait a second… Microsoft’s instruction for installing Exchange 2010 included installing the latest Windows Management Framework. What’s worst, is that Windows Update pushes that update as well to Windows server clients. My guess is that probably a later update provides the compatibility but for now if you have the management framework installed the update will fail.

Resolution

  • Go to Uninstall all programs on your control panel
  • Click on the Updates section so you see (http://en.wikipedia.org/wiki/Windows_Update “Windows Update”) installed not applications
  • Find the Windows Management Framework and perform an uninstall.

Notes

As mentioned previously Microsoft instructs to install the management framework on your (http://www.windowsserver.com “Windows Server”) as part of the Exchange 2010 pre-configuration. The only thing that seems to break at this time for me is the installation of the rollup updates, theoretically you could reinstall the management framework once you are done updating your server if that is something you need. I would recommend contacting Microsoft directly to get a clear and supported answer to this problem and reinstalling the management framework but this is something to keep in mind. UPDATE: Microsoft does not support Windows Management Framework 3.0 with any version of Exchange 2007 or Exchange 2010 at the time of the update.

Microsoft’s response to this issue:

Windows Management Framework 3.0 on Exchange 2007 and Exchange 2010

Recently, Windows Update began offering the Windows Management Framework 3.0 as an Optional update. This includes all forms of update distribution, such as Microsoft Update, WSUS, System Center Configuration Manager and other mechanisms. The key bit here is that the Windows Management Framework 3.0 includes PowerShell 3.0. Windows Management Framework 3.0 is being distributed as (http://support.microsoft.com/kb/2506146) and (http://support.microsoft.com/kb/2506143) (which one is offered depends on which server version you are running - Windows Server 2008 SP2 or Windows Server 2008 R2 SP1).

What does that mean to you?

Windows Management Framework 3.0 (specifically PowerShell 3.0) is not yet supported on any version of Exchange except Exchange Server 2013, which requires it. If you install Windows Management Framework 3.0 on a server running Exchange 2007 or Exchange 2010, you will encounter problems, such as Exchange update rollups that will not install, or the Exchange Management Shell may not run properly. We have seen Exchange update rollups not installing with the following symptoms:

  • If rollup is installed through Microsoft Update, the installation might error with error code 80070643
  • If rollup is installed from a download, the error displayed is Setup ended prematurely because of an error.
  • In both cases, Event ID 1024 may be logged in the Application event log with the error error code “1603”. For example, if you try to install update roll 5 for Exchange 2010 SP2, you may see the following description in event ID 1024:

Product: Microsoft Exchange Server - Update ‘Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2 (KB2785908) 14.2.328.10’ could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127

Our guidance at this time is that Windows Management Framework 3.0 should not be deployed on servers running Exchange 2007 or Exchange 2010, or on workstations with the Exchange Management Tools for either version installed. If you have already deployed this update, it should be removed. Once you remove the update, functionality should be restored. Obtained from: (http://blogs.technet.com/b/exchange/archive/2012/12/14/windows-management-framework-3-0-on-exchange-2007-and-exchange-2010.aspx)

(http://img.zemanta.com/zemified_h.png?x-id=35d5dd52-ee6e-4697-915c-562a1d3bd1c5)](http://www.zemanta.com/?px “Enhanced by Zemanta”)

Summary

This guide covered the common causes and solutions for this Exchange 2010 issue. If the problem persists, check the official documentation or system logs for additional diagnostic information.