Clients on WSUS not Updating

[aymenz]

Hi Guys,

 

I am new here and had already tried many solutions in KBs from Microsoft as well as solutions posted here, none worked for me so far.

 

I am receiving the following error messages in the WindowsUpdate.log

 

2012-10-12 12:18:55:160 1252 f24 Service ** START ** Service: Service startup

2012-10-12 12:18:55:254 1252 f24 Service *********

2012-10-12 12:18:55:363 1252 f24 Agent * WU client version 7.6.7600.256

2012-10-12 12:18:55:395 1252 f24 Agent * Base directory: C:\Windows\SoftwareDistribution

2012-10-12 12:18:55:473 1252 f24 Agent * Access type: No proxy

2012-10-12 12:18:55:551 1252 f24 Agent * Network state: Connected

2012-10-12 12:19:26:556 1252 824 Report CWERReporter::Init succeeded

2012-10-12 12:19:26:556 1252 824 Agent *********** Agent: Initializing Windows Update Agent ***********

2012-10-12 12:19:26:556 1252 824 Agent *********** Agent: Initializing global settings cache ***********

2012-10-12 12:19:26:556 1252 824 Agent * WSUS server: http://servername:8530/

2012-10-12 12:19:26:556 1252 824 Agent * WSUS status server: http://servername:8530/

2012-10-12 12:19:26:556 1252 824 Agent * Target group: Workstations

2012-10-12 12:19:26:556 1252 824 Agent * Windows Update access disabled: No

2012-10-12 12:19:26:587 1252 824 DnldMgr Download manager restoring 0 downloads

2012-10-12 12:19:26:712 1252 f24 Report *********** Report: Initializing static reporting data ***********

2012-10-12 12:19:26:712 1252 f24 Report * OS Version = 6.0.6002.2.0.65792

2012-10-12 12:19:26:712 1252 f24 Report * OS Product Type = 0x00000006

2012-10-12 12:19:26:743 1252 f24 Report * Computer Brand = Hewlett-Packard

2012-10-12 12:19:26:743 1252 f24 Report * Computer Model = HP Compaq 8510p

2012-10-12 12:19:26:743 1252 f24 Report * Bios Revision = 68MVD Ver. F.0F

2012-10-12 12:19:26:743 1252 f24 Report * Bios Name = KBC Version 71.36

2012-10-12 12:19:26:743 1252 f24 Report * Bios Release Date = 2008-02-05T00:00:00

2012-10-12 12:19:26:743 1252 f24 Report * Locale ID = 3081

2012-10-12 12:19:31:867 1252 e54 Report CWERReporter finishing event handling. (00000000)

2012-10-12 12:19:41:567 1252 f24 AU ########### AU: Initializing Automatic Updates ###########

2012-10-12 12:19:41:676 1252 f24 AU # WSUS server: http://servername:8530/

2012-10-12 12:19:41:676 1252 f24 AU # Detection frequency: 22

2012-10-12 12:19:41:676 1252 f24 AU # Target group: Workstations

2012-10-12 12:19:41:676 1252 f24 AU # Approval type: Scheduled (Policy)

2012-10-12 12:19:41:676 1252 f24 AU # Scheduled install day/time: Every day at 4:00

2012-10-12 12:19:41:676 1252 f24 AU # Auto-install minor updates: Yes (User preference)

2012-10-12 12:19:41:707 1252 f24 AU Setting AU scheduled install time to 2012-10-12 17:00:00

2012-10-12 12:19:41:707 1252 f24 AU Initializing featured updates

2012-10-12 12:19:41:707 1252 f24 AU Found 0 cached featured updates

2012-10-12 12:19:41:723 1252 f24 AU AU finished delayed initialization

2012-10-12 12:26:44:069 2120 168c Misc =========== Logging initialized (build: 7.6.7600.256, tz: +1100) ===========

2012-10-12 12:26:44:069 2120 168c Misc = Process: c:\Program Files\Microsoft Security Client\MpCmdRun.exe

2012-10-12 12:26:44:069 2120 168c Misc = Module: C:\Windows\system32\wuapi.dll

2012-10-12 12:26:44:069 2120 168c COMAPI -------------

2012-10-12 12:26:44:069 2120 168c COMAPI -- START -- COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]

2012-10-12 12:26:44:069 2120 168c COMAPI ---------

2012-10-12 12:26:44:084 1252 e54 Agent *************

2012-10-12 12:26:44:084 2120 168c COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]

2012-10-12 12:26:44:084 1252 e54 Agent ** START ** Agent: Finding updates [CallerId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]

2012-10-12 12:26:44:084 1252 e54 Agent *********

2012-10-12 12:26:44:084 1252 e54 Agent * Online = Yes; Ignore download priority = No

2012-10-12 12:26:44:084 1252 e54 Agent * Criteria = "(IsInstalled = 0 and IsHidden = 0 and CategoryIDs contains '6b9e8b26-8f50-44b9-94c6-7846084383ec' and CategoryIDs contains 'e0789628-ce08-4437-be74-2495b842f43b')"

2012-10-12 12:26:44:084 1252 e54 Agent * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service

2012-10-12 12:26:44:084 1252 e54 Agent * Search Scope = {Machine}

2012-10-12 12:26:44:115 1252 e54 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:

2012-10-12 12:26:44:256 1252 e54 Misc Microsoft signed: Yes

2012-10-12 12:26:46:847 1252 e54 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194

2012-10-12 12:26:46:847 1252 e54 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194

2012-10-12 12:26:46:847 1252 e54 Misc WARNING: DownloadFileInternal failed for http://download.windowsupdate.com/v9/1/windowsupdate/redir/muv4wuredir.cab: error 0x80190194

2012-10-12 12:26:46:847 1252 e54 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:

2012-10-12 12:26:46:847 1252 e54 Misc Microsoft signed: Yes

2012-10-12 12:26:49:562 1252 e54 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194

2012-10-12 12:26:49:562 1252 e54 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194

2012-10-12 12:26:49:562 1252 e54 Misc WARNING: DownloadFileInternal failed for http://download.microsoft.com/v9/1/windowsupdate/redir/muv4wuredir.cab: error 0x80190194

2012-10-12 12:26:49:562 1252 e54 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:

2012-10-12 12:26:49:562 1252 e54 Misc Microsoft signed: Yes

2012-10-12 12:26:52:543 1252 e54 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:

2012-10-12 12:26:52:543 1252 e54 Misc Microsoft signed: Yes

 

-------------------------------------------

 

Errors are highlighted in red

 

I have tried the fix it in both normal and aggressive mode on one of the client machines which is used for testing...

The machine was throwing an error when running automatic updates, followed an article about deleting the Softwaredistribution subs, then running fix it, done that now it is running the update without an error but always displaying "Up to Date"

 

I have approved a couple of Updates from WSUS, to no avail...

 

Also tried various things like editing the permissions of both the Defaut and WSUS admin pages in IIS, granting Network Services and Admin full control, made sure that Anonymous is also Enables,

 

Here some of things I have attempted so far:

http://www.edugeek.net/forums/windows-server-2000-2003/57672-wsus-3-1-computers-not-reporting.html

The Microsoft Windows Server Update Services (WSUS) SelfUpdate service does not send automatic updates

Windows Update Fails; Mr Fixit doesn't fix it -- what now???? (Network Steve Forum)

WSUS Clients Failing with Error 0x80244019 After Installing WSUS SP1 - Random Musings of Jeremy Jameson - Site Home - MSDN Blogs

 

Your help and suggestions are much appreciated...

 

Thx

[Michael]

You could try the Readiness Tool. This fixes all kinds of problems related to Windows Update.

 

The error 0x80190194 points to something wrong with your Virtual Directory. This would make sense hence no client(s) are updating. It's your server at fault. I presume clicking the link to Windows/Microsoft Update still works (from Control Panel) and that the problem's only when clicking the link to updates provided by your local WSUS install?

[aymenz]

Hi Michael,

 

That is exactly right, when clicking the WSUS update it comes up with Windows is up to date, if I check through windows update online it returns some updates...

Do I need to run the readiness tool on the server running WSUS..

 

What should I do with the virtual directory?

[Michael]

It's difficult to say, as the site and Virtual Directory are created by WSUS setup. By uninstalling WSUS, but keeping the database and its files, then re-installing should fix the Virtual Directory problems. You will need several restarts to complete this.

 

There is a 2008 R2 version of the Readiness Tool and it can and does fix problems. I'm not convinced it'll fix a Virtual Directory problem however

[aymenz]

Hi Michael,

 

Uninstalled WSUS, downloaded updates, and log files.

Re-installed WSUS and configured it to use a custom page on 8035, this was from a downloaded WSUS 3 sp2 file not as a server role.... does it make any difference.

 

will test and let you know.

 

Thx

[aymenz]

Hi Michael,

 

All working fine mate, had to run the hotfix for WSUS 3.0 SP2, then restart for the clients to run the windows update...

 

Can confirm all good mate, thx for you support.

[Michael]

No probs