none
How to prompt Windows XP to check for updates

    Question

  • In Windows 7, you can click "Check for Updates".

    In Windows XP, I guess you need to run wuauclt /detectnow

    WSUS shows an XP machines has 36 needed updates, and C:\Windows\WindowsUpdate.log shows the machine is connecting to the WSUS okay. 

    On the XP machine, I did the following:

    • Turned the Automatic Updates service off.
    • Deleted contents of C:\Windows\SoftwareDistribution
    • Turned Automatic Updates on.
    • Deleted the browser cache.
    • Ran gpupdate /force
    • Rebooted
    • Logged back in, and run wuauclt /detectnow

    This is the appendment to the WindowsUpdate log:

    AU    Triggering AU detection through DetectNow API
    AU    Triggering Online detection (non-interactive)
    AU    #############
    AU    ## START ##  AU: Search for updates
    AU    #########
    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {5440DDD7-1870-43A3-8F63-F27EC562AF3F}]
    Agent    *************
    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    Agent    *********
    Agent      * Online = Yes; Ignore download priority = No
    Agent      * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    Agent      * Search Scope = {Machine}
    Misc    Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    Misc     Microsoft signed: Yes
    Misc    Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
    Misc     Microsoft signed: Yes
    Setup    ***********  Setup: Checking whether self-update is required  ***********
    Setup      * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
    Setup    Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    Setup    Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    Setup    Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    Setup    Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.4.7600.226, required version = 7.4.7600.226
    Setup    Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.4.7600.226, required version = 7.4.7600.226
    Setup    Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    Setup    Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    Setup    Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    Setup    Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    Setup    Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    Setup    Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    Setup    Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    Setup    Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    Setup      * IsUpdateRequired = No
    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://welprint:8530/ClientWebService/client.asmx

    Why is there no mention of the 36 available updates?

    (welprint:8530 is the correct WSUS server, and another Win 7 machine has already updated itself completely through WSUS)

    Thanks.

    Thursday, August 18, 2011 8:16 AM

Answers

  • Yes, I'm sure.

    The solution was to download a new WU client.

    • Marked as answer by SRD75 Wednesday, August 24, 2011 7:09 AM
    Wednesday, August 24, 2011 7:09 AM

All replies

  • That does not appear to be the end of the log file.  It is checking into the correct server, but has not finished processing the /detectnow.
    If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer".

    Rich Prescott | MCITP, MCTS, MCP

    Blog | Twitter: @Arposh | Powershell Client System Administration tool
    Thursday, August 18, 2011 1:00 PM
  • In Windows XP, I guess you need to run wuauclt /detectnow

    Correct.

    Based on your last couple of posts, I'd like to suggest that you may find some benefit from reviewing these two document sets:

    Update Management - an overview of the Microsoft philosphy and methodologies for patch management in the Windows environment.

    WSUS Operations Guide - a how-to for implementing WSUS and using the WSUS administration console.

    Why is there no mention of the 36 available updates?

    Aside from Rich's observation that your logfile is incomplete -- and a complete event would make diagnostics a whole bunch easier, not to mention more accurate -- based on your verbal description of the scenario:

    • Windows 7 systems are updating correctly
    • This Windows XP system is detecting and reporting correctly
    • This Windows XP system is not downloading/installing updates

    I'd be inclined to think that this is a classic example (discussed here weekly, almost, it seems) of one of two scenarios:

    • The update content for these Windows XP updates are not yet downloaded to the WSUS server.

    OR

    One of these related causes:

    • The updates for this Windows XP system are not approved.
    • The updates for this Windows XP system are not approved for the correct groups.
    • This Windows XP system is not assigned to the correct group(s) and thus is not getting the intended approvals.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com

    Thursday, August 18, 2011 1:10 PM
    Moderator
  • Although it does not appear to be the end of the log file, it is.

    The last line above is literally the last line of the log file.  Cheers.

    Friday, August 19, 2011 2:51 AM
  • Although it does not appear to be the end of the log file, it is.

    The last line above is literally the last line of the log file.  Cheers.


    Hi there,

    Are you sure you're looking at the correct file? I spotted on many old XP machines two logs from Windows Update, both located on "C:\Windows\" folder.

    An older one (not in use any more) called "Windows Update.log" and the newer (currently in use by the Windows Update Client) named "WindowsUpdate.log".

    It happened once to me, to be looking into the wrong file, wasting my time and brain cells away...

    Best Regards,

    Tiago Viana

    Friday, August 19, 2011 10:18 AM
  • Yes, I'm sure.

    The solution was to download a new WU client.

    • Marked as answer by SRD75 Wednesday, August 24, 2011 7:09 AM
    Wednesday, August 24, 2011 7:09 AM
  • Yes, I'm sure.

    The solution was to download a new WU client.


    The machine already had the latest WUAgent!

    Setup    Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.4.7600.226, required version = 7.4.7600.226

    There is more to this story than has been shared, and its likely that missing information would have shed light on the actual defect this machine was experiencing. If reinstallation of the WUAgent resolved that issue, it suggests that the existing installation was corrupted somehow.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com

    Wednesday, August 24, 2011 3:10 PM
    Moderator
  • It makes sense that the WU agent could of been corrupted.

    What information is missing?


    Wednesday, August 24, 2011 3:19 PM
  • What information is missing?


    1. The history of this Windows XP machine -- was it a new install? how was SP3 installed? was the machine ever actually working as a WSUS client?

    2. The logfiles before the first time you trashed the SoftwareDistribution folder -- which, btw, is a high-probability source for the cause of your dysfunctional WUAgent -- to identify the real reason the machine was allegedly not detecting/downloading originally.

    3. Confirmation of configuration settings for the WindowsUpdateAgent.

    4. Confirmation that the Automatic Updates service was actually running at the time the logfile terminated.

    5. A complete set of log entries for a current detection event -- unedited. It's not impossible that the end of the logfile which you posted was actually evidence that the WUAgent was still working -- recaching the thousands of updates in the DataStore that were lost when you unnecessarily (and prematurely) trashed the SoftwareDistribution folder. I think Rich actually hit the nail on the head when he wrote "...but has not finished processing the /detectnow."

    In essense, working with us since you did ask for help, and providing the answers and information requested in response to your request for help, responding to the active conversation in a timely manner rather than going incommunicado for five days and then informing us you reinstalled the WUAgent.

    All, of which, has no matter now, since you've ostensibly repaired the issue by reinstalling the WUAgent, despite the complete lack of evidence that anything was ever wrong with the system in the first place.

    I'm happy that you have a working system; I'm annoyed that you wasted a lot of people's time in this conversation.

     

     


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Wednesday, August 24, 2011 5:30 PM
    Moderator
  • Well strike me down.

    Forgive me if the answers have not been provided to your highness if the questions have never been asked before.

    Get over yourself.

    Thursday, August 25, 2011 12:35 AM
  • You can try this out..

    net stop wuauserv
    net start wuauserv
    wuauclt.exe /resetauthorization /detectnow

    Thursday, August 25, 2011 1:32 PM
  • Forgive me if the answers have not been provided to your highness if the questions have never been asked before.

    Some of the question were asked (and are still unanswered); some of them would have been asked had you returned to this thread at anytime since your original post and responded to the original questions and engaged in a conversation pursuant to your request for help.

    If you post in a forum asking for help, at least offer the courtesy of monitoring that thread, responding to posts in a timely manner and NOT going off engaging in rogue actions which will compromise the efforts of those you have requested help from, or worse, completely waste their time.

     


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Thursday, August 25, 2011 3:24 PM
    Moderator