none
Windows 8 PCs not reporting to WSUS

    Question

  • Hello,

    I have a small network that includes Windows XP, Windows 7, and Windows 8 machines. When I look at my WSUS console, only the XP and Windows 7 machines are shown and reporting. There are no Windows 8 machines listed at all. I first read that it may have been caused by my server being behind on updates. So I checked for updates and applied new updates as needed. It still didn't have any Windows 8 machines reporting. So after some more research on Google, I saw KB2734608, so I downloaded and installed it before the weekend. I came back to work this morning only to find that no Win 8 machines are reporting. I'm going to get my hands on one this morning and check to see what server they're pulling updates from. I'm pretty sure GPO is being applied correctly, because I've gotten reports from users that "Windows failed to download updates", and it had the little foot note that said updates are managed by an administrator.

    Anything else I should check, or anything I may have over looked? Thanks for your time!

    BradenP

    Monday, January 21, 2013 1:03 PM

Answers

  • Theory:

    LG suggested "unhealthy" WSUS due to "Agent Found 0/0 evaluated 0/0"

    I suspect the "Agent Found 0/0 evaluated 0/0" was caused by the underpinning missing/unuseable auth.cab on the client, per log:
    "2013-01-21 10:32:19:571964 2540Agent WARNING: failed to access the auth cab, fatal error 0x80070003"
    "2013-01-21 10:32:19:571964 2540Agent WARNING: could not get the auth file name 0x80070002"

    Note:

    0x80070002 -2147024894 ERROR_FILE_NOT_FOUND The System cannot find the file specified
    0x80070003 -2147024893 COR_E_DIRECTORYNOTFOUND The specified path couldn't be found - ALLUSERSPROFILE Microsoft network dir doesn’t exist
    0x80070003 -2147024893 ERROR_PATH_NOT_FOUND The system cannot find the path specified.

    And it looks like that was all resolved by zapping the SoftwareDistribution folder con the client, which subsequently auto-repaired overnight.

    So I don't necessarily agree that your WSUS is unhealthy..


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)


    Wednesday, January 23, 2013 9:15 PM
  • Just opened the console and refreshed. They're reporting today.

    Sorry, I had to obscure our hostnames for security reasons.

    On a side note:

    I know the config is good, because other PCs are reporting, using the same GPO settings.

    I have no idea why this WSUS server would be unhealthy, it's a fresh install from the MS website. I only applied KB2734608 after having problems with the windows 8 machines not showing up. I initially pulled the windowsupdate.log and looked at it myself, I had no idea why they wouldn't be showing, because they appeared to be reporting their status to the server. After a bit of research, I found someone with a similar situation who had to use KB2734608.

    So, here is how I handled the KB2734608 Instructions:

    First:

    1. Start the process with WSUS 3.0 SP2 that synchronizes with Microsoft Update.
      - We only have one, it's this one.
    2. Apply this update.
      - Done.
    3. Start a synchronization.
      - Did that.
    4. Wait for the synchronization to succeed.
      - It did.
    5. Repeat steps 2 through 4 for each WSUS 3.0 SP2 server that synchronizes to the server that you just updated.
      - We only have one.

    Second:

    If you have Windows 8 or Windows Server 2012 clients that synchronized with WSUS 3SP2 before you applied this update, wait for the update to be applied to the WSUS servers, and then follow these steps:
    1. On the affected client, open cmd.exe in elevated mode
    2. Type the following commands. Make sure that you press Enter after you type each command:

      Net stop wuauserv

      rd /s %windir%\softwaredistribution\

      Net start wuauserv

    I did this, just in case they did sync before the update. (because one of the windowsupdate.log's looked as if they were.)

    Third:

    The SQL Server side notes and NLB items do not apply to this configuration. So they were skipped.


    Can you elaborate on what may be unhealthy in regards to our WSUS server?

    Thanks,

    BradenP

    Wednesday, January 23, 2013 6:55 PM
  • Theory:

    LG suggested "unhealthy" WSUS due to "Agent Found 0/0 evaluated 0/0"

    I suspect the "Agent Found 0/0 evaluated 0/0" was caused by the underpinning missing/unuseable auth.cab on the client, per log:
    "2013-01-21 10:32:19:571964 2540Agent WARNING: failed to access the auth cab, fatal error 0x80070003"
    "2013-01-21 10:32:19:571964 2540Agent WARNING: could not get the auth file name 0x80070002"

    Note:

    0x80070002 -2147024894 ERROR_FILE_NOT_FOUND The System cannot find the file specified
    0x80070003 -2147024893 COR_E_DIRECTORYNOTFOUND The specified path couldn't be found - ALLUSERSPROFILE Microsoft network dir doesn’t exist
    0x80070003 -2147024893 ERROR_PATH_NOT_FOUND The system cannot find the path specified.

    And it looks like that was all resolved by zapping the SoftwareDistribution folder con the client, which subsequently auto-repaired overnight.

    So I don't necessarily agree that your WSUS is unhealthy..

    I concur, Don. Good catch!

    I made an assumption, and perhaps erroneous, that the logfile was from the post-destruction of the SoftwareDistribution folder. If, in fact, the SoftwareDistribution folder was deleted after the logfile capture, then I agree the rebuilding of that folder likely cleared the client-side error.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, January 23, 2013 11:12 PM

All replies

  • As Win 8 were already connected to the WSUS console after you updated WSUS with KB2734608 did you update the clients as well:

    http://chapsnet.wordpress.com/2012/09/17/updating-your-wsus-for-windows-8-windows-server-2012/

    Monday, January 21, 2013 1:17 PM
  • Followed the steps as directed on one of the PCs, still not even showing in the console.

    Here is the tail of the WindowsUpdate.log from that machine:

    2013-01-21 10:21:27:460 964 32a4 Service *************
    2013-01-21 10:32:18:898 964 2540 Misc ===========  Logging initialized (build: 7.8.9200.16451, tz: -0500)  ===========
    2013-01-21 10:32:18:941 964 2540 Misc  = Process: C:\Windows\system32\svchost.exe
    2013-01-21 10:32:18:941 964 2540 Misc  = Module: c:\windows\system32\wuaueng.dll
    2013-01-21 10:32:18:898 964 2540 Service *************
    2013-01-21 10:32:18:941 964 2540 Service ** START **  Service: Service startup
    2013-01-21 10:32:18:941 964 2540 Service *********
    2013-01-21 10:32:18:946 964 2540 Agent  * WU client version 7.8.9200.16451
    2013-01-21 10:32:18:946 964 2540 Agent  * Base directory: C:\Windows\SoftwareDistribution
    2013-01-21 10:32:18:946 964 2540 Agent  * Access type: No proxy
    2013-01-21 10:32:18:946 964 2540 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
    2013-01-21 10:32:18:946 964 2540 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2013-01-21 10:32:18:994 964 2540 Agent  * Network state: Connected
    2013-01-21 10:32:19:002 964 2540 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
    2013-01-21 10:32:19:002 964 2540 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2013-01-21 10:32:19:419 964 2540 DtaStor Default service for AU is {00000000-0000-0000-0000-000000000000}
    2013-01-21 10:32:19:521 964 2540 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
    2013-01-21 10:32:19:521 964 2540 DtaStor Data store successfully created
    2013-01-21 10:32:19:522 964 2540 Agent WARNING: failed to access the auth cab, fatal error 0x80070003
    2013-01-21 10:32:19:522 964 2540 Agent WARNING: Invalid service in the backup data store; cleaning up 
    2013-01-21 10:32:19:522 964 2540 Agent WARNING: Failed to add and register service 117cab2d-82b1-4b5a-a08c-4d62dbee7782 to the data store 0x80240031
    2013-01-21 10:32:19:522 964 2540 Agent WARNING: Service Recovery: Attempting to add pending registration for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782 to the data store
    2013-01-21 10:32:19:571 964 2540 Agent WARNING: failed to access the auth cab, fatal error 0x80070003
    2013-01-21 10:32:19:571 964 2540 Agent WARNING: Invalid service in the backup data store; cleaning up 
    2013-01-21 10:32:19:571 964 2540 Agent WARNING: Failed to add and register service 7971f918-a847-4430-9279-4a52d1efe18d to the data store 0x80240031
    2013-01-21 10:32:19:571 964 2540 Agent WARNING: Service Recovery: Attempting to add pending registration for service 7971f918-a847-4430-9279-4a52d1efe18d to the data store
    2013-01-21 10:32:19:571 964 2540 Agent WARNING: could not get the auth file name 0x80070002
    2013-01-21 10:32:19:572 964 2540 Agent WARNING: Service Recovery: Attempting to add pending registration for service 7971f918-a847-4430-9279-4a52d1efe18d to the data store
    2013-01-21 10:32:19:573 964 2540 Agent ***********  Agent: Initializing global settings cache  ***********
    2013-01-21 10:32:19:573 964 2540 Agent  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2013-01-21 10:32:19:573 964 2540 Agent  * WSUS server: http://(Correct WSUS Server Name)
    2013-01-21 10:32:19:573 964 2540 Agent  * WSUS status server: http://(Correct WSUS Server Name)
    2013-01-21 10:32:19:573 964 2540 Agent  * Target group: (Unassigned Computers)
    2013-01-21 10:32:19:573 964 2540 Agent  * Windows Update access disabled: No
    2013-01-21 10:32:19:580 964 2540 WuTask WuTaskManager delay initialize completed successfully..
    2013-01-21 10:32:19:645 964 2540 Report CWERReporter::Init succeeded
    2013-01-21 10:32:19:645 964 2540 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2013-01-21 10:32:19:645 964 2540 DnldMgr Download manager restoring 0 downloads
    2013-01-21 10:32:19:696 964 2540 AU ###########  AU: Initializing Automatic Updates  ###########
    2013-01-21 10:32:19:697 964 2540 AU AIR Mode is disabled
    2013-01-21 10:32:19:697 964 2540 AU  # Policy Driven Provider: http://(Correct WSUS Server Name)
    2013-01-21 10:32:19:697 964 2540 AU  # Detection frequency: 4
    2013-01-21 10:32:19:697 964 2540 AU  # Approval type: Scheduled (Policy)
    2013-01-21 10:32:19:698 964 2540 AU  # Auto-install minor updates: Yes (Policy)
    2013-01-21 10:32:19:699 964 2540 AU AU setting reboot grace timeout to 2013-01-24 13:41:35
    2013-01-21 10:32:19:752 964 2540 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80070490
    2013-01-21 10:32:19:758 964 2540 AU AU finished delayed initialization
    2013-01-21 10:32:19:865 964 2540 AU #############
    2013-01-21 10:32:19:865 964 2540 AU ## START ##  AU: Search for updates
    2013-01-21 10:32:19:865 964 2540 AU #########
    2013-01-21 10:32:19:986 964 2540 Report ***********  Report: Initializing static reporting data  ***********
    2013-01-21 10:32:19:986 964 2540 Report  * OS Version = 6.2.9200.0.0.65792
    2013-01-21 10:32:19:986 964 2540 Report  * OS Product Type = 0x00000030
    2013-01-21 10:32:19:994 964 2540 Report  * Computer Brand = Dell Inc.
    2013-01-21 10:32:19:995 964 2540 Report  * Computer Model = XPS 12 9Q23
    2013-01-21 10:32:19:995 964 2540 Report  * Platform Role = 2
    2013-01-21 10:32:19:995 964 2540 Report  * AlwaysOn/AlwaysConnected (AOAC) = 0
    2013-01-21 10:32:20:033 964 2540 Report  * Bios Revision =
    2013-01-21 10:32:20:033 964 2540 Report  * Bios Name = 
    2013-01-21 10:32:20:033 964 2540 Report  * Bios Release Date = 
    2013-01-21 10:32:20:033 964 2540 Report  * Bios Sku Number = 
    2013-01-21 10:32:20:033 964 2540 Report  * Bios Vendor = Dell Inc.
    2013-01-21 10:32:20:033 964 2540 Report  * Bios Family =
    2013-01-21 10:32:20:033 964 2540 Report  * Bios Major Release = 
    2013-01-21 10:32:20:033 964 2540 Report  * Bios Minor Release = 
    2013-01-21 10:32:20:033 964 2540 Report  * Locale ID = 
    2013-01-21 10:32:20:037 964 2540 AU <<## SUBMITTED ## AU: Search for updates  [CallId = {CA7C91F7-36BC-4C9E-8DC9-E6AF10002450} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2013-01-21 10:32:20:037 964 3038 Agent *************
    2013-01-21 10:32:20:037 964 3038 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-01-21 10:32:20:037 964 3038 Agent *********
    2013-01-21 10:32:20:037 964 3038 Agent  * Online = No; Ignore download priority = No
    2013-01-21 10:32:20:037 964 3038 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"
    2013-01-21 10:32:20:037 964 3038 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2013-01-21 10:32:20:037 964 3038 Agent  * Search Scope = {Machine & All Users}
    2013-01-21 10:32:20:037 964 3038 Agent  * Caller SID for Applicability: S-1-5-18
    2013-01-21 10:32:20:149 964 3038 Agent  * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
    2013-01-21 10:32:20:151 964 3038 Agent *********
    2013-01-21 10:32:20:151 964 3038 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-01-21 10:32:20:151 964 3038 Agent *************
    2013-01-21 10:32:20:152 964 2270 AU >>##  RESUMED  ## AU: Search for updates [CallId = {CA7C91F7-36BC-4C9E-8DC9-E6AF10002450} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2013-01-21 10:32:20:152 964 2270 AU  # 0 updates detected
    2013-01-21 10:32:20:152 964 2270 AU #########
    2013-01-21 10:32:20:152 964 2270 AU ##  END  ##  AU: Search for updates  [CallId = {CA7C91F7-36BC-4C9E-8DC9-E6AF10002450} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2013-01-21 10:32:20:152 964 2270 AU #############
    2013-01-21 10:32:20:152 964 2270 AU All AU searches complete.
    2013-01-21 10:42:21:308 964 2540 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2013-01-21 10:42:21:374 964 2540 WuTask Uninit WU Task Manager
    2013-01-21 10:42:21:615 964 2540 Service *********
    2013-01-21 10:42:21:615 964 2540 Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2013-01-21 10:42:21:615 964 2540 Service *************

    Thanks,

    BradenP

    Monday, January 21, 2013 9:49 PM
  • I saw KB2734608, so I downloaded and installed it before the weekend. I came back to work this morning only to find that no Win 8 machines are reporting. 

    Did you also perform all of the ancillary procedures documented in KB2734608, since your Win8 systems were registered with that WSUS v3 server prior to installing KB2734608?

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Tuesday, January 22, 2013 1:58 AM
  • Maybe I worded my question incorrectly.

    The Win 8 PCs were never showing in WSUS to start with, nor are they now.

    I did follow the procedures as described in KB2734608

    "Net stop wuauserv

    rd /s %windir%\softwaredistribution\

    Net start wuauserv"

    Screenshot:

    Tuesday, January 22, 2013 1:11 PM
  • The Win 8 PCs were never showing in WSUS to start with, nor are they now.

    Then I would speculate that they are misconfigured, but that's impossible to tell from the log segment provided since you've hidden the actual URL that was configured.

    One thing is certain .. whatever the machine is talking to isn't a healthy WSUS server!

    2013-01-21 10:32:20:149 964 3038 Agent  * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities

    I did follow the procedures as described in KB2734608

    I vaguely recall there being a bit more to it than that ... some notes about server synchronizations, for sure.

    So, with regard to the -30- systems reported in the WSUS console... how many systems actually exist in your network? How many of them are Windows 8?


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Tuesday, January 22, 2013 10:34 PM
  • Just opened the console and refreshed. They're reporting today.

    Sorry, I had to obscure our hostnames for security reasons.

    On a side note:

    I know the config is good, because other PCs are reporting, using the same GPO settings.

    I have no idea why this WSUS server would be unhealthy, it's a fresh install from the MS website. I only applied KB2734608 after having problems with the windows 8 machines not showing up. I initially pulled the windowsupdate.log and looked at it myself, I had no idea why they wouldn't be showing, because they appeared to be reporting their status to the server. After a bit of research, I found someone with a similar situation who had to use KB2734608.

    So, here is how I handled the KB2734608 Instructions:

    First:

    1. Start the process with WSUS 3.0 SP2 that synchronizes with Microsoft Update.
      - We only have one, it's this one.
    2. Apply this update.
      - Done.
    3. Start a synchronization.
      - Did that.
    4. Wait for the synchronization to succeed.
      - It did.
    5. Repeat steps 2 through 4 for each WSUS 3.0 SP2 server that synchronizes to the server that you just updated.
      - We only have one.

    Second:

    If you have Windows 8 or Windows Server 2012 clients that synchronized with WSUS 3SP2 before you applied this update, wait for the update to be applied to the WSUS servers, and then follow these steps:
    1. On the affected client, open cmd.exe in elevated mode
    2. Type the following commands. Make sure that you press Enter after you type each command:

      Net stop wuauserv

      rd /s %windir%\softwaredistribution\

      Net start wuauserv

    I did this, just in case they did sync before the update. (because one of the windowsupdate.log's looked as if they were.)

    Third:

    The SQL Server side notes and NLB items do not apply to this configuration. So they were skipped.


    Can you elaborate on what may be unhealthy in regards to our WSUS server?

    Thanks,

    BradenP

    Wednesday, January 23, 2013 6:55 PM
  • Theory:

    LG suggested "unhealthy" WSUS due to "Agent Found 0/0 evaluated 0/0"

    I suspect the "Agent Found 0/0 evaluated 0/0" was caused by the underpinning missing/unuseable auth.cab on the client, per log:
    "2013-01-21 10:32:19:571964 2540Agent WARNING: failed to access the auth cab, fatal error 0x80070003"
    "2013-01-21 10:32:19:571964 2540Agent WARNING: could not get the auth file name 0x80070002"

    Note:

    0x80070002 -2147024894 ERROR_FILE_NOT_FOUND The System cannot find the file specified
    0x80070003 -2147024893 COR_E_DIRECTORYNOTFOUND The specified path couldn't be found - ALLUSERSPROFILE Microsoft network dir doesn’t exist
    0x80070003 -2147024893 ERROR_PATH_NOT_FOUND The system cannot find the path specified.

    And it looks like that was all resolved by zapping the SoftwareDistribution folder con the client, which subsequently auto-repaired overnight.

    So I don't necessarily agree that your WSUS is unhealthy..


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)


    Wednesday, January 23, 2013 9:15 PM
  • Theory:

    LG suggested "unhealthy" WSUS due to "Agent Found 0/0 evaluated 0/0"

    I suspect the "Agent Found 0/0 evaluated 0/0" was caused by the underpinning missing/unuseable auth.cab on the client, per log:
    "2013-01-21 10:32:19:571964 2540Agent WARNING: failed to access the auth cab, fatal error 0x80070003"
    "2013-01-21 10:32:19:571964 2540Agent WARNING: could not get the auth file name 0x80070002"

    Note:

    0x80070002 -2147024894 ERROR_FILE_NOT_FOUND The System cannot find the file specified
    0x80070003 -2147024893 COR_E_DIRECTORYNOTFOUND The specified path couldn't be found - ALLUSERSPROFILE Microsoft network dir doesn’t exist
    0x80070003 -2147024893 ERROR_PATH_NOT_FOUND The system cannot find the path specified.

    And it looks like that was all resolved by zapping the SoftwareDistribution folder con the client, which subsequently auto-repaired overnight.

    So I don't necessarily agree that your WSUS is unhealthy..

    I concur, Don. Good catch!

    I made an assumption, and perhaps erroneous, that the logfile was from the post-destruction of the SoftwareDistribution folder. If, in fact, the SoftwareDistribution folder was deleted after the logfile capture, then I agree the rebuilding of that folder likely cleared the client-side error.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, January 23, 2013 11:12 PM