Windows Update Error code 0x80070643 installing Update Rollup 4-v2 or 5-v2 for Exchange Server 2010 SP2

How to resolve Windows Update Error 0x80070643 when installing an update 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 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 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 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.


  • Go to Uninstall all programs on your control panel
  • Click on the Updates section so you see Windows Updates installed not applications
  • Find the Windows Management Framework and perform an uninstall.


As mentioned previously Microsoft instructs to install the management framework on your 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 KB2506146 and KB2506143 (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:

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: 

Enhanced by Zemanta

You may also like...

8 Responses

  1. Thomas Leinberger says:

    Thank you, this workaround solved it. Good job.

    • JCarlos says:

      You’re welcome. It was driving me crazy too! I wasn’t expecting that to be the reason considering Microsoft has you install it but oh well, glad I could help.

  2. Lonnie says:

    What if you don’t gave management framework installed and keep getting the same error

    • Carlos says:

      Hi Lonnie,

      Although I am not sure then what could be causing your problems try downloading the updates directly from Microsoft and applying them manually to see if that works. The other thing to keep in mind is that the management framework gets deployed via Windows Update. Even if you did not manually install it you still get it with the updates. I would go and double check it is not installed. If I had to bet I would put the odds in that but if not then I don’t have any better ideas right now. If it turns out to be something else let me know so I can make that information available to others as well. Good luck!

      • Lonnie says:

        – I have tried manual download
        – Tried installing it in multiple admin accounts
        – I triple checked the Management Framework
        – I even installed it and then removed it to see if that fixed the problem
        – I have tried all the hot fixes for the 0×80070643 error. Nothing works
        – Stymied every time

        • Carlos says:

          … looks like a rough one. I might look into reinstalling my server or installing a new VM replicating the setup to see if you experience the same behaviour or is computer specific. Do you get any messages or additional details on the event log? Even though Microsoft recommends installing all updates before installing a product sometimes the installation goes more smoothly if you update after you are done installing. If you have more details I can try looking around to see if I can get any additional information.

          • Lonzo says:

            I ended up installing SP3 and that fixed everything. But then I couldn’t connect to it at all then I gave up and tried to uninstall it and cratered server 2011 and had to re-install 🙁

          • Carlos says:

            🙁 That’s aweful. I didn’t know SP3 had finally been released. If SP3 doesn´t require the rollup updates I would just jump straight to it. Sorry you had to reinstall, I hope this time around it works from the get go.

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.