Windows update and WSUS

Burnsy2023 · 2 Apr 2009 at 21:43

I'm getting very annoyed as for a while my Vista machine hasn't been getting updates. However, when checking for updates I get a error: 80070424.

I've tried restarting the BITS service, I've tried registering DLLs using these commands:

regsvr32 wuaueng.dll ->Wouldn't work until UAC is turned off.
Regsvr32 QMGR.DLL -> this one errors out and says it can't find an entry point.

I've got WSUS on my server and have added a group policy so that it should get the updates from that. I've run gpupdate but how do I tell what server it's looking at?

Any other advice?

Snow-Munki · 2 Apr 2009 at 22:20

have you tried the client diag tool ?

http://absoblogginlutely.net/mtblogarchive/005304.php

Burnsy2023 · 2 Apr 2009 at 22:44

I get this when running the tool

J.B · 3 Apr 2009 at 00:40

I had this problem a while ago I think, cant remember the exact error number.

There was a list of several dll files to regsrv32 which seemed to work for everyone else but me. Then someone suggested running a SFC scan, which mine failed to intiate. At this point I decided my time would be better spent reformatting.

Sorry its not much help.

Django x2 · 3 Apr 2009 at 01:15

Hmm. I take it WSUS has the correct computer groups set up and this machine is pointing to the right server in its GPO?

This might be a step too high but is your gpresult coming back with the WSUS GPO as a result? Remember, the WSUS GPO should be completely seperate on its own OU.

If not, I think a re-install may well be on ther cards

Burnsy2023 · 3 Apr 2009 at 12:44

Lucero said:
Hmm. I take it WSUS has the correct computer groups set up and this machine is pointing to the right server in its GPO?

This might be a step too high but is your gpresult coming back with the WSUS GPO as a result? Remember, the WSUS GPO should be completely seperate on its own OU.

All present and correct

I really don't want to reinstall :mad:

Pigeon_Killer · 3 Apr 2009 at 13:02

Had the same problem with updates last year. Countless hours wasted looking for a solution but not one person seems to have found an answer. Wouldn't waste any more of your time.

Vertigo · 3 Apr 2009 at 18:08

Check this registry key:

HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

There should be two values, "WUServer" and "WUStatusServer", both set to https://wsusserver.domain:8531

A check for updates can be forced from the command line by typing "wuauclt /detectnow"

IME, even with a perfectly functioning WSUS server from which all clients successfully retrieve updates, initiating a standard Windows Update from the client still bypasses the WSUS server and goes directly to the website. Never known why exactly but can't say I've been bothered much as everything just works anyway.

On odd occasions I've had machines that just won't update but it's always been fixed by removing the agent from the client and re-deploying it again.

Django x2 · 4 Apr 2009 at 00:09

Vertigo1 said:
Check this registry key:

HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

There should be two values, "WUServer" and "WUStatusServer", both set to https://wsusserver.domain:8531

A check for updates can be forced from the command line by typing "wuauclt /detectnow"

IME, even with a perfectly functioning WSUS server from which all clients successfully retrieve updates, initiating a standard Windows Update from the client still bypasses the WSUS server and goes directly to the website. Never known why exactly but can't say I've been bothered much as everything just works anyway.

On odd occasions I've had machines that just won't update but it's always been fixed by removing the agent from the client and re-deploying it again.

I can't do this. If I point a client directly to the WU website, the site comes back saying that WUs are administered locally and cannot be downloaded from the site.

Burnsy2023 · 12 Apr 2009 at 14:27

Sorted this in the end with help. Turns out it was a problem with the Windows Trusted Module Service. Readding registry values sorted it out. Thank god I don't have to format.

Vertigo · 12 Apr 2009 at 18:58

Burnsy2023 said:
Sorted this in the end with help. Turns out it was a problem with the Windows Trusted Module Service. Readding registry values sorted it out. Thank god I don't have to format.

You always have to format, it's just a question of when

Think of it like death - it's inevitable.

Burnsy2023 · 12 Apr 2009 at 19:02

Vertigo1 said:
You always have to format, it's just a question of when

Think of it like death - it's inevitable.

Lets hope I don't have to format until I'm collecting my pension