Extract from Installation History on Windows Update:
#Successful 05 May 2004 Security Update for Windows XP
(KB835732) Automatic update
#Successful 27 April 2004 Security Update for Windows XP
(KB835732) Automatic update
#Successful 26 April 2004 Security Update for Windows XP
(KB835732) Automatic update
#Successful 25 April 2004 Security Update for Windows XP
(KB835732) Automatic update
#Successful 24 April 2004 Security Update for Windows XP
(KB835732) Automatic update
#Successful 22 April 2004 Security Update for Windows XP
(KB835732) Automatic update
#Successful 21 April 2004 Security Update for Windows XP
(KB835732) Automatic update
#Successful 20 April 2004 Security Update for Windows XP
(KB835732) Automatic update
#Successful 18 April 2004 Security Update for Windows XP
(KB835732) Automatic update
#Successful 17 April 2004 Security Update for Windows XP
(KB835732) Automatic update
#Successful 14 April 2004 Security Update for Windows XP
(KB835732) Automatic update
The most important thing is that it is installed to prevent
infestation by the Sasser worm.
Since you've confirmed that it is listed in Add/Remove Programs,
advise you to compare the files of the update with the files on your
system and check the Registry key that shows it as installed.
Go here :
http://www.microsoft.com/technet/security/Bulletin/MS04-011.mspx
Under the " General Information " heading click the plus sign next to
Security Update Information, click the plus sign next to
Windows XP (all versions). Scroll down to " File Information " and
compare the versions of callcont.dll, mst120.dll, and nscom.dll
with the files on your system ( make sure you choose pre-SP1 or with
SP1 to match your installation ). They are located in the Program
Files\NetMeeting folder. Right click the files, choose Properties,
click the Version tab. If these files match and the Registry key
matches (it is given on the above page under " Verifying Update
Installation ") , then the update is installed and not being detected
by the Windows Update site.
MowGreen [MVP]
*-343-* Never Forgotten
> Dai,
>
> The most important thing is that it is installed to prevent
> infestation by the Sasser worm.
> Since you've confirmed that it is listed in Add/Remove Programs,
> advise you to compare the files of the update with the files on your
> system and check the Registry key that shows it as installed.
>
> Go here :
> http://www.microsoft.com/technet/security/Bulletin/MS04-011.mspx
>
> Under the " General Information " heading click the plus sign next to
> Security Update Information, click the plus sign next to
> Windows XP (all versions). Scroll down to " File Information " and
> compare the versions of callcont.dll, mst120.dll, and nscom.dll
^^^^^
Don't you mean nmcom.dll?
> with the files on your system ( make sure you choose pre-SP1 or with
> SP1 to match your installation ). They are located in the Program
> Files\NetMeeting folder. Right click the files, choose Properties,
> click the Version tab. If these files match and the Registry key
> matches (it is given on the above page under " Verifying Update
> Installation ") , then the update is installed and not being detected
> by the Windows Update site.
>
OK, I did that. Both the NetMeeting folder and the Registry indicate that
I have the three files in the correct versions as described on the
Microsoft page. So I know that "the update is installed and not being
detected by the Windows Update site." So how do I keep it from getting
downloaded day after day?
--
David Tenner
dte...@ameritech.net
MowGreen [MVP]
>.
>
I've checked and the files callout.dll and nmcom.dll are the
correct versions.... however...... I do not find nscom.dll on my
system (WinXP Home - (pre-SP1) and neither do I see it listed under
File Information on the page you list? Should I have this file??
Thanks for your time......... JamesKB
MowGreen [MVP]
*-343-* Never Forgotten
MowGreen [MVP]
-343-* Never Forgotten