locked
2008 R2 Update Client fails to detect new updates without error RRS feed

  • Question

  • OS: Windows 2008 R2 Standard SP1 x64

    Update source: WSUS

    Symptom: Server reports it successfully found 0 updates in log without error despite there being approved updates needed by the client.

    Before anyone links to any number of people that have had similar issues -- I've tried just about everything short of rebuilding the OS which should not be necessary to detect updates.

    I've tried:


    1. Doing a soft reset of the wuauclt by deleting the contents of SoftwareDistribution and deleting browsing data.

    2. Doing #1 in conjunction with re-registering related DLLs, qmgr files and renaming catroot2 as described here:

    http://www.thewindowsclub.com/manually-reset-windows-update-components

    3. Deleting the computer from WSUS in conjunction with #1.

    4. Installing the Update Readiness tool and any wuauclt related patches I can find.

    5. Reapplied patch approvals.

    6. Used the Adamj script to clean and optimize the WSUS server.


    It might be worth noting that the server last detected all patches during the December patch cycle (KB4054521, KB4054518) and it still does detect Windows Malicious Software Removal Tool updates, but that's it.

    If there's something else I should try, I'm all ears.

    Here is the WindowsUpdate.log output after #2:



    2018-03-29 10:37:07:068 884 fb4 Misc ===========  Logging initialized (build: 7.6.7601.23806, tz: -0500)  ===========
    2018-03-29 10:37:07:071 884 fb4 Misc   = Process: C:\Windows\system32\svchost.exe
    2018-03-29 10:37:07:072 884 fb4 Misc   = Module: c:\windows\system32\wuaueng.dll
    2018-03-29 10:37:07:068 884 fb4 Service *************
    2018-03-29 10:37:07:073 884 fb4 Service ** START **  Service: Service startup
    2018-03-29 10:37:07:079 884 fb4 Service *********
    2018-03-29 10:37:08:016 884 fb4 Agent   * WU client version 7.6.7601.23806
    2018-03-29 10:37:08:017 884 fb4 Agent   * Base directory: C:\Windows\SoftwareDistribution
    2018-03-29 10:37:08:020 884 fb4 Agent   * Access type: No proxy
    2018-03-29 10:37:08:024 884 fb4 Agent   * Network state: Connected
    2018-03-29 10:37:10:825 884 fb4 DtaStor Default service for AU is {00000000-0000-0000-0000-000000000000}
    2018-03-29 10:37:10:872 884 fb4 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
    2018-03-29 10:37:10:958 884 fb4 Agent WARNING: Failed to read the service id for re-registration 0x80070002
    2018-03-29 10:37:11:004 884 fb4 Agent WARNING: Missing service entry in the backup data store; cleaning up
    2018-03-29 10:37:15:786 884 994 Report CWERReporter::Init succeeded
    2018-03-29 10:37:15:786 884 994 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2018-03-29 10:37:15:789 884 994 Agent   * Prerequisite roots succeeded.
    2018-03-29 10:37:15:790 884 994 Agent ***********  Agent: Initializing global settings cache  ***********
    2018-03-29 10:37:15:790 884 994 Agent   * WSUS server: http://<our WSUS server>:8530
    2018-03-29 10:37:15:790 884 994 Agent   * WSUS status server: http://<our WSUS server>:8530
    2018-03-29 10:37:15:790 884 994 Agent   * Target group: <server group>
    2018-03-29 10:37:15:790 884 994 Agent   * Windows Update access disabled: No
    2018-03-29 10:37:15:820 884 994 DnldMgr Download manager restoring 0 downloads
    2018-03-29 10:37:15:835 884 994 AU ###########  AU: Initializing Automatic Updates  ###########
    2018-03-29 10:37:15:854 884 994 AU   # WSUS server: http://<our WSUS server>:8530
    2018-03-29 10:37:15:854 884 994 AU   # Detection frequency: 22
    2018-03-29 10:37:15:854 884 994 AU   # Target group: <server group>
    2018-03-29 10:37:15:854 884 994 AU   # Approval type: Pre-install notify (Policy)
    2018-03-29 10:37:15:854 884 994 AU   # Auto-install minor updates: No (Policy)
    2018-03-29 10:37:15:949 884 fb4 Report ***********  Report: Initializing static reporting data  ***********
    2018-03-29 10:37:15:949 884 fb4 Report   * OS Version = 6.1.7601.1.0.196880
    2018-03-29 10:37:15:949 884 fb4 Report   * OS Product Type = 0x00000007
    2018-03-29 10:37:15:956 884 fb4 Report   * Computer Brand = VMware, Inc.
    2018-03-29 10:37:15:956 884 fb4 Report   * Computer Model = VMware Virtual Platform
    2018-03-29 10:37:15:957 884 fb4 Report   * Bios Revision = 6.00
    2018-03-29 10:37:15:957 884 fb4 Report   * Bios Name = PhoenixBIOS 4.0 Release 6.0     
    2018-03-29 10:37:15:957 884 fb4 Report   * Bios Release Date = 2015-09-21T00:00:00
    2018-03-29 10:37:15:957 884 fb4 Report   * Locale ID = 1033
    2018-03-29 10:37:16:068 884 994 AU Successfully wrote event for AU health state:0
    2018-03-29 10:37:16:068 884 994 AU Initializing featured updates
    2018-03-29 10:37:16:068 884 994 AU Found 0 cached featured updates
    2018-03-29 10:37:16:068 884 994 AU Successfully wrote event for AU health state:0
    2018-03-29 10:37:16:070 884 994 AU Successfully wrote event for AU health state:0
    2018-03-29 10:37:16:070 884 994 AU AU finished delayed initialization
    2018-03-29 10:37:17:347 884 994 AU Triggering AU detection through DetectNow API
    2018-03-29 10:37:17:347 884 994 AU Triggering Online detection (interactive)
    2018-03-29 10:37:17:354 884 fb4 AU #############
    2018-03-29 10:37:17:354 884 fb4 AU ## START ##  AU: Search for updates
    2018-03-29 10:37:17:354 884 fb4 AU #########
    2018-03-29 10:37:17:402 884 fb4 AU <<## SUBMITTED ## AU: Search for updates [CallId = {289A6F90-20A1-492D-BF2E-10DFEE77A398}]
    2018-03-29 10:37:17:402 884 7b0 Agent *************
    2018-03-29 10:37:17:402 884 7b0 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2018-03-29 10:37:17:409 884 7b0 Agent *********
    2018-03-29 10:37:17:409 884 7b0 Agent   * Online = Yes; Ignore download priority = No
    2018-03-29 10:37:17:409 884 7b0 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2018-03-29 10:37:17:409 884 7b0 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2018-03-29 10:37:17:409 884 7b0 Agent   * Search Scope = {Machine}
    2018-03-29 10:37:17:415 884 7b0 Setup Checking for agent SelfUpdate
    2018-03-29 10:37:17:415 884 7b0 Setup Client version: Core: 7.6.7601.23806  Aux: 7.6.7601.23806
    2018-03-29 10:37:17:615 884 7b0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2018-03-29 10:37:17:719 884 7b0 Misc Microsoft signed: NA
    2018-03-29 10:37:17:729 884 7b0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP7755.tmp with dwProvFlags 0x00000080:
    2018-03-29 10:37:17:787 884 7b0 Misc Microsoft signed: NA
    2018-03-29 10:37:17:900 884 7b0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2018-03-29 10:37:17:908 884 7b0 Misc Microsoft signed: NA
    2018-03-29 10:37:17:976 884 7b0 Setup Determining whether a new setup handler needs to be downloaded
    2018-03-29 10:37:17:976 884 7b0 Setup SelfUpdate handler is not found.  It will be downloaded
    2018-03-29 10:37:17:976 884 7b0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
    2018-03-29 10:37:20:939 884 7b0 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2018-03-29 10:37:20:939 884 7b0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2018-03-29 10:37:20:963 884 7b0 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2018-03-29 10:37:20:963 884 7b0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2018-03-29 10:37:21:014 884 7b0 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2018-03-29 10:37:21:015 884 7b0 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2018-03-29 10:37:21:326 884 7b0 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2018-03-29 10:37:21:326 884 7b0 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://<our WSUS server>/ClientWebService/client.asmx
    2018-03-29 10:37:21:442 884 7b0 PT WARNING: Cached cookie has expired or new PID is available
    2018-03-29 10:37:21:442 884 7b0 PT Initializing simple targeting cookie, clientId = 41223918-1ff2-4bf4-bc0b-0a1073036b72, target group = <server group>, DNS name = <server name>
    2018-03-29 10:37:21:442 884 7b0 PT   Server URL = http://<our WSUS server>:8530/SimpleAuthWebService/SimpleAuth.asmx


    • Edited by AK_BDBC Friday, March 30, 2018 5:53 PM
    Thursday, March 29, 2018 6:20 PM

All replies

  • Did you figure out what your issue was with this yet?

    I am seeing the EXACT same problem on two separate Server 2008 R2 Standard servers as well.

    The last time it did successful updates was back in December, and since then, they both are not able to find any newer updates since then, either if I have the clients check against WSUS or from Windows Update online.

    However, they both are seeing the March 2018 malicious software removal tool!

    I tried doing most of the steps you have too, but I just cannot get either of these clients to detect newer updates since December.

    Stumped!

    • Proposed as answer by Craig.Dovyak Thursday, April 12, 2018 5:14 PM
    • Unproposed as answer by Craig.Dovyak Thursday, April 12, 2018 5:15 PM
    Monday, April 2, 2018 3:34 PM
  • AK_BDBC,

    I finally figured out the issue for this.  The problem is around AntiVirus and the Spectre/Meltdown patches in January.

    Basically, you need the following registry key on your servers to allow Windows Updates to work past 01/2018.

    RegKey="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat"
    Value Name ="cadca5fe-87d3-4b96-b7fb-a231484277cc"
    Type="REG_DWORD"
    Data="0x00000000"

    As soon as I implemented this registry key, my problematic servers started detecting the outstanding WSUS updates.

    Give it a shot!

    • Proposed as answer by Craig.Dovyak Thursday, April 12, 2018 5:24 PM
    Thursday, April 12, 2018 5:24 PM