Fix: Failed to populate ServiceStartup entries in Cache: error 0×80070002 in WSUS

by admin on May 30, 2008

Today I configured my new Windows Server 2003 R2 machine to use our internal Windows Software Update Services (WSUS) 3.0 box as a local repository for Microsoft patches and updates.  The server didn’t appear in the WSUS console, so I checked out the C:\Windows\WindowsUpdate.log file on the new server and found the following error:

EEHndlr WARNING: Failed to populate ServiceStartup entries in Cache: error 0×8007000

I was able to fix this error, which appeared to be caused by a corrupted Windows Update Client, by doing the following:

1)  Download the most recent version of the Windows Update Client. 

You can find the links to the appropriate version in the wuredist.cab file available from Microsoft.  Extract the file and you will have a wuredist.xml file that has links to the current ( version 7.0.6000.381 as of 2008-05-29 ) x86, x64, and ia64 Itanium clients.

2) Run a command prompt, and change to the directory where you downloaded the client

3) From the command prompt run

WindowsUpdateAgent30-xx.exe /wuforce /norestart

Where WindowsUpdateAgent30-xx.exe is the name of the client you downloaded

4) Force the newly installed Windows Update Client to synchronize with the WSUS server by running

wuauclt /detectnow

Soon my server appeared in the WSUS console, and I was able to manage the patches on it.

Related Posts

{ 2 comments… read them below or add one }

jeff December 29, 2008 at 4:54 am

This worked like a champ, thanks.

Reply

Tom Richards January 16, 2009 at 7:59 am

Used psexec to run this on all the machines on the network that weren’t reporting to the WSUS server; ten minutes later, all of them had reported in and had downloaded updates – thank you very much!

Reply

Leave a Comment

Previous post:

Next post: