Quote:
Originally Posted by _drummer_
|
Yup, I'm sure. It was after BlazeFind started abusing wsaupdater that they rolled the change back.
It's not uncommon for the MicroSoft update procedures to fail that rollback (if you install SP1, then follow every update given in order without jumping SP2 etc), there's a bug in the update procedure that
can leave wsaupdater being called.
That's why the MSKB article you linked states to copy userinit.exe from a known good location & name it wsaupdater.exe on the target, as the failed rollback involves the registry keys still pointing to wsaupdater.