locked
2012R2 server windows update does not update from Microsoft, although works with WSUS RRS feed

  • Question

  • I am trying to track down odd behavior with Windows Update on 2012R2 clients: behavior is other than expected.

    1) If I hit start (enter) and type "Windows Update", then select the Windows Update widget, I get a "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item." This dialogue box has hte caption "c:\users\Administrator\AppData\Local\Packages\Windows.immersivecont..."


    2) If instead, I hit start (enter) and type "Windows Update" & hit enter (to search), I can open the windows update widget from "Check for updates" and  the widget works properly against my WSUS server (2008R2 with many, many patches). 

    2b) If I then attempt to scan for updates against Microsoft updates, I get error code 8024500C. (if I reset the UseWUServer registry key from 1 (use WSUS) to 0, I can scan: However, my 2008R2 clients can use either with this configuration)


    I think the logs as follows are what I get during this time (eg: the failure from MS update: from the systemroot/windowslog file) ...

    2016-10-27      11:34:35:163   796     13c8    Agent   *************

    2016-10-27      11:34:35:163   796     13c8    Agent   ** START **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 20]

    2016-10-27      11:34:35:163   796     13c8    Agent   *********

    2016-10-27      11:34:35:163   796     13c8    Agent     * Online = Yes; Ignore download priority = No

    2016-10-27      11:34:35:163   796     13c8    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"

    2016-10-27      11:34:35:163   796     13c8    Agent     * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update

    2016-10-27      11:34:35:163   796     13c8    Agent     * Search Scope = {Machine & All Users}

    2016-10-27      11:34:35:163   796     13c8    Agent     * Caller SID for Applicability: S-1-5-21-124603586-1994988818-2211796862-1341

    2016-10-27      11:34:35:163   796     13c8    Agent     * RegisterService is set

    2016-10-27      11:34:35:163   796     13c8    EP        FATAL: EP: CSLSEndpointProvider::GetWUClientData - failed to get SLS data, error = 0x8024500C

    2016-10-27      11:34:35:163   796     13c8    EP        FATAL: EP: CSLSEndpointProvider::GetEndpointFromSLS - Failed to get client data, error = 0x8024500C

    2016-10-27      11:34:35:163   796     13c8    EP        FATAL: Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL, error = 0x8024500C

    2016-10-27      11:34:35:163   796     13c8    PT        WARNING: PTError: 0x8024500c

    2016-10-27      11:34:35:163   796     13c8    PT        WARNING: Initialization failed for Protocol Talker Context: 0x8024500c

    2016-10-27      11:34:35:163   796     13c8    Agent     * WARNING: Exit code = 0x8024500C

    2016-10-27      11:34:35:163   796     13c8    Agent   *********

    2016-10-27      11:34:35:163   796     13c8    Agent   **  END  **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 20]



    This behavior is .. not expected, as we expect to be able to check against both WSUS and Microsoft directly.


    The GPO settings for WSUS are as follows:

    allow automatic updates immediate installation: enabled

    Allow non-administrator to receive update notifications: Enabled

    Automat Updates detection frequency:1 hour

    configure automatic updating 3- auto download and notify for install

    set the intranet update service for detecting updates: http://wsusserver.my.domain

    set the intranet statistics server: http://wsusserver.my.domain.

    Suggestions appreciated.


    Thursday, October 27, 2016 5:39 PM

Answers

  • The Not updating from MS bit has been resolved: I was unaware that the DoNotConnectToWindowsUpdateInternetLocations key was set to disallow direct updates from MS (under  HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate ) 
    Thursday, October 27, 2016 6:43 PM

All replies

  • The Not updating from MS bit has been resolved: I was unaware that the DoNotConnectToWindowsUpdateInternetLocations key was set to disallow direct updates from MS (under  HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate ) 
    Thursday, October 27, 2016 6:43 PM
  • Hi am2o,

    Glad to see you have found the cause of the issue and thanks for sharing the information with us. If you have no other issues, you may mark your reply as answer, if you still have other issues, feel free to feed back.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, October 28, 2016 6:53 AM