PCs not seeing WSUS updates

Number6 · March 16, 2010

Good morning all.

Mainly Windows 7 PCs + a few XP, WSUS is running on SBS2003.

When I check on the CP all our PCs are reporting as up to date and no updates available yet if I click the "check online for updates from Microsoft Update" then there are 30+ important updates found.

WSUS itself reports that all our PCs need updates. WSUS is synchronizing, downloading and auto-approving updates.

There are no apparent errors reported anywhere, it's just that the PCs think they're up to date but they're not. I've checked that all appropriate services are running on the clients and there are no firewall issues.

What can I check next to troubleshoot this?

broc · March 16, 2010

Where your PCs 'imaged'? There are known problems with Ghost & imaging..... where all images update the same WSUS status records, easily fixed with a quick registry update & restart Windows update service. Search for SusClientId, AccountDomainSid

I would start by looking at the windows update log, on XP, in the Windows folder is a txt file called Windowsupdate which can tell you a lot about what is going on.... Not sure about Windows 7 .... but I would hazard a guess that it might be in the same place, it is on Vista.

Edited March 16, 2010 by broc

danrhodes · March 16, 2010

Yes please post a few lines from the windowsupdate txt file and we can help you out further. I've spent many hours working on windows update WSUS issues I may be able to help you out.

WSUS relies on many things to work so it could be anything at this point!

Do all your other machiens update ok?

D

danrhodes · March 16, 2010

Might be helpfull for you

How to read the Windowsupdate.log file

List Windows Update Settings

Number6 · March 16, 2010

Sorry for the delay, doing 101 other things.

All PCs appear to be out of date from the point of view of the WSUS console on the server, but at the PC it thinks it's up to date.

Here's the latest few lines from the windowsupdate log for today on one of the W7 machines:

2010-03-16 09:01:31:360 912 11c0 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2010-03-16 09:01:31:360 912 11c0 Agent * Search Scope = {Machine}
2010-03-16 09:01:31:409 912 11c0 Setup Checking for agent SelfUpdate
2010-03-16 09:01:31:409 912 11c0 Setup Client version: Core: 7.4.7600.226 Aux: 7.4.7600.226
2010-03-16 09:01:31:409 912 11c0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2010-03-16 09:01:31:415 912 11c0 Misc Microsoft signed: Yes
2010-03-16 09:01:31:426 912 11c0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2010-03-16 09:01:31:429 912 11c0 Misc Microsoft signed: Yes
2010-03-16 09:01:31:430 912 11c0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2010-03-16 09:01:31:434 912 11c0 Misc Microsoft signed: Yes
2010-03-16 09:01:31:443 912 11c0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2010-03-16 09:01:31:447 912 11c0 Misc Microsoft signed: Yes
2010-03-16 09:01:31:461 912 11c0 Setup Determining whether a new setup handler needs to be downloaded
2010-03-16 09:01:31:461 912 11c0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
2010-03-16 09:01:31:469 912 11c0 Misc Microsoft signed: Yes
2010-03-16 09:01:31:469 912 11c0 Setup SelfUpdate handler update NOT required: Current version: 7.4.7600.226, required version: 7.4.7600.226
2010-03-16 09:01:31:469 912 11c0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226"
2010-03-16 09:01:32:005 912 11c0 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226" is already installed.
2010-03-16 09:01:32:005 912 11c0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226"
2010-03-16 09:01:32:025 912 11c0 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226" is already installed.
2010-03-16 09:01:32:026 912 11c0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226"
2010-03-16 09:01:32:051 912 11c0 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226" is already installed.
2010-03-16 09:01:32:051 912 11c0 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2010-03-16 09:01:32:777 912 11c0 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2010-03-16 09:01:32:778 912 11c0 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://kh2003sbs:8530/ClientWebService/client.asmx
2010-03-16 09:01:33:013 912 11c0 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2010-03-16 09:01:33:013 912 11c0 PT WARNING: SOAP Fault: 0x00012c
2010-03-16 09:01:33:013 912 11c0 PT WARNING: faultstring:Fault occurred
2010-03-16 09:01:33:013 912 11c0 PT WARNING: ErrorCode:ConfigChanged(2)
2010-03-16 09:01:33:013 912 11c0 PT WARNING: Message:(null)
2010-03-16 09:01:33:013 912 11c0 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2010-03-16 09:01:33:013 912 11c0 PT WARNING: ID:f924bef7-ea1b-4fb9-b698-c44773b32e11
2010-03-16 09:01:33:025 912 11c0 PT Initializing simple targeting cookie, clientId = ec13a151-2934-4057-afb8-843c1010c4d3, target group = , DNS name = it-office.kh.local
2010-03-16 09:01:33:025 912 11c0 PT Server URL = http://kh2003sbs:8530/SimpleAuthWebService/SimpleAuth.asmx
2010-03-16 09:01:33:048 912 11c0 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2010-03-16 09:01:33:048 912 11c0 PT WARNING: SOAP Fault: 0x00012c
2010-03-16 09:01:33:049 912 11c0 PT WARNING: faultstring:Fault occurred
2010-03-16 09:01:33:049 912 11c0 PT WARNING: ErrorCode:FileLocationChanged(11)
2010-03-16 09:01:33:049 912 11c0 PT WARNING: Message:(null)
2010-03-16 09:01:33:049 912 11c0 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2010-03-16 09:01:33:049 912 11c0 PT WARNING: ID:2ec7a6a7-e3f4-42d7-a48e-585f52acfc95
2010-03-16 09:01:33:061 912 11c0 PT WARNING: Cached cookie has expired or new PID is available
2010-03-16 09:01:33:061 912 11c0 PT Initializing simple targeting cookie, clientId = ec13a151-2934-4057-afb8-843c1010c4d3, target group = , DNS name = it-office.kh.local
2010-03-16 09:01:33:061 912 11c0 PT Server URL = http://kh2003sbs:8530/SimpleAuthWebService/SimpleAuth.asmx
2010-03-16 09:01:33:358 912 11c0 PT WARNING: PTError: 0x80244025
2010-03-16 09:01:33:358 912 11c0 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80244025
2010-03-16 09:01:33:358 912 11c0 PT WARNING: Sync of Updates: 0x80244025
2010-03-16 09:01:33:358 912 11c0 Agent * WARNING: Failed to synchronize, error = 0x80244025
2010-03-16 09:01:33:358 912 11c0 DnldMgr File locations for service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 changed
2010-03-16 09:01:33:358 912 11c0 Agent Server changed and need resyncing with server
2010-03-16 09:01:33:471 912 11c0 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2010-03-16 09:01:33:471 912 11c0 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://kh2003sbs:8530/ClientWebService/client.asmx
2010-03-16 09:01:37:582 912 11c0 Agent * Found 0 updates and 55 categories in search; evaluated appl. rules of 882 out of 957 deployed entities
2010-03-16 09:01:37:583 912 11c0 Agent *********
2010-03-16 09:01:37:583 912 11c0 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2010-03-16 09:01:37:583 912 11c0 Agent *************
2010-03-16 09:01:37:592 912 1ef8 AU >>## RESUMED ## AU: Search for updates [CallId = {87E0CF55-9DD2-4B90-B9C7-4271F2E932B7}]
2010-03-16 09:01:37:592 912 1ef8 AU # 0 updates detected
2010-03-16 09:01:37:592 912 1ef8 AU #########
2010-03-16 09:01:37:592 912 1ef8 AU ## END ## AU: Search for updates [CallId = {87E0CF55-9DD2-4B90-B9C7-4271F2E932B7}]
2010-03-16 09:01:37:592 912 1ef8 AU #############
2010-03-16 09:01:37:593 912 1ef8 AU Successfully wrote event for AU health state:0
2010-03-16 09:01:37:593 912 1ef8 AU Featured notifications is disabled.
2010-03-16 09:01:37:593 912 1ef8 AU AU setting next detection timeout to 2010-03-17 02:08:37
2010-03-16 09:01:37:593 912 1ef8 AU Setting AU scheduled install time to 2010-03-16 12:00:00
2010-03-16 09:01:37:593 912 1ef8 AU Successfully wrote event for AU health state:0
2010-03-16 09:01:37:593 912 1ef8 AU Successfully wrote event for AU health state:0
2010-03-16 09:01:42:583 912 11c0 Report REPORT EVENT: {9E9F96B7-0B2E-4FA9-9607-45796A72ECC2} 2010-03-16 09:01:37:583-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
2010-03-16 09:01:42:583 912 11c0 Report REPORT EVENT: {61407279-EB0F-40C8-93DC-11EF3EAB0A6A} 2010-03-16 09:01:37:583-0000 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2010-03-16 09:01:42:585 912 11c0 Report CWERReporter finishing event handling. (00000000)
2010-03-16 09:14:39:767 912 11c0 Report Uploading 2 events using cached cookie, reporting URL = http://kh2003sbs:8530/ReportingWebService/ReportingWebService.asmx
2010-03-16 09:14:39:774 912 11c0 Report Reporter successfully uploaded 2 events.
2010-03-16 09:23:18:901 912 f64 AU AU received policy change subscription event
2010-03-16 09:58:21:496 912 f64 AU AU received policy change subscription event
2010-03-16 09:58:21:496 912 f64 AU AU Options changed from policy.
2010-03-16 09:58:21:497 912 f64 AU Successfully wrote event for AU health state:0
2010-03-16 09:58:21:497 912 f64 AU ########### AU: Policy change processed ###########
2010-03-16 09:58:21:497 912 f64 AU # Policy changed, AU refresh required = No
2010-03-16 09:58:21:497 912 f64 AU # WSUS server:
2010-03-16 09:58:21:498 912 f64 AU # Detection frequency: 20
2010-03-16 09:58:21:498 912 f64 AU # Approval type: Scheduled (Policy)
2010-03-16 09:58:21:498 912 f64 AU # Scheduled install day/time: Every day at 10:00
2010-03-16 09:58:21:498 912 f64 AU # Auto-install minor updates: Yes (Policy)
2010-03-16 09:58:21:498 912 f64 AU # Will interact with non-admins (Non-admins are elevated (User preference))
2010-03-16 09:58:21:498 912 f64 AU AU settings changed through Policy.
2010-03-16 09:58:21:498 912 f64 AU Setting AU scheduled install time to 2010-03-16 10:00:00
2010-03-16 09:58:21:498 912 f64 AU Successfully wrote event for AU health state:0
2010-03-16 09:58:21:499 912 f64 AU Successfully wrote event for AU health state:0
2010-03-16 09:58:26:498 912 184c Report CWERReporter finishing event handling. (00000000)
2010-03-16 10:00:10:003 912 f64 AU Forced install timer expired for scheduled install
2010-03-16 10:00:10:003 912 f64 AU UpdateDownloadProperties: 0 download(s) are still in progress.
2010-03-16 10:00:10:004 912 f64 AU Setting AU scheduled install time to 2010-03-17 10:00:00
2010-03-16 10:00:10:004 912 f64 AU Successfully wrote event for AU health state:0
2010-03-16 10:00:15:005 912 184c Report CWERReporter finishing event handling. (00000000)

Edited March 16, 2010 by Number6

Number6 · March 16, 2010

From the log above this line seems specific:

AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates

Seems to indicate that coms are working but that no updates were detected?

But the WSUS server reports back that the same PC needs updates.

elsiegee40 · March 16, 2010

I shall follow this with interest. I've got about 15 PCs that are not talking to WSUS and haven't been doing so for about 10 days. (All XP Pro SP2), yet there are others with the identical image that are updating.

If I look at Computers in WSUS, it says they haven't been in touch, yet I have run

wuauclt.exe /detectnow

on all of them

As my version of WSUS is in need of update, I have decided to update that and see what happens then. Probably won't get round to it until the holidays though.

Number6 · March 16, 2010

Here's what WSUS says of the same PC that the log file is from. You can see that 23 updates are needed but the PC itself reports that it's up to date.

WSUS also reports the last status update from this PC was today so it is communicating.

broc · March 16, 2010

There are loads of reasons why WSUS will suddenly stop....

Typical error messages are listed here :

Appendix G: Windows Update Agent Result Codes

My approach is to examine the windowsupdate log & look for 0x8........ errors.

We have had problems with Ghosting where the client appears to be working properly but never updates its status on WSUS, and resort to running the following:

rem Fixes problem with client machines not showing up on the server due to imaging method

@echo on

reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f

reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f

reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f

@echo Triggering detection after resetting WSUS client identity

net stop wuauserv

net start wuauserv

wuauclt /resetauthorization /detectnow

Number6 · March 16, 2010

The thing is in our case that WSUS and it's clients all appear to be talking to each other OK. The clients are just not seeing the updates.

pwds · March 16, 2010

Try manually installing the Windows Update Agent on a affected machine, restarting and then running gpupdate /force.

danrhodes · March 16, 2010

Attached are two IIS patches that can be run. I don't think this has anything to do with IIS but they may come in handy< they have fixed WSUS for me before.

Also ive attached a helpsheet with common issues regarding WSUS.

Common Problems.doc

Patches.zip

broc · March 16, 2010

I would start by trying to understand why you are getting this for a start:

2010-03-16 09:01:32:778 912 11c0 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://kh2003sbs:8530/ClientWebService/client.asmx

2010-03-16 09:01:33:013 912 11c0 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200

This could be a WMI problem.... try google as there is loads of information about WSUS problems on the WWW

Also download the WSUS Client diagnostic tool from

Windows Server Update Services Tools and Utilities

Edited March 16, 2010 by broc

Number6 · March 16, 2010

Diagnostic output file:

broc · March 16, 2010

Forgot to mention, try looking in %program files%\update services\logfiles\softwaredistribution.log file for errors too.

Number6 · March 16, 2010

Forgot to mention, try looking in %program files%\update services\logfiles\softwaredistribution.log file for errors too.

No such file in W7

elsiegee40 · March 16, 2010

If you look at the Computers in WSUS (directly, not via the updates), when is the last contect date?

Number6 · March 16, 2010

If you look at the Computers in WSUS (directly, not via the updates), when is the last contect date?

Today..

broc · March 16, 2010

No such file in W7

True, that's because I should have said it should be on your WSUS server

Number6 · March 16, 2010

True, that's because it should be on your WSUS server

Bugger, sorry!

broc · March 16, 2010

Sorry, this is all a bit 'trial & error'....

If you delete the client PC from WSUS, then run (on the client)

net stop wuauserv

net stop bits

Next delete the Softwaredistribution folder from the windows directory

and then run

net start bits

net start wuauserv

wuauclt /resetauthorization /detectnow

What happens?

If WSUS & Automatic updates comms is working properly, the deleted system should show up again within a short period of time on WSUS with 'not yet reported', and then minutes later report its correct status.

Number6 · March 16, 2010

If WSUS & Automatic updates comms is working properly, the deleted system should show up again within a short period of time on WSUS with 'not yet reported', and then minutes later report its correct status.

It did.

The PC also found updates. But... it didn't download or install them until I said it could which is not what the GP says, but that's a different problem.

So.... do I need to do this on all the affected machines now?

broc · March 16, 2010

You may need to do it on them all, it depends if they are all suffering from the same problem. I would check the log on the clients & see if they are all reporting the same set of errors.....

If you download PSTools & install you can run most of the commands remotely using psexec. You can even target multiple systems

alan-d · April 15, 2010

Sorry I'm a bit late with this but I've been hammering away at WSUS over the past few days with Clients refusing to be picked up and WSUS not picking them up all for different reasons which is annoying.

I've put together a batch file which I call my 'Kill or Cure' approach and so far it has worked on 99.9% of clients I've run it on (All XP Pro)

rem Runs BitFix
@echo
sc sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
rem Fixes problem with client machines not showing up on the server due to imaging method
@echo on
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /f
@echo update winhttp proxy
proxycfg -u
@echo Triggering detection after resetting WSUS client identity
net stop wuauserv
net start wuauserv
wuauclt /resetauthorization /detectnow
@echo Force GPO Update
gpupdate /force /boot

I don't know if this will run on Vista or Win 7 but should be easy enough to adapt.

danrhodes · April 19, 2010

Sorry I'm a bit late with this but I've been hammering away at WSUS over the past few days with Clients refusing to be picked up and WSUS not picking them up all for different reasons which is annoying.

I've put together a batch file which I call my 'Kill or Cure' approach and so far it has worked on 99.9% of clients I've run it on (All XP Pro)
rem Runs BitFix
@echo
sc sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
rem Fixes problem with client machines not showing up on the server due to imaging method
@echo on
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /f
@echo update winhttp proxy
proxycfg -u
@echo Triggering detection after resetting WSUS client identity
net stop wuauserv
net start wuauserv
wuauclt /resetauthorization /detectnow
@echo Force GPO Update
gpupdate /force /boot
I don't know if this will run on Vista or Win 7 but should be easy enough to adapt.

Added this to my public folders store for future reference, cheers.

PCs not seeing WSUS updates

Recommended Posts

Number6

broc

danrhodes

danrhodes

Number6

Number6

elsiegee40

Number6

broc

Number6

pwds

danrhodes

broc

Number6

broc

Number6

elsiegee40

Number6

broc

Number6

broc

Number6

broc

alan-d

danrhodes

Create an account or sign in to comment

Create an account

Sign in

Recent Threads

iOS 27 BYOD and Smoothwall web filtering - Connectivity Assist causing issues?

3rd Party Warranty on Existing Panels

Edge Auto Sign in Broken / Cloud Filter

Home

Forums

What's New