locked
Windows 7 machines not showing in WSUS (windows 2016 Server) RRS feed

  • Question

  • Dears

    My windows 7 Machines not showing in WSUS (windows 2016).

    Error showing in Logs --> "Windows Update Client failed to detect with error 0x80072ee6" 

    I tried all below but still same problem.

    1. I recreated the Software Distribution Folder and also remove the registry values same error as mentioned above.

    2. I run the SFC and DISM tools to fix the issue but same error.

    3. Below also working fine.

    Try to download the WSUS iuident CAB file from the client machine.

    http://UpdateServerName:8530/selfupdate/iuident.cab
    https://UpdateServerName:8531/selfupdate/iuident.cab

    and then try to browse to:

    http://UpdateServerName:8530/ClientWebService/client.asmx
    https://UpdateServerName:8531/ClientWebService/client.asmx

    4. Also check the ports and also in registry keys all fine.

    5. I reinstall the update server also but no luck.

    If anyone can help will be appriciated.

    Thanks and Regards


    Muhammad Faheem

    Thursday, June 13, 2019 7:31 AM

All replies

  • Hi,
      

    The error code 0x80072EE6 means that the client can't recognize the protocol. Typically this has invoked as a result of attempting to use UNC pathnames, or simple hostnames. First check if the intranet update service configured in the GPO is missing the "http://" or "https://" prefix and the port number as a suffix.
      

    If this does not solve the problem you are experiencing, please post the complete windowsupdate.log here. It may give some hints.
      

    Reply back with the results would be happy to help.
      

    Regards,
    Yic


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

    Friday, June 14, 2019 1:43 AM
  • Dear

    Thanks for the reply.

    UNC path and port is ok in GPO.

    Kindly find the below result from the log file.

    {0B4664E5-24C7-4F80-90FB-03DF7E5EBDDA} 2019-06-12 14:41:49:174+0300 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80072ee6 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee6.
    {B953A2D2-8DB2-4C57-B527-DBBD567E0E76} 2019-06-12 19:41:49:038+0300 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80072ee6 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee6.
    {979F825D-4D39-4591-A718-4CD8F91D3109} 2019-06-13 00:41:49:123+0300 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80072ee6 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee6.
    {65B47C7F-EF30-43A3-955E-6FAD5041E093} 2019-06-13 03:38:23:469+0300 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee6 Windows Defender Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee6.
    {39D2FAC4-E144-4632-BC8F-98957B4CC4E8} 2019-06-13 03:38:23:562+0300 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072f78 Windows Defender Failure Software Synchronization Windows Update Client failed to detect with error 0x80072f78.
    {C2C258FF-B869-40E5-910A-801555221300} 2019-06-13 05:41:49:136+0300 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80072ee6 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee6.
    {1D980286-90CF-4621-9470-E94723702DED} 2019-06-13 10:41:49:103+0300 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80072ee6 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee6.
    {E2F14FD6-B17C-4809-88CB-B5F194C6B066} 2019-06-13 15:41:49:088+0300 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80072ee6 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee6.
    {E38636AD-E6CA-460E-AB6B-73138A358BF0} 2019-06-16 08:50:26:197+0300 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80072ee6 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee6.
    {611577A9-050B-4C1C-A256-3A71A519B1EC} 2019-06-16 08:50:26:197+0300 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software Synchronization Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
    {24736E03-8BB9-4CB6-A3A4-CE69FB13225C} 2019-06-16 08:51:48:548+0300 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80072ee6 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee6.
    {05150BF8-DB2D-41FA-A5F8-0AF0733A967B} 2019-06-16 13:51:48:558+0300 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80072ee6 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee6.
    {2EC90480-BF92-4156-94B8-6361F228164B} 2019-06-17 08:37:51:131+0300 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80072ee6 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee6.


    Thanks and Regards


    Muhammad Faheem

    Monday, June 17, 2019 7:37 AM
  • Hi Muhammad Faheem,
       

    Maybe you have already done this, but I hope that you can check the address of the intranet server in the GPO again:
      

    1. On the client with 0x80072ee6 error, execute the following command with the enhanced CMD to generate a group policy result report:
      > gpresult /h c:/GPO.htm
      The report will be generated on this client's C drive with the file name GPO.htm.
    2. Open this report and browse to the following path:
      [Computer Details > Settings > Policies > Administrative Templates > Windows Components/Windows Update]
    3. You will see the website address set by "Set the intranet update service for detecting updates" and "Set the intranet statistics server".

      Copy this URL and in the new tab, visit the following address:
      > http://[CopyURL]/selfupdate/iuident.cab
      If the iuident.cab download prompt appears normally, this may not be the reason for Group Policy.
         

    Reply back with the results would be happy to help.
      

    Regards,
    Yic

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

    Tuesday, June 18, 2019 6:11 AM
  • Dear

    Thanks for the reply.

    I run the gpresult command and i can download the file .cab without any problem.


    Muhammad Faheem

    Tuesday, June 18, 2019 6:38 AM
  • Issue resolved by removing the FQDN from the http://FQDM:8530 and put the local IP of wsus server http://localIP:8530. After that i can see all windows 7 machines in WSUS Console.

    Thanks and Regards


    Muhammad Faheem

    Sunday, June 23, 2019 9:45 AM
  • Hi Muhammad Faheem,
      

    Good job! Nice to see you solved the problem.
    As curious, I want to know if the client directly pings the server's FQDN is smooth? This seems to be a problem with the DNS server.
      

    Looking forward to your reply.
      

    Regards,
    Yic

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

    Monday, June 24, 2019 8:54 AM
  • Dear

    I tried to ping FQDN for wsus server and working smoothly.

    Regards


    Muhammad Faheem

    Monday, June 24, 2019 9:43 AM