locked
Windows Server 2008R2 64bit -System Update Readiness issue- endless search for update RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Recently, I can't change roles or Features of a win2008R2 server. As recommended, I downloaded the System Update readiness tool to find out if there is any missing-update package. The System Update readiness tool pops up a windows "Windows Update Standalone Installed" and hangs there forever.

    There is an error log :

    Faulting application name: TrustedInstaller.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc4b0

    Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b

    Exception code: 0xc00000fd

    Fault offset: 0x0000000000055237

    Faulting process id: 0x1794

    Faulting application start time: 0x01cb0cc41070107a

    Faulting application path: C:\Windows\servicing\TrustedInstaller.exe

    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

    Report Id: 5bd60a6e-78b7-11df-80eb-0024e87cacaf

     

    Please help...

    Thank you.

    Tuesday, June 15, 2010 10:06 PM

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote

    The text blow are copied from the email between me and Spencer S., a Windows Support Professional.

     

    The %windir%\SoftwareDistribution directory is where the Windows Update client keeps pretty much all of its information about the Windows Update/Microsoft Update/WSUS process – what update services are available, what updates are available from those services, etc. In addition, all of the updates themselves that have been downloaded from the update services are stored there temporarily.

     

    The folder can be re-downloaded from the update service. To rebuild the folder, please refer to the following steps:

    Note: Before dong these steps, we recommend that you back up the system first.

    -------------------------------------------------------------------------------------------------

    a. Click Start and click Administrative Tools. Select Services.

    b. Find Background Intelligent Transfer Service (BITS) and Windows Update service. Stop the two services.

    Note: If any of the service is set to start Automatic, set it to Manual.

    c. Restart the server.

    d. Rename the SoftwareDistribution folder to SoftwareDistribution.Old under C:\windows\.

    e. Start Windows Update and BITS services.

    -Neil
    • Marked as answer by SEED IT Monday, April 4, 2011 5:55 PM
    Monday, April 4, 2011 5:55 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Seed IT,

     

    Please perform a clean boot and run the System Update Readiness Tool again. A clean boot helps eliminate software conflicts. In order to perform a clean boot, please follow these steps.  

     

        1.  Click Start, type msconfig in the Start Search box, and then press ENTER. If you are prompted for an administrator password or for a confirmation, type the password, or click Continue.

     

        2.  On the General tab, click Selective Startup.

     

        3.  Under Selective Startup, click to clear the Load Startup Items check box.

     

        4.  Click the Services tab, click to select the Hide All Microsoft Services check box, and then click Disable All.

     

        5.  Click OK.

     

        6.  When you are prompted, click Restart.

     

        7.  After the computer starts, download and run the System Update Readiness Tool again. You can find the tool from the following KB.

    http://support.microsoft.com/kb/947821

     

    After you have finished troubleshooting, follow these steps to reset the computer to start as usual:

     

        1.  Click Start , type msconfig.exe in the Start Search box, and then press ENTER.

    If you are prompted for an administrator password or for confirmation, type your password, or click Continue.

     

        2.  On the General tab, click the Normal Startup option, and then click OK.

     

        3.  When you are prompted to restart the computer, click Restart.

     

    Regards,

    Karen Ji

     
    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by SEED IT Thursday, March 10, 2011 5:55 PM
    • Unmarked as answer by SEED IT Thursday, March 10, 2011 9:34 PM
    Wednesday, June 16, 2010 8:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Karen

    After a clean boot, the System Update Readiness Tool is still hanging there.

    Any further suggestion?

    Thank you.

    Thursday, June 17, 2010 3:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Seed IT,

     

    You can also try to use Windows server 2008 R2 installation media perform a startup repair and rename the pending.xml file. The pending.xml file stores information of failed updates. System Update Readiness Tool is one of the updates.

     

    To do so, please follow the steps below:

     

    1)      Insert Windows server 2008 R2 media and restart the computer from CD/DVD.

    2)      Choose the language. Then in the bottom left of the installation windows, click Repair the computer.

    3)      Choose CMD prompt to repair the computer.

    4)      Enter the following command to rename pending.xml file.

     

    takeown /f C:\Windows\winsxs\pending.xml

     

    cacls C:\Windows\winsxs\pending.xml /G <EnterUsernameHere>:F

     

    ren C:\Windows\winsxs\pending.xml C:\Windows\winsxs\pending.old

     

    5)      Restart the computer and run System Update Readiness Tool again.

     

    If the method above won’t work, I’m afraid you will have to perform an in-place upgrade to fix the corrupt files.

     

    To perform an in-place upgrade of Windows Server 2008 R2, follow these steps:

     

    1. Insert the Windows Server 2008 R2 installation CD/DVD, then double click to run the Setup from CD/DVD.
    1. Choose the language and click Install Now.
    1. Accept the License Agreement and Choose Upgrade.
    1. Select the same edition of Windows Server 2008 R2 that is installed on server.

    (Please make sure you have enough space in your System drive.)

     

    Regards,

    Karen Ji

    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by Karen Ji Tuesday, June 22, 2010 2:07 AM
    • Unmarked as answer by SEED IT Thursday, March 10, 2011 5:54 PM
    Friday, June 18, 2010 1:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    I have to open this thread again.

    The problem is still there.

    What I tried:

    1. In-place Upgrade. Failed at the end and restored to previous system.

    2. Rename Pending.xml after a clean boot. Failed. No Pending.xml found.

    3. Run the System Update Readiness Tool after a clean boot. Failed. The System Update Readiness Tool runs forever.

    And, I am having same error:

    error log :

     

    Faulting application name: TrustedInstaller.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc4b0

    Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b

    Exception code: 0xc00000fd

    Fault offset: 0x0000000000055237

    Faulting process id: 0x1794

    Faulting application start time: 0x01cb0cc41070107a

    Faulting application path: C:\Windows\servicing\TrustedInstaller.exe

    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

    Report Id: 5bd60a6e-78b7-11df-80eb-0024e87cacaf

    Please help.

     

    -Neil
    Thursday, March 10, 2011 9:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello, 

    I am also having this same issue on a XenServer Windows 2008R2 x64 VM.

    I am a developer, not an Administrator, so I apologize in advance for the how I magically hacked a solution for my similar issue. In the end

    My issues include Active Directory is not responding, Windows Update fails, Server Manager Features and Roles fail to load. There are also issues with some services (for example the BITS service will not shut down and gets stuck in a delayed shutdown state). Also, the resource kit NetDiag fails with "Entry Point Not Found". There is also a Windows Update icon that appears in the task bar notification area which 

    The issue was first seen when Windows updates began failing intermittently in January and then completely failed by mid February. 

    Fixes for the above issues tend to point to "run the System Update Readiness Tool", which leads me to here. So I tried shutting down all the services as recommended by Karen Ji above. Still installing the Readiness Tool either hangs on "Searching for updates on this computer", or gives me this error: "Installer encountered an error: 0x8024800c". Based on the last error I received, 0x8024800c, I was able to get it to start the install process if I set the automatic windows update service to disabled, reboot, then set it to manual and then try and install the System Update Readiness Tool, it would make some progress, but then a second wuauclt process would start up and the install would hang. I then took note of the wuauclt process that the installer spawned, and began killing off the other wuauclt processes and the installer prompted me to ask if I wanted to install KB947821, for which I clicked yes. I went through this process varying degrees of failure. During one failure, I noticed the Windows Update icon in the task bar system tray. When I hovered over it it would usually show it frozen at 0%, or sometimes some other number. But this time the percentage was changing. I did a Windows Update and it failed (after it had reached 100%). I tried a few more times and it began downloading updates. 

    After installing the updates and restarting the server, the Server Manager issue is resolved and the server is up to date now with patches/updates. After I get Active Directory running I'll get back to seeing if I can install KB947821.

    Dan.

     

    Friday, March 11, 2011 12:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello again,

    I came back a few hours later (from above post) and the System Update Readiness Tool had installed successfully. It looks like too many wuauclt processes were being created (one for the System Readiness Tool, and the other for automatic updates). 

    By the way, I tried using sfc /scannow and it completed without any errors prior to this.

    Dan.

    Friday, March 11, 2011 4:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello.

    I repeat the process again today as DWWOLFE decripted on the post above but still , no luck. The Windows Update STandalon installer still hangs there.

    I am thinking to open a ticket with Microsoft support.

    -Neil
    Friday, March 11, 2011 4:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Neil,

    Did you try running sfc /scannow? I ran into quite a few posts where that was the solution.

    Dan.

     

    Monday, March 14, 2011 9:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Dan

    I tried Sfc /scannow and it says 'Windows Resource Protection did not find any integrity violations.'

    :(

     

    Tuesday, March 15, 2011 3:19 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    The text blow are copied from the email between me and Spencer S., a Windows Support Professional.

     

    The %windir%\SoftwareDistribution directory is where the Windows Update client keeps pretty much all of its information about the Windows Update/Microsoft Update/WSUS process – what update services are available, what updates are available from those services, etc. In addition, all of the updates themselves that have been downloaded from the update services are stored there temporarily.

     

    The folder can be re-downloaded from the update service. To rebuild the folder, please refer to the following steps:

    Note: Before dong these steps, we recommend that you back up the system first.

    -------------------------------------------------------------------------------------------------

    a. Click Start and click Administrative Tools. Select Services.

    b. Find Background Intelligent Transfer Service (BITS) and Windows Update service. Stop the two services.

    Note: If any of the service is set to start Automatic, set it to Manual.

    c. Restart the server.

    d. Rename the SoftwareDistribution folder to SoftwareDistribution.Old under C:\windows\.

    e. Start Windows Update and BITS services.

    -Neil
    • Marked as answer by SEED IT Monday, April 4, 2011 5:55 PM
    Monday, April 4, 2011 5:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    <...>

    The %windir%\SoftwareDistribution directory is where the Windows Update client keeps pretty much all of its information about the Windows Update/Microsoft Update/WSUS process – what update services are available, what updates are available from those services, etc. In addition, all of the updates themselves that have been downloaded from the update services are stored there temporarily.

    <...>

    -Neil

    Monday, April 04, 2011 5:55 PM


    Apparently something corrupted in the SoftwareDistribution folder on my machine was causing wusa to hang.  Because the server is in a remote branch on a thin WAN/internet pipe I really didn't want to delete the 1.5gb folder and start from scratch, however, I walked through these steps, ran the readiness tool (Windows6.1-KB947821-v27-x64) and now Windows Update is working fine.  Thank you for posting your solution to this issue (more than two years later, it's still helping idiots like me...), I found lots of cases where people have had similar problems but they never post a fix (or at least one that actually works)...

    -brendan

    Monday, August 19, 2013 4:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have now used the above solution to successfully restore functionality on a server.

    Remarkably simple solution, easily implemented and very, very satisfying to fix. Thanks Neil.

    C-J

    Monday, September 15, 2014 2:29 PM