Win 2000 error message on Win XP computer

[martyk444]

error message 1073741819...LSA Shell...causes Windows to
shut down. This is an error message for Win 2000, but
this computer is running Win XP Home. MS article 260910
says to download an update, but this is for the wrong
OS. What now ? Martyk444(remove this)@hotmail.com

 

[Carey Frisch [MVP]]

How to Remove the "Sasser Worm" from your Computer:
http://www3.telus.net/dandemar/sasser.htm

[Courtesy of MS-MVP Jupiter Jones]

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

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/security/protect/default.aspx

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

:

| error message 1073741819...LSA Shell...causes Windows to
| shut down. This is an error message for Win 2000, but
| this computer is running Win XP Home. MS article 260910
| says to download an update, but this is for the wrong
| OS. What now ? Martyk444(remove this)@hotmail.com

 

[S.Sengupta]

This is the sasser worm,check it here:-

http://vil.nai.com/vil/content/v_125007.htm
http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_SASSER.A

To stop the shutdown, click start/run, type "shutdown -a" (without the
quotes)> ok.

Details on the patch needed to prevent it:

http://www.microsoft.com/technet/security/bulletin/MS04-011.mspx

see also:-http://www.microsoft.com/security/incident/sasser.mspx
regards,
ssg MS-MVP
pronetworks.org

error

message 1073741819...LSA Shell...causes Windows to

 

[Bruce Chambers]

error message 1073741819...LSA Shell...causes Windows to
shut down. This is an error message for Win 2000, but
this computer is running Win XP Home. MS article 260910
says to download an update, but this is for the wrong
OS. What now ? Martyk444(remove this)@hotmail.com

You've apparently contracted the latest worm, W32.Sasser.Worm,
specifically designed to attack people who do not update their
computers promptly and who do not practice "safe hex." In other
words, like Blaster, this worm was developed and distributed after a
patch for the vulnerability was announced and made publicly available.
Further, and also like Blaster, this worm could not affect any
computer whose user had taken the basic precaution of using a properly
configured firewall.

To stay on-line long enough to get the necessary updates, patches,
and removal tools, click Start > Run, and enter "shutdown -a" when the
next Shutdown countdown begins. This will abort the shut down. Also,
make sure you've enabled a firewall before starting, to preclude any
more intrusions while getting the updates/patches/tools.

What You should Know about the Sasser Worm and its Variants
http://www.microsoft.com/security/incident/sasser.asp

Microsoft Security Bulletin MS04-011
http://www.microsoft.com/technet/security/bulletin/MS04-011.mspx

W32.Sasser.Worm
http://www.symantec.com/avcenter/venc/data/w32.sasser.worm.html

A tool is available to remove the Sasser worm variants
http://support.microsoft.com/default.aspx?scid=kb;EN-US;841720

W32.Sasser.Worm Removal Tool
http://securityresponse.symantec.com/avcenter/venc/data/w32.sasser.removal.tool.html

McAfee AVert Stinger Virus Removal Tool
http://vil.nai.com/vil/stinger/

--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. - RAH

 

[Guest]

I have had similar problems (on XP Home), but neither Stinger nor FXSasser
(from Symantec) has detected Sasser. I did find BugBear, but detleting that
infection has not stopped the LSA error.

I have tried to download the service back but keep getting other error
messages even when I used the "shutdown -a" command and stayd on line. I am
now waiting for a CD, although MS have adised me that I need a patch from my
ISP BEFORE installing SP2 to ensure that my broadband connection will not be
disabled! I find this odd as I have signed up for automatic updates (on
another system - XP Pro) but that has not got SP 2 installed (I have
Ver5.1.2600 - SP1 Build 2600). Do automatic updates not do the same as the
new service pack, and how can automated upated be provided if rely on a patch
from a 3rd party?

 

[Malke]

I have had similar problems (on XP Home), but neither Stinger nor
FXSasser (from Symantec) has detected Sasser. I did find BugBear, but
detleting that infection has not stopped the LSA error.

You might have the older MSBlaster or one of the many Agobot/Gaobot
variants. Stinger is a good little first-line tool, but it is no
substitute for an installed full-featured antivirus using updated
deifnitions. Do you have one? If not, you need to get one ASAP.

I have tried to download the service back but keep getting other error
messages even when I used the "shutdown -a" command and stayd on line.
I am now waiting for a CD, although MS have adised me that I need a
patch from my
ISP BEFORE installing SP2 to ensure that my broadband connection will
not be
disabled! I find this odd as I have signed up for automatic updates
(on
another system - XP Pro) but that has not got SP 2 installed (I have
Ver5.1.2600 - SP1 Build 2600). Do automatic updates not do the same
as the new service pack, and how can automated upated be provided if
rely on a patch from a 3rd party?

There is no point installing a service pack if your computer is not
clean. Nothing will work right. Address the virus/spyware issues first
and then do all the normal pre-installation preparation; i.e., getting
drivers and application patches onhand, doing disk cleanup, backing up
data.

Malke