locked
Windows 2016 with WSUS RRS feed

  • Question

  • Clients can't connect to it.

    Now, here's what happened.  My previous WSUS (win2k12r2) crashed hard.  No recovery.  So I figured now would probably be a good time to do a clean win2k16 install.  I had hardware glitches but all seemed cool once I got it working.  Clients could get back to their shared drives easily (in fact, most didn't even notice a difference).

    But, the update history in WSUS was gone.  This is a new WSUS instance.  It installed just fine.  Set the products and classifications just fine.  Even ran the windows update on the local box.  It connected, downloaded and installed updates.

    Now the clients, all win10 pro, can't connect.  I've gone through the powershell commands of stopping the service, deleting the C:\Windows\SoftwareDistribution\* -recuse -recursive (or something like that).  And they still can't connect.

    Now, I can fire up the remote admin console for WSUS and connect to WSUS just fine to administrate it. 

    The last time it failed, I went into the C:\Windows\SoftwareDistribution and found a file called ReportingEvents.log  Here are the contents:

    {94510F55-9758-46BD-A40C-2B1B5706D2EC} 2016-11-19 01:08:02:119-0700 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
    {698B6305-B93E-49C0-B3A8-BF15BB66FEC0} 2016-11-19 01:13:15:768-0700 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.

    Also of note, The clients are all set via GPO.  It worked until the fresh install of WSUS on the fresh box.

    The Windows Update Service startup is Manual (Trigger Start) and is currently started.

    Saturday, November 19, 2016 8:30 AM

All replies

  • I stand corrected.  WSUS console now shows 1 Win10 client actually did connect.  The other ones haven't tried yet or can't (like the one I'm on now).
    Saturday, November 19, 2016 8:33 AM
  • please have a look of below article.

    http://answers.microsoft.com/en-us/windows/forum/windows_8-update/i-keep-getting-windows-update-error-0x8024401c/ccf0eac4-44ca-433d-b478-c1afe4a1078f

    Also try with WSUS ClientDiag to check the connectivity between client to server.


    Regards,
    Sandeep Poonia
    Please verify the answer if it helps you.

    Saturday, November 19, 2016 9:32 AM
  • Clean boot.  Nope.

    Clean boot with Norton uninstalled, Nope.

    This link: http://windows.microsoft.com/en-US/windows-8/windows-update-error-0x8024401c and this link: http://windows.microsoft.com/en-US/windows-8/windows-update-error-0x8024401c don't take me to what their supposed to.  Just some 'download and install windows 10' links.  Which is what I'm having a problem with.

    ClientDiag returned this:

    GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002

    The system cannot find the file specified.

    sfc /scannow was the first thing I did.

    Anything else?

    Sunday, November 20, 2016 9:50 PM
  • Hi _Michael,

    >Now the clients, all win10 pro, can't connect.

    1.  Please check if the WSUS server 2016 has patched with the latest rollup, if not, you may patch it;

    https://support.microsoft.com/en-us/help/12387/windows-10-update-history

    2. Please check if the WSUS clients report to the WSUS server recently? You may provide a screenshot of WSUS overview, it may help us check the status of the WSUS server;

    3. On WSUS clients, please try reset windows update components, check if it could help:

    https://support.microsoft.com/en-us/kb/971058

    Best Regards,

    Anne


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

    Monday, November 21, 2016 6:46 AM
  • Read my second post.  I found one client reporting when I posted that.  Today, I found all of them reporting except this one (it's running Windows 10 Anniversary update).

    https://support.microsoft.com/en-us/help/12387/windows-10-update-history just takes me to a link to download Windows 10 Anniversary update.

    https://support.microsoft.com/en-us/kb/971058 .  Now this one was interesting.  When I got the part about re-registering DLL's, I got 3 different errors across quite a few of the files.  Here's the info (error listed then the files that had that error).

    "The module <module> was loaded but the entry-point DllRegisterServer was not found.  Makre sure that <module> is a valid DLL or OCX file and then try again."
    mshtml.dll, shdocvw.dll, browseui.dll, wuaueng.dll, wuaueng1.dll, qmgr.dll

    "The module <module> failed to load.  Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.  The specified module could not be found."
    msxml.dll, gpkcsp.dll, sccbase.dll, slbcsp.dll, initpki.dll, wucltui.dll, wuweb.dll, qmgrprxy.dll, wucltux.dll, muweb.dll, wuwebv.dll

    "The module <module> was loaded but the call to DllRegisterServer failed with error code 0x80070005.  For information about this problem, search online using the error code as a search term."
    actxprxy.dll, oleaut32.dll, wups.dll, wups2.dll

    Thoughts?

    Monday, November 21, 2016 9:06 AM
  • Hi Michael,

    >Now this one was interesting.  When I got the part about re-registering DLL's, I got 3 different errors across quite a few of the files.  Here's the info (error listed then the files that had that error).

    Please run sfc /scannow on the client, check if there are corrupted or missing system files.

    Best Regards,

    Anne


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

    Monday, November 28, 2016 2:12 AM