Win XP/Update bug

  • Thread starter Thread starter Boca Bob
  • Start date Start date
B

Boca Bob

Altho Knowledge Base article 822798 gives a "resolution"
for recurring update recomendations, IT DOESN'T WORK for
819696 which according to the install history has been
successfully installed several times over the past few
months. How can Update be fixed so that only patches NOT
previously installed be identified ???
 
Prevent Windows Update from prompting you to install a Hotfix
you know is already installed.
http://www.dougknox.com/xp/scripts_desc/xp_hotfix_prompt.htm

[Courtesy of MS-MVP Doug Knox]


--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

----------------------------------------------------------------------------


| Altho Knowledge Base article 822798 gives a "resolution"
| for recurring update recomendations, IT DOESN'T WORK for
| 819696 which according to the install history has been
| successfully installed several times over the past few
| months. How can Update be fixed so that only patches NOT
| previously installed be identified ???
 
Try this it worked for me, I was not getting this error
code,but a hotfix kept showing up after it was
installed,Later Mike
Question: I have Windows XP Home installed, and I've been
trying to install the critical updates for my system like
you recommend. But I get errors that say Windows Update
was unable to complete the operation. The error is 643.
Help! What can I do? - Jeff P.

Answer: One common problem that causes the 643 error
message is a corrupt or damaged catalog database log file
(Edb.log). This database is used by Windows Update and
also by the Windows Media Player. Another clue that this
is the problem is performance problems with WMP (slow
response). The easiest way to fix the problem is to
delete the catalog database file; it will then be
recreated by the system. The file is located in the
following folder: Windows\System32\Catroot2. Normally,
the file should be 5,120KB in size, but when it becomes
corrupt, it can grow to several megabytes in size.
Microsoft also has a fix (Q817287) that should be
installed to prevent the problem from recurring. See:
http://www.winxpnews.com/rd/rd.cfm?id=030923QC-
Windows_Updates
 
Back
Top