D
dana
Guest
An updated link for Process Explorer:
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
"aeriform" wrote:
> Not sure on the 0xc8000408 error, but the 0xc8000202 seems to be due to a
> faulty install of windows update. MY
> %windir%\SoftwareDistribution\ReportingEvents.log had entries similar to:
>
> "{4687AAD8-5ABF-40ED-835C-7B9B7A7650D5} 2005-07-20
> 10:07:05-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 c8000202 WindowsUpdate Failure Software
> Synchronization Error: Agent failed detecting with reason: 0xc8000202"
>
>
> The solution that worked for me (thanks Alex Xie) was as follows.
>
> I ignored step one which was turn off your virus checker (McAfee is fine,
> some other products may cause problems, running with as few other programs as
> possible is a good idea). You want to rename/delete
> %windir%\SoftwareDistribution because it's garbage and you want a new one to
> be installed/downloaded. If you're having trouble deleting/renaming the
> folder you can use a program like that available from
> http://www.sysinternals.com/Utilities/ProcessExplorer.html which allows you
> to close a handle that another process has on a file. One of the SVCHost.exe
> processes should have a handle on the folder, just select that File handle
> and close it, no other processes "should" have handles on the folder. Once
> you've removed/deleted that folder, just reboot and head back to the windows
> update site and hopefully you should be able to update smoothly.
>
> Alex Xie wrote:
> "...
> Step 2: Check the local Windows Update services.
> ===============
> This issue can occur if three services have not been configured correctly.
> Please refer to the following steps to check them:
>
> 1. Click Start->Run, type "services.msc" (without quotation marks) in the
> open box and click OK.
> 2. Double click the service " Background Intelligent Transfer Service ".
> 3. Click on the Log On tab, please ensure the option "Local System account"
> is selected and the option "Allow service to interact with desktop" is
> unchecked.
> 4. Check if this service has been enabled on the listed Hardware Profile. If
> not, please click the Enable button to enable it.
> 5. Click on the tab "General "; make sure the "Startup Type" is "Automatic".
> Then please click the button "Start" under "Service Status" to start the
> service.
>
> Step 3: Rename the temporary folder of Windows Update.
> ===============
> 1. Click Start, Run, type: cmd and press Enter. Please run the following
> command in the opened window.
>
> Net stop WuAuServ
>
> 2. Click Start, Run, type: %windir% and press Enter.
>
> 3. In the opened folder, rename the folder SoftwareDistribution to Sdold.
>
> 4. Click Start, Run, type: cmd and press Enter. Please run the following
> command in the opened window.
>
> Net start WuAuServ
> ..."
>
>
> "Alan Tattersall" wrote:
>
> > I've been dealing today with a MS technician who's tried very hard. He's
> > moved me past the 0xc8000202 message but only to where I now get 0xc8000408.
> >
> > ...
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
"aeriform" wrote:
> Not sure on the 0xc8000408 error, but the 0xc8000202 seems to be due to a
> faulty install of windows update. MY
> %windir%\SoftwareDistribution\ReportingEvents.log had entries similar to:
>
> "{4687AAD8-5ABF-40ED-835C-7B9B7A7650D5} 2005-07-20
> 10:07:05-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 c8000202 WindowsUpdate Failure Software
> Synchronization Error: Agent failed detecting with reason: 0xc8000202"
>
>
> The solution that worked for me (thanks Alex Xie) was as follows.
>
> I ignored step one which was turn off your virus checker (McAfee is fine,
> some other products may cause problems, running with as few other programs as
> possible is a good idea). You want to rename/delete
> %windir%\SoftwareDistribution because it's garbage and you want a new one to
> be installed/downloaded. If you're having trouble deleting/renaming the
> folder you can use a program like that available from
> http://www.sysinternals.com/Utilities/ProcessExplorer.html which allows you
> to close a handle that another process has on a file. One of the SVCHost.exe
> processes should have a handle on the folder, just select that File handle
> and close it, no other processes "should" have handles on the folder. Once
> you've removed/deleted that folder, just reboot and head back to the windows
> update site and hopefully you should be able to update smoothly.
>
> Alex Xie wrote:
> "...
> Step 2: Check the local Windows Update services.
> ===============
> This issue can occur if three services have not been configured correctly.
> Please refer to the following steps to check them:
>
> 1. Click Start->Run, type "services.msc" (without quotation marks) in the
> open box and click OK.
> 2. Double click the service " Background Intelligent Transfer Service ".
> 3. Click on the Log On tab, please ensure the option "Local System account"
> is selected and the option "Allow service to interact with desktop" is
> unchecked.
> 4. Check if this service has been enabled on the listed Hardware Profile. If
> not, please click the Enable button to enable it.
> 5. Click on the tab "General "; make sure the "Startup Type" is "Automatic".
> Then please click the button "Start" under "Service Status" to start the
> service.
>
> Step 3: Rename the temporary folder of Windows Update.
> ===============
> 1. Click Start, Run, type: cmd and press Enter. Please run the following
> command in the opened window.
>
> Net stop WuAuServ
>
> 2. Click Start, Run, type: %windir% and press Enter.
>
> 3. In the opened folder, rename the folder SoftwareDistribution to Sdold.
>
> 4. Click Start, Run, type: cmd and press Enter. Please run the following
> command in the opened window.
>
> Net start WuAuServ
> ..."
>
>
> "Alan Tattersall" wrote:
>
> > I've been dealing today with a MS technician who's tried very hard. He's
> > moved me past the 0xc8000202 message but only to where I now get 0xc8000408.
> >
> > ...