locked
Windows 2008 R2 SP1 64-BIT node not showing KB3177467 on the windows update RRS feed

  • Question

  • Hi All,

    I have a few Windows 2008 R2 SP1 64-BIT nodes in my environment which are reporting to WSUS which is also running in the same OS. In the windowsupdate.log it seems all are reporting 2 missing patches. And all of them are only able to receive KB4471318 which keeps failing and understand that I would need to install KB3177467 as a prerequisite before KBB4471318 can be installed. 

    It appears in the WSUS and have been approve to install, but end nodes is not displaying it on the Window update. How do I make it appear via windows update.

    Thanks

    Monday, January 21, 2019 3:01 AM

Answers

  • Hi,
     
    Have you checked this?
     

     
    Best Regards,
    Ray

    Please remembers to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, January 29, 2019 9:56 AM

All replies

  • Hello,
     
    Even if clients receive KB3177467 and KB4471318 successfully, they are not smart enough to know they should install the former first. So let's focus on the KB3177467 first.
     
    1> In the WSUS console, only approve KB3177467.
    2> On the affected clients, run the following script in the elevated CMD and check the results.
     
    net stop bits
    net stop wuauserv
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f
    rd /s /q "C:\WINDOWS\SoftwareDistribution"
    net start bits
    net start wuauserv
    wuauclt /resetauthorization /detectnow
     
    3> If KB3177467 still not show up, check if the client has installed it before. 
     
    4> If KB3177467 is installed successfully, then approve KB4471318. Note that KB4471318 has been replaced by KB4480970.
     
    Hope my answer could help you and look forward to your feedback.
     
    Best Regards,
    Ray

    Please remembers to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, January 21, 2019 8:12 AM
  • Hi Ray,

    Did the following but still  KB3177467 is not appearing. and the patch is also not installed before. but the system is reporting 2 patch but only displaying KB4471318. suppose the other patch is KB3177467 as i went through the list of the patch deployed and install in the system.

    Thanks

    Tuesday, January 22, 2019 7:55 AM
  • Hello, 
     
    Have you checked in the WSUS console that the KB3177467 has a "needed" flag for the client? 
     
    Could it be an option that you manually download and install KB3177467 then install KB4471318 from WSUS?
     
    And you could upload the windowsupdate.log here for further troubleshooting.
     
    Best Regards,
    Ray

    Please remembers to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, January 22, 2019 10:06 AM
  • Hi Ray,

    as requested the log file,

    2019-01-28 09:40:25:948 556 27c4 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2019-01-28 09:40:25:948 556 27c4 Agent *********
    2019-01-28 09:40:25:948 556 27c4 Agent   * Online = Yes; Ignore download priority = No
    2019-01-28 09:40:25:948 556 27c4 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"
    2019-01-28 09:40:25:948 556 27c4 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2019-01-28 09:40:25:948 556 27c4 Agent   * Search Scope = {Machine}
    2019-01-28 09:40:25:948 556 27c4 Setup Checking for agent SelfUpdate
    2019-01-28 09:40:25:948 556 27c4 Setup Client version: Core: 7.6.7601.24085  Aux: 7.6.7601.24085
    2019-01-28 09:40:25:963 556 27c4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2019-01-28 09:40:56:538 556 27c4 Misc Microsoft signed: NA
    2019-01-28 09:40:56:538 556 27c4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPDA54.tmp with dwProvFlags 0x00000080:
    2019-01-28 09:41:23:538 556 27c4 Misc Microsoft signed: NA
    2019-01-28 09:41:23:548 556 27c4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2019-01-28 09:41:23:553 556 27c4 Misc Microsoft signed: NA
    2019-01-28 09:41:23:563 556 27c4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2019-01-28 09:41:23:573 556 27c4 Misc Microsoft signed: NA
    2019-01-28 09:41:23:593 556 27c4 Setup Determining whether a new setup handler needs to be downloaded
    2019-01-28 09:41:23:593 556 27c4 Setup SelfUpdate handler is not found.  It will be downloaded
    2019-01-28 09:41:23:593 556 27c4 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
    2019-01-28 09:41:23:888 556 27c4 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2019-01-28 09:41:23:888 556 27c4 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2019-01-28 09:41:23:923 556 27c4 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2019-01-28 09:41:23:923 556 27c4 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2019-01-28 09:41:23:963 556 27c4 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2019-01-28 09:41:23:963 556 27c4 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2019-01-28 09:41:24:128 556 27c4 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2019-01-28 09:41:24:128 556 27c4 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://CCBPTCH01SRV/ClientWebService/client.asmx
    2019-01-28 09:41:24:143 556 27c4 PT WARNING: Cached cookie has expired or new PID is available
    2019-01-28 09:41:24:143 556 27c4 PT Initializing simple targeting cookie, clientId = 421b9940-e66c-4dc4-a4d2-4789dc1c8d4c, target group = , DNS name = ccbsdassrv2a.nsrpics.local
    2019-01-28 09:41:24:143 556 27c4 PT   Server URL = http://CCBPTCH01SRV/SimpleAuthWebService/SimpleAuth.asmx
    2019-01-28 09:41:24:158 556 27c4 PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2019-01-28 09:41:24:158 556 27c4 PT WARNING: SOAP Fault: 0x00012c
    2019-01-28 09:41:24:158 556 27c4 PT WARNING:     faultstring:Fault occurred
    2019-01-28 09:41:24:158 556 27c4 PT WARNING:     ErrorCode:ConfigChanged(2)
    2019-01-28 09:41:24:158 556 27c4 PT WARNING:     Message:(null)
    2019-01-28 09:41:24:158 556 27c4 PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2019-01-28 09:41:24:158 556 27c4 PT WARNING:     ID:8922966b-6787-45b8-ab35-a8d744e067c0
    2019-01-28 09:41:24:168 556 27c4 PT WARNING: Cached cookie has expired or new PID is available
    2019-01-28 09:41:24:168 556 27c4 PT Initializing simple targeting cookie, clientId = 421b9940-e66c-4dc4-a4d2-4789dc1c8d4c, target group = , DNS name = ccbsdassrv2a.nsrpics.local
    2019-01-28 09:41:24:168 556 27c4 PT   Server URL = http://CCBPTCH01SRV/SimpleAuthWebService/SimpleAuth.asmx
    2019-01-28 09:41:44:598 556 27c4 PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2019-01-28 09:41:44:598 556 27c4 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://CCBPTCH01SRV/ClientWebService/client.asmx
    2019-01-28 09:41:44:693 556 27c4 Agent   * Added update {0C61DDD7-E452-4905-8522-7DC923F043A7}.203 to search result
    2019-01-28 09:41:44:693 556 27c4 Agent   * Added update {3DF43753-6CBF-40D1-9249-DB8009BBBC7A}.200 to search result
    2019-01-28 09:41:44:693 556 27c4 Agent   * Found 2 updates and 79 categories in search; evaluated appl. rules of 1861 out of 2899 deployed entities
    2019-01-28 09:41:44:693 556 27c4 Agent *********
    2019-01-28 09:41:44:693 556 27c4 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2019-01-28 09:41:44:693 556 27c4 Agent *************
    2019-01-28 09:41:44:698 556 4198 AU >>##  RESUMED  ## AU: Search for updates [CallId = {EC55957A-071E-4E63-8466-5A8A8F25BD03}]
    2019-01-28 09:41:44:698 556 4198 AU   # 2 updates detected
    2019-01-28 09:41:44:698 556 4198 AU #########
    2019-01-28 09:41:44:698 556 4198 AU ##  END  ##  AU: Search for updates [CallId = {EC55957A-071E-4E63-8466-5A8A8F25BD03}]
    2019-01-28 09:41:44:698 556 4198 AU #############
    2019-01-28 09:41:44:698 556 4198 AU Successfully wrote event for AU health state:0
    2019-01-28 09:41:44:698 556 4198 AU Featured notifications is disabled.
    2019-01-28 09:41:44:698 556 4198 AU AU setting next detection timeout to 2019-01-28 23:40:35
    2019-01-28 09:41:44:698 556 4198 AU Successfully wrote event for AU health state:0
    2019-01-28 09:41:44:698 556 4198 AU Successfully wrote event for AU health state:0
    2019-01-28 09:41:44:698 556 4320 AU Getting featured update notifications.  fIncludeDismissed = true
    2019-01-28 09:41:44:703 556 4320 AU No featured updates available.
    2019-01-28 09:41:49:693 556 27c4 Report REPORT EVENT: {91889A67-9827-4938-86B5-1E6F02A57F1A} 2019-01-28 09:41:44:693+0700 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 2 updates.
    2019-01-28 09:41:49:693 556 27c4 Report REPORT EVENT: {6F6CCB28-B324-4695-8F54-20465306AB3D} 2019-01-28 09:41:44:693+0700 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2019-01-28 09:44:05:353 556 4114 AU Getting featured update notifications.  fIncludeDismissed = true
    2019-01-28 09:44:05:353 556 4114 AU No featured updates available.
    2019-01-28 09:48:54:792 556 27c4 Report Uploading 2 events using cached cookie, reporting URL = http://CCBPTCH01SRV/ReportingWebService/ReportingWebService.asmx
    2019-01-28 09:48:54:797 556 27c4 Report Reporter successfully uploaded 2 events.

    Monday, January 28, 2019 7:33 AM
  • Hello,
     
    I checked the 2 updates ID and yes, they are KB3177467 and KB4471318. It would be very helpful if you could double check that you have approved KB3177467 for the corresponding group. And double check that the update file has been downloaded to the WSUS server successfully.
     
    Best Regards,
    Ray

    Please remembers to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, January 28, 2019 9:09 AM
  • Hi Ray,

    Yes, I have double checked on it. On WSUS both patches has been downloaded successfully and has been assigned to the group. But it seems to be only displaying KB4171318 in the window update which is failing due to missing patch KB3177467.

    Thanks 

    Tuesday, January 29, 2019 1:10 AM
  • Hi,
     
    Have you checked this?
     

     
    Best Regards,
    Ray

    Please remembers to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, January 29, 2019 9:56 AM
  • Hello,
     
    I noticed that you have not updated for several days. So has your issue been solved or is there any update?
     
    Feel free to feedback.
     
    Best Regards,
    Ray

    Please remembers to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, February 4, 2019 1:55 AM