Check out this page
http://support.microsoft.com/kb/977165. It says
On certain Windows XP-based systems, this security update may be reoffered.
This problem occurs because certain binaries are in a "Not Signed" state. To
resolve this issue, follow the steps in the "Method 3: Rename the Catroot2
folder" section of the following article in the Microsoft Knowledge Base:
822798 (
http://support.microsoft.com/kb/822798/ ) You cannot install some
updates or programs.
This is the information provided in 822798 for method 3
Method 3: Rename the Catroot2 folder
Rename the Catroot2 folder (Windows XP and Windows Server 2003 only), and
then try to install the program again.
Note Skip this method if the operating system is Windows 2000.
To rename the Catroot2 folder, follow these steps:
1.. Click Start, click Run, type cmd, and then click OK.
2.. At the command prompt, type the following commands, and then press
ENTER after each line:
net stop cryptsvc
ren %systemroot%\System32\Catroot2 oldcatroot2
net start cryptsvc
exit
3.. Remove all tmp*.cat files from the following folder:
%systemroot%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
If no files that start with tmp exist in this folder, do not remove any
other files. The .cat files in this folder are necessary for installing
hotfixes and service packs.
Important Do not rename the Catroot folder. The Catroot2 folder is
automatically recreated by Windows, but the Catroot folder is not recreated
if the Catroot folder is renamed.
Good luck,
Jim
"R_W_B" wrote in message
news
![Big Grin :D :D](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f600.png)
8D3CAB6-D44B-4120-B2DD-7B8D52552E0C@microsoft.com...
> Hello, my automatic updates keeps saying I need to download and install
> the Security Update XP kb977165. Problem is that I have clicked OK
> and it has download and also installed this update now 6 times on my
> laptop running XP sp3 and after each time it still says the same update
> needs downloading. Been getting updates for years now with no issue ?
> Is anybody else having this issue ?
>