Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.

Answered Error code 0x80070643 installing Update Rollup 4-v2

  • Wednesday, October 10, 2012 7:29 PM
     
     

    I'm having trouble installing the new RU4-v2 update on my Exchange Enterprise 2010 SP2 RU4 server (running CAS/HUB on this server).  When I try to install the update via Microsoft Update I receive error 80070643, which seems to be a .NET issue.  

    If I download the installer manually, it completes the first step of "generating the native images for .NET assemblies".  Once I click next it shows stopping services, then immediately says rolling back actions.

    I tried the suggestions on this website:  http://support.microsoft.com/kb/KB976982 and they did not help.


    This update installed just fine on four servers in my test lab.  It appears that the only difference between my test lab and production is that I have Windows Management Framework 3.0 installed. (http://www.microsoft.com/en-us/download/details.aspx?id=34595)  All servers are running 2008 R2 w/ SP1.

    This update just came out today so maybe I'm jumping the gun  :-)

All Replies

  • Thursday, October 11, 2012 8:33 AM
    Moderator
     
     

    Hi ,

    Please check if the Microsoft .NET Framework NGEN v2.0.50727_x64 service is started.

    Would you post the detail error information (Error code 0x80070643<//span>) ?


    Wendy Liu

    TechNet Community Support

  • Thursday, October 11, 2012 2:57 PM
     
     

    If it helps, I received the same error installing the October 2012 "patch Tuesday" updates this morning.  "Update Rollup 7-v2 for Exchange Server 2010 Service Pack 1" (KB2756496) failed with "WindowsUpdate_80070643" and "WindowsUpdate_dt000".

    Environment:

    • Machine is Windows 7 Pro x64 bit.
    • Exchange is not running but I installed some components for development purposes.
    • Windows Management Framework 3.0 (like @thomish above).

    The Microsoft .NET Framework NGEN service is installed for v2.0.50727_X64, v2.0.50727_X86, v4.0.30319_X64, and v4.0.30319_X86.  The 2.0 services have a startup type of "Manual", while the 4.0 ones are "Automatic (delayed start)".

    Note that while the Windows Management Framework 3.0 did not show any errors on install, whenever I try to start a PowerShell x64 command shell it comes up, then dies immediately. Uninstalling and re-installing the Windows Management Framework 3.0 did not fix the PowerShell issue.

    I hope this helps.

    Dave Parker


    Dave Parker

  • Thursday, October 11, 2012 3:52 PM
     
     

    Hi ,

    Please check if the Microsoft .NET Framework NGEN v2.0.50727_x64 service is started.

    Would you post the detail error information (Error code 0x80070643<//span>) ?


    Wendy Liu

    TechNet Community Support

    Hi Wendy,

    I looked at the .net services and the  Microsoft .NET Framework NGEN v2.0.50727_x64 service was set as Disabled.  I set it to automatic and tried to start it.  When I tried to start it a pop up box came up that says:

    "The Microsoft .NET Framework NGEN v2.0.50727_X64 service on Local Computer started then stopped.  Some services stop automatically if they are not in use by other services or programs."

    I tried to install the update again and it failed with the same error.  Here is additional information about the error that I located in the Event Viewer:


    Log Name:      System
    Source:        Microsoft-Windows-WindowsUpdateClient
    Date:          10/11/2012 11:43:55 AM
    Event ID:      20
    Task Category: Windows Update Agent
    Level:         Error
    Keywords:      Failure,Installation
    User:          SYSTEM
    Computer:      *name removed*
    Description:
    Installation Failure: Windows failed to install the following update with error 0x80070643: Update Rollup 4-v2 for Exchange Server 2010 Service Pack 2 (KB2756485).
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945A8954-C147-4ACD-923F-40C45405A658}" />
        <EventID>20</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>1</Task>
        <Opcode>13</Opcode>
        <Keywords>0x8000000000000028</Keywords>
        <TimeCreated SystemTime="2012-10-11T15:43:55.480616600Z" />
        <EventRecordID>7900</EventRecordID>
        <Correlation />
        <Execution ProcessID="916" ThreadID="3092" />
        <Channel>System</Channel>
        <Computer>*name removed*</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="errorCode">0x80070643</Data>
        <Data Name="updateTitle">Update Rollup 4-v2 for Exchange Server 2010 Service Pack 2 (KB2756485)</Data>
        <Data Name="updateGuid">{7BFFFCE5-6717-4F58-8D6B-696C38B52B82}</Data>
        <Data Name="updateRevisionNumber">201</Data>
      </EventData>
    </Event>

  • Thursday, October 11, 2012 3:56 PM
     
     
    My Powershell doesn't have that issue, it opens and works just fine.  I'm curious if I uninstall WMF 3.0 if the install will work.  It could have something to do with .NET 4 though.
  • Thursday, October 11, 2012 5:07 PM
     
     

    Be warned, when I uninstalled WMF 3.0 (before re-installing it), it remove something like MSVCRT90.dll and caused at least Windows Live Messenger to fail when it tried to start. A repair install of it fixed it, but it seems like either the Windows Live installer did not properly place a dependency or the WMF 3.0 installer/uninstaller ignored it.

    Dave Parker


    Dave Parker

  • Friday, October 12, 2012 1:03 AM
     
     Answered

    I can confirm that uninstalling Windows Management Framework 3.0 (Windows6.1-KB2506143-x64) first (requires a server reboot), then applying the RU4-v2 update does allow the update to install successfully.

    Re-installing the Management Framework 3.0 after installing the RU4-v2 update was also successful (another reboot).

    Beforehand, I was not able to install the RU4-v2 to any of our Exchange servers. They all exhibited the same symptoms as Thomish has stated.

    This doesn't seem related to the fact that the Microsoft .NET Framework NGEN v2.0.50727_x64 service is set to disabled.

    All servers are Server 2008 R2 SP1 Enterprise - fully patched and updated. The previous Exchange 2010 rollup applied to the servers was the original RU4 rollup. This was installed without issue.

    Interestingly, the RU4-v2 update installed without issue to my Windows 8 (x64) management computer that has the Exchange 2010 Management console installed.

    • Marked As Answer by Thomish Friday, October 12, 2012 12:31 PM
    •  
  • Friday, October 12, 2012 12:31 PM
     
     

    Thank you Joss for confirming my suspicions! This worked for me too.  Four exchange servers, all had the same problem, uninstalling Windows Management Framework 3.0 then installing the 4-v2 update worked on all four servers.

    If you have WMF3 installed there will be three reboots for each server:
    1 to uninstall Windows Management Framework 3.0
    1 after you install Rollup 4-v2
    1 after you reinstall WMF3

    I hope this helps some other people out.  Thanks everyone for your help!

    -Tom

  • Tuesday, October 16, 2012 1:48 AM
     
     
    This is a great read. Has anyone managed to fix this problem that's using Server 2012 ?

    Weltec IT support

  • Tuesday, October 16, 2012 5:18 AM
     
     

    Windows server 2012 and Exchange 2010 isn't supported.

    In first quarter of 2013 will be Service Pack 3 for Exchange 2010 which will include feature to support Windows 2012 server

    more info about Exchange 2010 Service Pack:

    Exchange 2010 SP3 announcing

    Regards

    Remigiusz

  • Tuesday, October 16, 2012 6:54 PM
     
     

    Thanks. This was a test box that was running 2008 R2 with Exchange 2010 upgraded to Win 2012. All worked well until this rollup 4 v2 failed to apply.

    The good news is that I have used this opportunity to perform a clean install of Win 2012 and Exchange 2013 preview. It's awesome.

    Thanks again. 


    Weltec IT support

  • Thursday, October 18, 2012 3:01 PM
     
     

    Same here...

    Tried on 3 2010 Sp2 Ru4 Exchange Server - two are SBS 2011...

    Imediately Rollback.... seems again not tested...

    Wait for RU5 !!!

    Uwe


    • Edited by Ritchy059 Thursday, October 18, 2012 3:03 PM
    •  
  • Friday, October 19, 2012 3:38 PM
     
     

    Found the Problem with my Install on Two SBS2011 with Exchange 2010 SP2 and RU4-V1.
    ------------
    On my SBS 2001 there was a file in C:\USERS\DEFAULT\APPDATA\LOCAL\MICROSOFT\EXCHANGE SERVER\V14\
    named Configuration9260_100.sqm. This was Access Protected - from a earlier Windows Update, Problem, Issue.

    As a second Issue this generated a lot of Temporary Profiles names TEMPxxxx.DOMAIN in C:\USERS
    and in my Eventlog every Time a Service or User tried to Logon. Also there was many red Errors with Event-Source: User-Profile.

    After inherit the Folder/File with the Rights from the Directory above and after Reboot I was able to delete the TEMPxxx.DOMAIN Directories,

    Then I Installed the RU4-V2 as the Origin Administrator - not the SBS Administrator.
    ---------------------------------------

    Worked.

    Also my Update on a Windows 2008 R2 SP1  with Exchange 2010 Sp2 RU4 - after Disable all Services, Antivirus and so on, they Accessed Exchange.

    Uwe

  • Saturday, November 17, 2012 5:49 PM
     
     
    I see RU 5 has appeared but with a note saying not to install it. Will try removing WMI 3

    CarolChi

  • Saturday, November 17, 2012 7:44 PM
     
     

    You have to wait for RU5 because now it's not available on Microsoft Websites. 

    I think they are trying to fix RU5 :)


    Remigiusz
    ExchangeBlog

  • Saturday, November 17, 2012 7:49 PM
     
     

    Well since I have failed to install RU4 v2, I saw RU5 and then the note not to install it.

    I think I will wait. perhaps SP3 will help.

    As a good administrator I like to keep my systems fully patched, but this is nearly impossible at the moment.


    CarolChi

  • Monday, December 17, 2012 12:33 AM
     
     

    The good news is that Update Rollup 5 has been re-released as Update Rollup 5-v2. Unfortunately it suffers from the same installation issue as the v4 rollup.

    It fails after at the preparing .NET Framework stage and then rolls back the installation.

    The fix is the same as per Rollup v4. Uninstall Windows Management FrameWork 3.0, then apply the 5-v2 Rollup. You can then re-install WMF 3.0. Note: You can re-install WMF 3.0 immediately after installing the rollup without having to reboot first. This seems to work okay.