Vista x64 not working with WSUS 3.0

Hello Experts,

I've been working on this problem for a while now, Vista x64 just isn't updating from my WSUS server.

I've got 26 XP pro workstations and 1 other Vista Business installations (x86) working fine with WSUS 3.0 over 2 domains, which indicates the GPO is set properly and all WSUS settings are correct.

the Vista x64 computer hasn't reported in for over 120 days and is apparently stuck at 88% (not so).

When I run ClientDiag.exe I am getting an error (attached) that I haven't come accross before. I've tried forcing check ins, i've also ensured the Autmatic Updates service is running with correct permissions etc etc.

Any help would be great!
wsus-error.JPG
BakasITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ryan_RIT Systems AdministratorCommented:
Microsoft recently pushed updates to update 'Windows Update' - see this article
http://www.news.com/8301-10784_3-9778152-7.html

Possibly your Vista 64bit machine hasn't got these files updated - and I'm under the impression that these are the files being referred to by the diagnostics app when checking the file versions.


Also can you do the following:
Note the current system time on your PC

Then goto Start - Run
type     wuauclt /detectnow

Wait for 30 seconds

Then open up c:\Windows\WindowsUpdate.log
Scroll down to the lines that start with the system time you noted (or thereabouts). Can you post everything from that line to the end of the file here for us to look at - thanks.
0
BakasITAuthor Commented:
Ryan R,
Cheers for your help mate, discovered that I do indeed have the 'stealth update' installed. I wasn't sure as to whether or not it hadn't installed correctly so I downloaded it from Microsoft:
http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.0.6000.381/WindowsUpdateAgent30-x64.exe

and the install went though without issues. Still getting the same result with clientdiag.exe though. I've compared it to my own system's clientdiag.exe output and I've realised its failing on wuauclt.dll check. even after a fresh install. strange.

I've checked and the latest version of the dll is where its meant to be...

any further ideas?
0
Ryan_RIT Systems AdministratorCommented:
See if going to update.microsoft.com and starting the update process (which will install the latest update clients and some other stuff) helps at all. Go up to the stage where you have a large list of updates that you can install and stop there (since you'll want to get them from your server).

Also can you post the end part of your WindowsUpdate Log file?

Thanks
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

BakasITAuthor Commented:
In Vista, if you go to update.microsoft.com Microsoft supplies you with directions to your control panel update icon. If you Go via IE7s shortcut, it just opens the updates section in conrtrol panel automatically.

Over the weekend, I noticed that someone had taken this particular computer's account out of the correct OU on the DC. I'm not sure when this happened but having re-added it and forcing a check in The pc is now reporting in and is appearing as 100%

This hasn't fixed the ClientDiag issues though. Because my main question is related to this, the points are still available and i'll keep the question open.

WindowsUpdate.log doens't contain anything very interesting within the last few lines but here it is never the less.

I believe that this is just showing the successful checking for updates as it should.

Cheers,
Henry
2008-02-06	16:06:30:240	 684	1a80	Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2008-02-06	16:06:30:240	 684	1a80	Agent	*********
2008-02-06	16:06:30:240	 684	1a80	Agent	  * Online = Yes; Ignore download priority = No
2008-02-06	16:06:30:240	 684	1a80	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"
2008-02-06	16:06:30:240	 684	1a80	Agent	  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-02-06	16:06:30:240	 684	1a80	Setup	Checking for agent SelfUpdate
2008-02-06	16:06:30:241	 684	1a80	Setup	Client version: Core: 7.0.6000.381  Aux: 7.0.6000.381
2008-02-06	16:06:30:241	 684	1a80	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2008-02-06	16:06:30:246	 684	1a80	Misc	 Microsoft signed: Yes
2008-02-06	16:06:30:262	 684	1a80	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2008-02-06	16:06:30:266	 684	1a80	Misc	 Microsoft signed: Yes
2008-02-06	16:06:30:269	 684	1a80	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2008-02-06	16:06:30:273	 684	1a80	Misc	 Microsoft signed: Yes
2008-02-06	16:06:30:277	 684	1a80	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2008-02-06	16:06:30:281	 684	1a80	Misc	 Microsoft signed: Yes
2008-02-06	16:06:30:301	 684	1a80	Setup	Determining whether a new setup handler needs to be downloaded
2008-02-06	16:06:30:301	 684	1a80	Setup	SelfUpdate handler update required: Current version: 7.0.6000.381, required version: 7.0.6000.374
2008-02-06	16:06:30:302	 684	1a80	Setup	Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.0.6000.374"
2008-02-06	16:06:30:969	 684	1a80	Setup	Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.0.6000.374" is not applicable
2008-02-06	16:06:30:969	 684	1a80	Setup	Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.0.6000.374"
2008-02-06	16:06:31:109	 684	1a80	Setup	Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.0.6000.374" is not applicable
2008-02-06	16:06:31:110	 684	1a80	Setup	Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.0.6000.374"
2008-02-06	16:06:31:313	 684	1a80	Setup	Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.0.6000.374" is not applicable
2008-02-06	16:06:31:314	 684	1a80	Setup	SelfUpdate check completed.  SelfUpdate is NOT required.
2008-02-06	16:06:33:592	 684	1a80	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
2008-02-06	16:06:33:592	 684	1a80	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://hermes:8530/ClientWebService/client.asmx
2008-02-06	16:07:39:044	 684	1a80	Agent	  * Found 0 updates and 42 categories in search; evaluated appl. rules of 478 out of 569 deployed entities
2008-02-06	16:07:39:263	 684	1a80	Agent	*********
2008-02-06	16:07:39:264	 684	1a80	Agent	**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2008-02-06	16:07:39:264	 684	1a80	Agent	*************
2008-02-06	16:07:39:266	 684	15d0	AU	>>##  RESUMED  ## AU: Search for updates [CallId = {6A37DB12-0D86-4462-B553-729AD5435685}]
2008-02-06	16:07:39:266	 684	15d0	AU	  # 0 updates detected
2008-02-06	16:07:39:266	 684	15d0	AU	#########
2008-02-06	16:07:39:266	 684	15d0	AU	##  END  ##  AU: Search for updates [CallId = {6A37DB12-0D86-4462-B553-729AD5435685}]
2008-02-06	16:07:39:266	 684	15d0	AU	#############
2008-02-06	16:07:39:267	 684	15d0	AU	AU setting next detection timeout to 2008-02-06 06:32:09
2008-02-06	16:07:39:267	 684	15d0	AU	Setting AU scheduled install time to 2008-02-07 01:30:00
2008-02-06	16:07:44:263	 684	1a80	Report	REPORT EVENT: {A7C4B729-F757-4A3E-9900-112E086B92FC}	2008-02-06 16:07:39:263+1030	1	147	101	{00000000-0000-0000-0000-000000000000}	0	0	AutomaticUpdates	Success	Software Synchronization	Windows Update Client successfully detected 0 updates.
2008-02-06	16:07:44:263	 684	1a80	Report	REPORT EVENT: {F5DDF0EB-F2B3-40C4-80B2-9163E486FDB1}	2008-02-06 16:07:39:263+1030	1	156	101	{00000000-0000-0000-0000-000000000000}	0	0	AutomaticUpdates	Success	Pre-Deployment Check	Reporting client status.
2008-02-06	16:12:58:430	 684	1a80	Report	Uploading 2 events using cached cookie, reporting URL = http://hermes:8530/ReportingWebService/ReportingWebService.asmx
2008-02-06	16:12:58:436	 684	1a80	Report	Reporter successfully uploaded 2 events.

Open in new window

0
Ryan_RIT Systems AdministratorCommented:
Well I'll get you to wait until your WSUS server get's some more updates for the Vista machine and then get you to check if everything works. If it does - then you can close the question. If there are issues then we can look at the diagnostics - unless someone else wants to post about it.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ryan_RIT Systems AdministratorCommented:
Attached is the start of the output from a working computer running the test:

Note the file there that has a PASS after checking the BITS service - this file most likely is the one missing on your PC:
WSUS Client Diagnostics Tool
 
Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 5.8.0.2469. . . . . . . . . . . . . PASS     <-----------------------
This version is WSUS 2.0

Open in new window

0
BakasITAuthor Commented:
Even though the clientdiag still doesn't run properly, I'll award you the points for your help. It seems that all is running well at the moment, saw two updates pulled from the WSUS server successfully in windowsupdate.log.

I've made sure that those files are present and of the correct version but for some reason clientdiag is not detecting them. It could simply be a Vista quirk or a incompatibilty with client diag with Vista x64.

even so, all is running now. cheers mate.

Thanks for your help Ryan!
0
BakasITAuthor Commented:
Cheers for your help mate, I know its not complete but I think you deserve the points for the work you put in. All that really matters is that it is now updating as it should.

thanks agian,
Henry
0
Ryan_RIT Systems AdministratorCommented:
No problems - thanks for the points.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.