mzhao <> wrote:
> 2 problems:
> 1. The CPU Usage is still going to rise to NEARLY 100% when checking
> updates from Microsoft Update Website
This no longer matters, as the CPU consumption is in a background process
with lower priority than before, so the update checking process will no
longer disrupt your foreground activity.
> 2. The whole update checking process took nearly 6 minutes, which is
> not acceptable (if it happens every time)
As this is in the background, it does not really matter how long it takes:
it is not interfering with your usage of the PC.
The length of the checking process seems to be associated primarily with the
presence of Office 2003. Make sure your Office installation (particularly
MSO.DLL) is totally up to date. If bringing it up to date does not help,
then you could try uninstalling Office completely, and re-installing a fresh
copy, then bringing that up to date with Service Packs and patches.
On my desktop PC with XP Pro and Office 2003, the Microsoft Update checking
process takes about 45 seconds, on my laptop with the same, it takes about 1
min 15 secs. So your 6 minutes suggests something specifically wrong in
your system.
Another suggested area to be investigated is the file
C:\WINDOWS\SoftwareDistribution\DataStore\DataStor e.edb
Experts only: you might wish to investigate the use of the "esentutl"
command on this database file - it is self-documenting. Make sure the
"wuauserv" service is stopped first.
The final thing to try is just wiping out the entire
C:\WINDOWS\SoftwareDistribution\ folder hierarchy (by stopping wuauserv and
BITS and then renaming SoftwareDistribution). This hierarchy will be
rebuilt by the next use of Microsoft Update, but you will lose forever all
update history.
--
Robin Walker [MVP Networking]
Similar Threads
Linear Mode
