none
Windows 2008 R2 SP1 Fails to install on Domain Controller - ERROR_TIMEOUT at 42% RRS feed

  • Question

  • Hi All,

    I have at least 2 Windows 2008 R2  Domain Controllers that I am unable to install Windows 2008 R2 SP1 on. Running through the installation process, they proceed with the install, get to about 42% and then after sitting there for some time, seem to restart (not sure if they go past 42%).

    After the restart, they show that the Service Pack has failed and they roll back.

    After the server boots, the Error Details are given as follows:ERROR_INSTALL_FAILURE (0x80070643)

    This error does NOT appear in the Event Log - instead, Service Pack Installer logs event 9 (Service Pack 1 installation succeeded)

    System Update Rediness Tool - 6.1.7601.21645 indicates No errors detected, there is one Warning

    (w)    Unable to get system disk properties    0x0000045D    IOCTL_STORAGE_QUERY_PROPERTY    Disk Cache

    sfc /scannow finds no integrity violations

    CBS.log has consistent error between both DCs

    Something similar to this appears twice

    2013-01-03 18:54:37, Info                  CSI    00000280 Performing 1 operations; 1 are not lock/unlock and follow:
      LockComponentPath (10): flags: 0 comp: {l:16 b:a6c06ef58fe9cd015701000080033401} pathid: {l:16 b:a6c06ef58fe9cd015801000080033401} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-windows-p..g-xpsdocumentwriter_31bf3856ad364e35_6.1.7601.17514_none_80fea45979a5d3f2" pid: 380 starttime: 130016767665937500 (0x01cde98fb3929c5c)
    2013-01-03 18:54:37, Info                  CSI    00000281 Calling generic command executable (sequence 3): [129]"C:\Windows\WinSxS\amd64_microsoft-windows-p..g-xpsdocumentwriter_31bf3856ad364e35_6.1.7601.17514_none_80fea45979a5d3f2\MxdwGc.exe"
        CmdLine: [142]""C:\Windows\WinSxS\amd64_microsoft-windows-p..g-xpsdocumentwriter_31bf3856ad364e35_6.1.7601.17514_none_80fea45979a5d3f2\MxdwGc.exe" /uninstall"
    2013-01-03 18:54:37, Info                  CBS    Progress: UI message updated. Operation type: Service Pack. Stage: 1 out of 1. Percent progress: 42.
    2013-01-03 19:09:38, Info                  CBS    Startup: Timed out waiting for startup processing to complete
    2013-01-03 19:09:38, Info                  CBS    Current global progress. Current: 22, Limit: 194, ExecuteState: CbsExecuteStateResolvePending
    2013-01-03 19:09:38, Info                  CBS    Previous global progress. Current: 0, Limit: 1, ExecuteState: CbsExecuteStateStageDrivers
    2013-01-03 19:09:38, Info                  CBS    Clearing HangDetect value
    2013-01-03 19:09:38, Info                  CBS    Saved last global progress. Current: 22, Limit: 194, ExecuteState: CbsExecuteStateResolvePending
    2013-01-03 19:09:38, Info                  CBS    Setting HangDetect value to 1
    2013-01-03 19:09:38, Info                  CBS    Startup: restarting the computer to attempt to continue or recover.
    2013-01-03 19:09:39, Info                  CBS    Startup: A system shutdown was initiated while waiting for startup to complete
    2013-01-03 19:09:39, Info                  CBS    Startup: Attempting to terminate the startup thread.
    2013-01-03 19:09:39, Info                  CBS    Failed a critical portion of startup processing. [HRESULT = 0x800705b4 - ERROR_TIMEOUT]
    2013-01-03 19:09:39, Info                  CBS    Ending the TrustedInstaller main loop.
    2013-01-03 19:09:39, Info                  CBS    Starting TrustedInstaller finalization.
    2013-01-03 19:09:40, Info                  CBS    Failed to unload the COMPONENTS hive. [HRESULT = 0x80070005 - E_ACCESSDENIED]
    2013-01-03 19:13:22, Info                  CBS    Starting TrustedInstaller initialization.
    2013-01-03 19:13:22, Info                  CBS    Loaded Servicing Stack v6.1.7601.17592 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\cbscore.dll
    2013-01-03 19:13:24, Info                  CSI    00000001@2013/1/3:09:13:24.265 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fefb1ef0ad @0x7fefb719849 @0x7fefb6e34e3 @0xffc8e97c @0xffc8d799 @0xffc8db2f)
    2013-01-03 19:13:24, Info                  CBS    Could not load SrClient DLL from path: SrClient.dll.  Continuing without system restore points.
    2013-01-03 19:13:24, Info                  CSI    00000002@2013/1/3:09:13:24.531 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fefb1ef0ad @0x7fefb766816 @0x7fefb732aac @0x7fefb6e35b9 @0xffc8e97c @0xffc8d799)
    2013-01-03 19:13:24, Info                  CSI    00000003@2013/1/3:09:13:24.687 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fefb1ef0ad @0x7fefaf98738 @0x7fefaf98866 @0xffc8e474 @0xffc8d7de @0xffc8db2f)
    2013-01-03 19:13:24, Info                  CBS    Ending TrustedInstaller initialization.
    

    then this

    2013-01-03 19:33:54, Info                  CBS    Startup: Waiting for SC autostart event
    2013-01-03 19:33:54, Info                  CBS    Startup: BlockTime: 10800000ms, BlockTimeIncrement: 900000ms
    2013-01-03 19:33:54, Info                  CBS    Startup: Changing logon timeout to a static timeout: 10800000
    2013-01-03 19:35:31, Info                  CBS    Startup: SC autostart event signaled
    2013-01-03 19:35:31, Info                  CBS    Clearing HangDetect value
    2013-01-03 19:35:31, Error                 CBS    Startup: A possible hang was detected on the last boot. [HRESULT = 0x800705b4 - ERROR_TIMEOUT]
    2013-01-03 19:35:31, Info                  CBS    Current global progress. Current: 22, Limit: 194, ExecuteState: CbsExecuteStateResolvePending
    2013-01-03 19:35:31, Info                  CBS    Previous global progress. Current: 22, Limit: 194, ExecuteState: CbsExecuteStateResolvePending
    2013-01-03 19:35:31, Error                 CBS    Startup: No progress detected while needing to process the advanced operation queue, rolling back and cancelling the transaction. [HRESULT = 0x80004005 - E_FAIL]
    2013-01-03 19:35:31, Info                  CBS    Setting ExecuteState key to: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed
    2013-01-03 19:35:31, Info                  CBS    Progress: UI message updated. Operation type: Service Pack. Stage: 1 out of 1. Rollback.
    2013-01-03 19:35:35, Info                  CSI    00000005 Rolling back transactions...
    
    

    Attempting to run the command line immediately preceeding the "hang" results in this (no reboot is initiated)

    "C:\Windows\WinSxS\amd64_microsoft-windows-p..g-xpsdocumentwriter_31bf3856ad364e35_6.1.7601.17514_none_80fea45979a5d3f2\MxdwGc.exe" /uninstall"
    C:\Windows\WinSxS\amd64_microsoft-windows-p..g-xpsdocumentwriter_31bf3856ad364e35_6.1.7601.17514_none_80fea45979a5d3f2\MxdwGc.exe
    MxdwGc.exe: CCommandOptions::ParseCommandLine(): Uninstall MXDW Print Queue.
    MxdwGc.exe: IsSpoolerRunning(): The SPOOLER is Running.
    MxdwGc.exe: IsMxdwPrintDriverInstalled(): The MXDW Print Driver is installed.
    MxdwGc.exe: IsMxdwPrintQueueInstalled(): The MXDW Print Queue is NOT INSTALLED.
    MxdwGc.exe: iRtnVal=0

    Other software on these domain controllers includes Quest Change Auditor and Symantec Antivirus - though these are on many other DCs that we have successfully installed deployed SP1 to.

    Grateful for any ideas on how to proceed here, we might have quite a few DCs with this problem (I haven't checked them all yet) and I don't want to rebuild so many machines.

    Kind Regards,

    Shane Wright

    Thursday, January 3, 2013 6:14 PM

Answers

  • I ended up raising a Premier case for this issue to get it resolved.

    The solution was to modify the registry value BlockTimeIncrement in the Key HKLM\System\CurrentControlSet\Services\TrustedInstaller.

    Increasing this value from 384 (15 Minutes) to 2a30 (3 hours) gave it enough time to wait for whichever component was hanging the install.

    See this thread http://social.technet.microsoft.com/Forums/en-US/dataprotectionmanager/thread/e67497ca-e638-4868-a020-a90175e19fa9.

    Thank you all for your help,

    Shane

    Thursday, May 2, 2013 3:28 PM

All replies

  • This issue might be related to corrupt .NET installation. Try uninstalling and reinstalling the .NET Framework. To do this follow these steps:

    1. Visit the following blog post:
      .NET Framework Cleanup Tool User's Guide
            (http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx)   
    2. Download dotnetfx_cleanup_tool.zip from the following site:
      http://blogs.msdn.com/cfs-file.ashx/__key/CommunityServer-Components-PostAttachments/00-08-90-44-93/dotnetfx_5F00_cleanup_5F00_tool.zip
            (http://blogs.msdn.com/cfs-file.ashx/__key/CommunityServer-Components-PostAttachments/00-08-90-44-93/dotnetfx_5F00_cleanup_5F00_tool.zip)   
    3. When you are prompted, click Open, and then click Extract Now.
    4. In the files that you extracted, double-click cleanup_tool.exe.
      If you are prompted for an administrator password or for confirmation, provide the password, and then click Continue.
    5. In the Do you want to run the .NET Framework Setup Cleanup Utility? message, click Yes.
      Note This tool may be in English only, but it also works for other language versions of Windows.
    6. Click Yes to accept the license agreement.
    7. In the Product to cleanup window, click the list, select .NET Framework - All Versions, and then click Cleanup Now.
      Note The cleanup tool does not let you remove the .NET Framework 2.0 in Windows Vista or later versions of Windows because the .NET Framework is installed as an operating system component.
    8. After the .NET Framework is removed, restart the computer.
    9. Download and install the following components:
      .NET Framework 1.1
      Microsoft .NET Framework Version 1.1 Redistributable Package
            (http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3)   
      .NET Framework 1.1 Service Pack 1 (SP1)
      Microsoft .NET Framework 1.1 Service Pack 1
            (http://www.microsoft.com/downloads/details.aspx?familyid=A8F5654F-088E-40B2-BBDB-A83353618B38)   
      .NET Framework 3.5 SP1 (this will also install the .NET Framework 2.0 SP2 and the .NET Framework 3.0 SP2)
      Microsoft .NET Framework 3.5 Service Pack 1
            (http://www.microsoft.com/downloads/details.aspx?familyid=AB99342F-5D1A-413D-8319-81DA479AB0D7)   
    10. Restart the computer.
    11. Visit Windows Update again, and then check for and install updates.


    ...

    Thursday, January 3, 2013 6:47 PM
  • Thanks Marius,

    I will give that a go. Is there anything indicating that as the cause, or is this a known issue?

    Cheers!

    Shane

    Thursday, January 3, 2013 6:50 PM
  • Well, based on the "symptoms" described I would think the issue is related to the net framework, and I remember having the same issue some time ago and I managed to resolve it using the tool described above. You can also have a look on these links and see if they might provide additional useful information:

    http://support.microsoft.com/kb/976982 - Error codes “0x80070643” or “0x643” occur when you install the .NET Framework updates

    http://support.microsoft.com/kb/906602 - Troubleshoot common installation issues in Windows Update, Microsoft Update, and Windows Server Update Services

    http://blogs.msdn.com/b/varungupta/archive/2010/06/22/troubleshooting-net-framework-4-install-failures.aspx - Troubleshooting .NET Framework 4 Install failures

    Hope the info helps.


    ...

    Thursday, January 3, 2013 7:05 PM
  • Hi,
     
    As this thread has been quiet for a while, we will mark it as ‘Answered’ as the information provided should be helpful. If you need further help, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.
      
    BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.
      
    Best Regards
      
    Kevin
    Thursday, January 10, 2013 3:27 AM
  • Thanks Kevin,

    I will update the thread when I have tried Marius's suggested process.

    Cheers!

    Shane

    Thursday, January 10, 2013 1:36 PM
  • Finally got to try this process, unfortunately it didn't work.

    Although now the Installation gets to 43% it still seems to be hanging after the same command:

    "C:\Windows\WinSxS\amd64_microsoft-windows-p..g-xpsdocumentwriter_31bf3856ad364e35_6.1.7601.17514_none_80fea45979a5d3f2\MxdwGc.exe" /uninstall

    This command runs successfully on all DC's with the issue. I will see if I can restore one of the servers into a test environment to work on it more actively, and update the thread if I find a solution.

    Cheers!

    Shane

    Thursday, February 14, 2013 9:02 PM
  • I ended up raising a Premier case for this issue to get it resolved.

    The solution was to modify the registry value BlockTimeIncrement in the Key HKLM\System\CurrentControlSet\Services\TrustedInstaller.

    Increasing this value from 384 (15 Minutes) to 2a30 (3 hours) gave it enough time to wait for whichever component was hanging the install.

    See this thread http://social.technet.microsoft.com/Forums/en-US/dataprotectionmanager/thread/e67497ca-e638-4868-a020-a90175e19fa9.

    Thank you all for your help,

    Shane

    Thursday, May 2, 2013 3:28 PM
  • Shane, I've been noticing a Windows 7 system that reboots after about 15 minutes in the CBS logs when it is stuck at 32% installing patches.  It does this 3 times, then goes to Failure and Reverting changes.  The CBS logs say there is timeout happening.  I'm hoping this will fix my issue too.

    Update: It fixed my issue.  Thank you so much for posting this.

    Sunday, October 22, 2017 7:34 AM