This post is also available in: Polish
Installation of Rollup 4 for Exchange 2010 SP2 fails:
Few days ago Microsoft has released new versions of latest Rollups for Exchange 2010 and 2007.
All of those rollups (version 2) we can install on server without uninstalling previous version.
When you are trying to install version 2 of Rollup 4 for Exchange 2010 SP2 you can get error 0x80070643
How to resolve issue with Rollup 4 v2 for Exchange 2010 SP2 error code 0x80070643
If during installation of Rollup 4 version 2 you will get error code 0x80070643 then you have to do following:
- uninstall from Windows Server Windows Management Framework 3.0 (WMF 3.0) (Windows6.1-KB2506143-x64)
- reboot server
- install update Rollup 4-v2 for Exchange 2010 SP2
- reboot server
install Windows Management Framework 3.0 after installing the Rollup 4-v2because of issues with installation of Rollup 5 and WMF 3.0 it’s better to not install WMF 3.0
We hope it will also help to update yours environments.
I have been fighting with this ever since this rollup was released. Removing WMF3 fixed one server which was just installed in the past few days; however I have another which has existed and has had updates installed since Exchange 2010 RTM. On that one, removing WMF3 gets to 98% after the reboot, then dies and reverts the changes, leaving it installed. Any ideas on that?
What Exchange server roles do you have on this server ?
Just the default roles: Mailbox, Hub Transport, Client Access and Admin Tools.
Did you checked Event Log specially application. Do you see any errors ?
Did you run Rollup 4-v2 update from CMD with run as Administrator ?
I have tried to install every way possible: from WSUS, from command line as administrator. I searched every log I could find but nothing useful. Now I find your article but I can’t get 2506143 to uninstall.
check this link: http://technet.microsoft.com/en-us/library/ff772434(v=exchg.80).aspx
and try to Set-ExecutionPolicy Unrestricted and Execute the MSP installation file from an elevated command prompt
also you can try with this:
On your server, be sure that you don’t have the Framework NET 4 installed. Remove all these Framework NET 4 component and try again:
In Microsoft Exchange\v14\Scripts
Line 462 of ManageScheduledTask.ps1
Change “return $success” in “Write-Output $success” (for the result of the TryExecute-ScriptBlock function)
PowerShell : Set-ExecutionPolicy Unrestricted
Open a command prompt in Administrator mode and launch Rollup with log: Exchange2010-KB2756485-v2-x64-xx.msp /lxv* Rollup4v2.log
During the Rollup installation, wait until it stop saying “Stoppping services” and while the Rollup is continuing, put the “Windows Management Instrumentation” service back to Automatic and restart it
Rollup4v2 should be successfull
Powershell: Set-ExecutionPolicy RemoteSigned
WOW, you are “da man” – that actually worked! I did all of what you suggested except for uninstalling .NET 4 and it finally succeeded. Many thanks!
Also, the article you linked cleared up a point of confusion for me. I was under the impression that the previous rollups were considered “interim updates” which needed to be uninstalled; a false assumption.
I’m glad I could help you
I was just at the point of deciding that it would be easier to deploy a new server and migrate everything, now maybe I can survive until SP3 and migrate it to Exchange 2013 then.
Apparently your article is the only one on the entire Internet to address this specific problem, your blog is now in my favorites folder.
Thanks, we’re always trying to help if we can.
Thanks! Removing WMF 2506143 did for me! : )
FYI: exact same behavior and exact same fix for “Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2 (KB2785908)” – uninstall KB2506143, install update rollup, install KB2506143.
Now that Windows Management Framework 3.0 has been officially released on Windows Update and is causing probably large numbers of people to experience this issue, hopefully Microsoft will notice and fix whatever it is in WMF that is breaking Exchange rollups.
You can check also this article, we found this solutions for errors 1603 and 1635
Exchange Server 2010 rollup upadate error 1603 or 1635
Pepper’s technique led me to a clean update of both the Rollup 4-v2 and the Rollup 5-v2. So, WMF is highly suspect at this point in time. Follow Pepper’s techniques as he describes ‘em and these upgrade problems disappear.
It’s nice to see people leaving these really helpful, useful tips. Thanks! : )
I think you should correct your “Step by Step” to fix this problem since WMF 3.0 should not be installed in an Exchange server. The problems is generated by powershell 3.0 included in WMF 3.0. This version of powershell is not compatible with Exchange 2007 and 2010.
For more information review the post in the EHLO blog:
we wrote about WMF 3.0 and KB in post with issues when you want to install Rollup 5
Exchange Server 2010 and 2007 Issues with Windows Updates KB2506146 and KB2506143