A
Andreas Volkert
dear friends,
had a strange experience this evening!
I hope, you have a solution or an explanation. Thanks in advance.
Customers PC had the sasser worm on it. I tried to install the kb-patch
835732 from my memory-stick.
the update ended as non-sucessful and was interrupted because of a missing
seclogon.dll file which - the system pretends - is not existing on the
harddrive in windows\system32 folder.
I thought - no problem, took a second w2k sp pc, searched for the file,
found it, coopied it to my memory stick and plugged it in - no seclogon.dll
file to be seen on it ( be sure, i removed the checkbox for the system-files
and showed all files before!). So i tried to rename the file on the stick
with the extension txt and copied it to the relevant folder. then tried to
rename it to seclogon.dll. Windows refused to rename, because already
existent.
Then tried to re-run the SP4 update. Interrupted because of missing
seclogon-file.
Does anybody have an idea, what's happening here?
i guess, the worm is still alive, but several removal tools say no. how to
install the kb835732 update now?
best regards
Andreas Volkert
had a strange experience this evening!
I hope, you have a solution or an explanation. Thanks in advance.
Customers PC had the sasser worm on it. I tried to install the kb-patch
835732 from my memory-stick.
the update ended as non-sucessful and was interrupted because of a missing
seclogon.dll file which - the system pretends - is not existing on the
harddrive in windows\system32 folder.
I thought - no problem, took a second w2k sp pc, searched for the file,
found it, coopied it to my memory stick and plugged it in - no seclogon.dll
file to be seen on it ( be sure, i removed the checkbox for the system-files
and showed all files before!). So i tried to rename the file on the stick
with the extension txt and copied it to the relevant folder. then tried to
rename it to seclogon.dll. Windows refused to rename, because already
existent.
Then tried to re-run the SP4 update. Interrupted because of missing
seclogon-file.
Does anybody have an idea, what's happening here?
i guess, the worm is still alive, but several removal tools say no. how to
install the kb835732 update now?
best regards
Andreas Volkert