thanks, did all steps and I'm still getting the same result. guess I'll keep digging On Tue, Feb 23, 2010 at 6:53 AM, Chris Hill <chill@xxxxxxxxxxxxxxxx> wrote: > 1) Delete the computer from the WSUS server (not really necessary, but not > a bad idea). > > 2) stop the AU service (services.msc) > > 3) Delete the " C:\Windows\SoftwareDistribution" folder > > 4) Delete the "C:\Windows\WindowsUpdate.log" file > > 5) Open a command prompt and execute the following batch file: > > > > @echo on > > net stop wuauserv > > 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 REG DELETE > "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" > > /v LastWaitTimeout /f > > REG DELETE > > "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" > > /v DetectionStartTime /f > > Reg Delete > > "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" > > /v NextDetectionTime /f > > regsvr32 /s wuapi.dll > > regsvr32 /s wups.dll > > regsvr32 /s wuaueng.dll > > regsvr32 /s wucltui.dll > > regsvr32 /s msxml3.dll > > regsvr32 /s wuapi.dll > > regsvr32 /s wuaueng.dll > > regsvr32 /s wuaueng1.dll > > regsvr32 /s wucltui.dll > > regsvr32 /s wups.dll > > regsvr32 /s wups2.dll > > regsvr32 /s wuweb.dll > > net start wuauserv > > wuauclt /resetauthorization /detectnow > > exit > > > > Most of the time just step 2, 3, restart service from 2, then wuauclt.exe > /detectnow from a command prompt and all is well, the whole process pretty > much guarantees it though > > > > *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Steve Snyder > *Sent:* Tuesday, 23 February 2010 3:29 PM > *To:* thin@xxxxxxxxxxxxx > *Subject:* [THIN] OT:WSUS 3 issue > > > > slowly poking around and learning wsus on the fly - I have one server that > seems to be checking in okay with the WSUS server on both the server and > client logs, but the client keeps seeing 0 updates needed and the WSUS > server shows 20 updates needed for that client. from the registry on the > client it appears the last successful install was last october. > > ideas? troubleshooting tips? >