GGGRRRRRRRRRRRRRR...

[sillymofo]

OK.... I'm now pissed off. I've just wiped my lappy drives and reinstalled. Already I got viri running amock. To top it off, every fcuking time I start my lappy, NT Authority is shutting my comp down about 2 mins after boot up. WTF??!?1/1/1?1/1/1/111!?!? :|

It's the same error every damn time something about "LSA Shell... " and "lsass.exe"... in temp and then another message pop up as just when the comp is shutting down, which I didn't have a chance to look at... Something about fail to open registry key. :|

Any thought?

 

[shekondar]

text
(edit: or maybe this one)

 

[jagec]

Start->Run->"shutdown -a" I believe? will temporarily halt the shutdown enough for you to run AV.

Incidentally, you DID have the laptop disconnected from the network during the whole installation procedure, and didn't reconnect until you had a firewall running, right?

 

[HonkeyDonk]

Originally posted by: jagec
Start->Run->"shutdown -e" I believe? will temporarily halt the shutdown enough for you to run AV.

Incidentally, you DID have the laptop disconnected from the network during the whole installation procedure, and didn't reconnect until you had a firewall running, right?

doesn't seem like he did.

 

[MrScott81]

Originally posted by: jagec
Start->Run->"shutdown -e" I believe? will temporarily halt the shutdown enough for you to run AV.

Incidentally, you DID have the laptop disconnected from the network during the whole installation procedure, and didn't reconnect until you had a firewall running, right?

obviously not

 

[sillymofo]

Originally posted by: jagec
Start->Run->"shutdown -e" I believe? will temporarily halt the shutdown enough for you to run AV.

Incidentally, you DID have the laptop disconnected from the network during the whole installation procedure, and didn't reconnect until you had a firewall running, right?

Will try that... but every time, AV picked up something and quarantine it. First one was windows update (navmgrd.exe) and then lsass, then lservr. The laptop connected to the network, but is on it's own (DMZ).

 

[Pepsi90919]

Originally posted by: cr4zymofo

Originally posted by: jagec
Start->Run->"shutdown -e" I believe? will temporarily halt the shutdown enough for you to run AV.

Incidentally, you DID have the laptop disconnected from the network during the whole installation procedure, and didn't reconnect until you had a firewall running, right?

Will try that... but every time, AV picked up something and quarantine it. First one was windows update (navmgrd.exe) and then lsass, then lservr. The laptop connected to the network, but is on it's own (DMZ).

why the hell?

 

[sillymofo]

Originally posted by: Pepsi90919

Originally posted by: cr4zymofo

Originally posted by: jagec
Start->Run->"shutdown -e" I believe? will temporarily halt the shutdown enough for you to run AV.

Incidentally, you DID have the laptop disconnected from the network during the whole installation procedure, and didn't reconnect until you had a firewall running, right?

Will try that... but every time, AV picked up something and quarantine it. First one was windows update (navmgrd.exe) and then lsass, then lservr. The laptop connected to the network, but is on it's own (DMZ).

why the hell?

gaming.

 

[xcript]

Originally posted by: cr4zymofo
The laptop connected to the network, but is on it's own (DMZ).

😕

 

[Blastomyces]

That's definitely the Sasser worm. Make sure you update Windows XP and you'll be fine.