I think I broke it!

[Blammo300]

I had a error that kept popping up in Windows that said Lsass.ese had some problem and had to restart my computer in 50sec. So i looked on google and found this site:

http://www.jsiinc.com/SUBK/tip5400/rh5456.htm

and it told me to type this in to fix the problem

REG DELETE HKLM\SYSTEM\CurrentControlSet\Services\WinSock2 /f

REG DELETE HKLM\SYSTEM\ControlSet001\Services\WinSock2 /f

REG DELETE HKLM\SYSTEM\ControlSet002\Services\WinSock2 /f

REG DELETE HKLM\SYSTEM\ControlSet003\Services\WinSock2 /f

So I did and then after I restarted my computer my internet stopped working. My DSL is a direct connection through a switch, the DSL just usually plugs in and works. So I ran the network connection manager-didnt work, then I ran Norton Utilities 2002 windoctor and it fixed some stuff-didnt work, and then I took the reg items that I entered that caused this problem but I replaced Delete with ADD and they all said "operation completed" but it-didnt work.

So now I am typing this using my older 400mhz computer. MY OS is Windows XP Pro SP1.

 

[Psych]

Hopefully, it's just a benign Windows Problem (TM).

But it might be Sasser. That's the virus that everyone is talking about on the boards. Microsoft released a patch that would protect you from Sasser a few weeks ago, and I suggest you find out whether or not you've installed it. In order to give you time to do so, go to start and run, then type "shutdown -a." I had heard that the virus disabled the abort function, but hopefully it didn't.

 

[Waylander]

you could try reinstalling tcp/ip on your network card..

also http://support.microsoft.com/default.aspx?scid=kb;en-us;811259&Product=winxp gives you some advice on trouble shooting winsock corruption...

 

[n0cmonkey]

Before you hook back to the net, make sure you're patched. Please.

 

[redbeard1]

There is a new virus out that can cause this error.

 

[adrenalinekick84]

I had this problem on a friend's computer with Win2k Pro, so hopefully it is similiar. First of all, I'd say you have a version of the Sasser worm. Check your computer for that first, I recommend looking at http://vil.nai.com/vil/content/v_125008.htm for info on the problem and downloading the Stinger tool as well (http://vil.nai.com/vil/stinger) Run an updated virus scan on the system as soon as you can connect online, and don't forget to go to windowsupdate.microsoft.com (only from internet explorer) and download any critical updates as well. Now for the connection problem itself, I resolved it by first uninstalling the Internet Protocol in the properties section of whatever connection you use to get online (for DSL, my guess is it looks something like "Local Area Connection" under Network Connections in Control Pannel or on the desktop) Uninstall Internet Control Protocol, reboot in safemode. Start menu, run, type "regedit" and navigate to those same registry values given in your post - delete the winsock2 key from each and every ControlSet available. I couldn't delete these keys until I was in safemode, I think its a side effect of the virus. Reboot like normal, and go back to Network Connections, right click on your DSL connection, properties, and click install, select protocol, when presented with a list of options, pick the one that looks closest to "TCP/IP Internet Protocol" (I'm not sure on the exact wording) and let the computer do its thing. You may need to reboot, but assuming the virus is gone from your computer if that was the case, you should be back up and online after all this. I hope this helps and Good luck!


P.S. If your computer keeps shutting down by itself due to a LSASS.EXE error, unplug the network connection - that worked for me. That would be a sure fire sign of Sasser by the way.

 

[NogginBoink]

Welcome to current events.

You're getting hit with Sasser.

Apply criticual updates. Next time, don't wait 2 weeks to apply them after MS publishes them. Configure your machine to use Automatic Updates.

 

[n0cmonkey]

Originally posted by: NogginBoink
Welcome to current events.

You're getting hit with Sasser.

Apply criticual updates. Next time, don't wait 2 weeks to apply them after MS publishes them. Configure your machine to use Automatic Updates.

I thought this was last week's news.