Shutdown in 5 seconds - unable to get to command prompt

  • Thread starter Thread starter Lauri
  • Start date Start date
L

Lauri

This is a repost from my response that is buried in a long
thread. This is in regard to a notebook computer running
XP Home that appears to be infected with something more
than the sasser worm. A lsass error in regard to a
password is shown right after the XP splash screen before
the opportunity to login. The system shuts down in 5
seconds - not enough time to get to a command prompt.

I really appreciate everyone's reply but the problem is
that I don't have time to get to a cmd prompt. The system
shutdown in 5 seconds - not the usual 60 seconds. (This
is not my notebook - all of my systems were patched
promptly.) I can't figure out how to get to a command
prompt if the system doesn't even log in to the desktop.
Booting in safe mode with command prompt, has the same
problem - a message about lsass and a password problem
and then it shuts off before it even goes to the command
prompt.

We tried using the recovery console from XP home cd but
the administrator's password is unknown. We are going to
try a XP boot disk and/or possibly starting a new install
from the CD and then use the repair option. I read that
may help but I am also concerned because I have seen some
knowledgebase articles that say using that option on a OEM
install may cause corrupt user data. The owner of the
notebook is desparately trying not to lose data on this
notebook. We also have the ability to hook up the
notebook harddrive to another computer and may try that
but we are not sure if we will be able to access the data
on the original notebook drive if there is indeed some
type of password problem.

Will the XP boot disk allow me to get to a command prompt
and still see the original hard drive? Any new comments
or suggestions are welcome. I will definitely let you
know how things turn out.

Lauri
 
Hello,Laurie,

Apologies your message got buried.i submitted your post
to my Anti-Virus provider,NORMAN.

Here is what they advised:

"It's Aaron here - a colleague of David's. My advice is
to download a Linux live distribution (or some other
bootable operating system), boot up, delete avserve.exe
(or avserve2.exe), reboot, enable the XP firewall, patch,
and finally run the repair tool from our website. Job
done.

If you need any more help, just ask.

Regards

NVC Technical Support

Norman Data Defense Systems (UK) Ltd
PO Box 5517
Milton Keynes
MK5 6XJ

Tel: +44 (0) 8707 448044 (Sales)
Fax: +44 (0) 8717 176999

Email: (e-mail address removed)
Web: http://www.normanuk.com

Hope this helps,

There is some other good advice in the original
thread,too.Everyone went all out to help.Sorry it became
so difficult to track.

Sadie
 
Thank you. We will give it a try and I will let you know
how it works out. The only thing is that this notebook
has a external floppy drive and we are not sure yet
whether it is bootable.
 
Lauri said:
This is a repost from my response that is buried in a long
thread. This is in regard to a notebook computer running
XP Home that appears to be infected with something more
than the sasser worm. A lsass error in regard to a
password is shown right after the XP splash screen before
the opportunity to login. The system shuts down in 5
seconds - not enough time to get to a command prompt.

I really appreciate everyone's reply but the problem is
that I don't have time to get to a cmd prompt. The system
shutdown in 5 seconds - not the usual 60 seconds. (This
is not my notebook - all of my systems were patched
promptly.) I can't figure out how to get to a command
prompt if the system doesn't even log in to the desktop.
Booting in safe mode with command prompt, has the same
problem - a message about lsass and a password problem
and then it shuts off before it even goes to the command
prompt.

We tried using the recovery console from XP home cd but
the administrator's password is unknown. We are going to
try a XP boot disk and/or possibly starting a new install
from the CD and then use the repair option. I read that
may help but I am also concerned because I have seen some
knowledgebase articles that say using that option on a OEM
install may cause corrupt user data. The owner of the
notebook is desparately trying not to lose data on this
notebook. We also have the ability to hook up the
notebook harddrive to another computer and may try that
but we are not sure if we will be able to access the data
on the original notebook drive if there is indeed some
type of password problem.

Will the XP boot disk allow me to get to a command prompt
and still see the original hard drive? Any new comments
or suggestions are welcome. I will definitely let you
know how things turn out.

Lauri

A friend of mine used an XP disk because she didn't want to use her OEM restore CD's because a whole fresh system would be installed and she didn't want to lose her data. She did an install repair but then it wouldn't boot. The solution, in her case, was to insert the last OEM restore CD in the series and type: fdisk /mbr
It worked.
Perhaps you could explore the OEM restore CDs on another computer and see if any contain a similar function before you try this method.

I don't have any other ideas but then I'm no expert.

treehugger
 
dunno if this will work or not but
when you get the shutdown warning
ctrl alt del
hit new task
type shutdown /a and return
im not rebooting my pc to see if ctrl alt del works at that stage of the
boot
sequence or not but its worth a go

ceedee



Lauri said:
This is a repost from my response that is buried in a long
thread. This is in regard to a notebook computer running
XP Home that appears to be infected with something more
than the sasser worm. A lsass error in regard to a
password is shown right after the XP splash screen before
the opportunity to login. The system shuts down in 5
seconds - not enough time to get to a command prompt.

I really appreciate everyone's reply but the problem is
that I don't have time to get to a cmd prompt. The system
shutdown in 5 seconds - not the usual 60 seconds. (This
is not my notebook - all of my systems were patched
promptly.) I can't figure out how to get to a command
prompt if the system doesn't even log in to the desktop.
Booting in safe mode with command prompt, has the same
problem - a message about lsass and a password problem
and then it shuts off before it even goes to the command
prompt.

We tried using the recovery console from XP home cd but
the administrator's password is unknown. We are going to
try a XP boot disk and/or possibly starting a new install
from the CD and then use the repair option. I read that
may help but I am also concerned because I have seen some
knowledgebase articles that say using that option on a OEM
install may cause corrupt user data. The owner of the
notebook is desparately trying not to lose data on this
notebook. We also have the ability to hook up the
notebook harddrive to another computer and may try that
but we are not sure if we will be able to access the data
on the original notebook drive if there is indeed some
type of password problem.

Will the XP boot disk allow me to get to a command prompt
and still see the original hard drive? Any new comments
or suggestions are welcome. I will definitely let you
know how things turn out.

Lauri

A friend of mine used an XP disk because she didn't want to use her OEM
restore CD's because a whole fresh system would be installed and she didn't
want to lose her data. She did an install repair but then it wouldn't boot.
The solution, in her case, was to insert the last OEM restore CD in the
series and type: fdisk /mbr
It worked.
Perhaps you could explore the OEM restore CDs on another computer and see if
any contain a similar function before you try this method.

I don't have any other ideas but then I'm no expert.

treehugger
 
ceedee said:
dunno if this will work or not but
when you get the shutdown warning
ctrl alt del
hit new task
type shutdown /a and return
im not rebooting my pc to see if ctrl alt del works at that stage of the
boot
sequence or not but its worth a go

ceedee





A friend of mine used an XP disk because she didn't want to use her OEM
restore CD's because a whole fresh system would be installed and she didn't
want to lose her data. She did an install repair but then it wouldn't boot.
The solution, in her case, was to insert the last OEM restore CD in the
series and type: fdisk /mbr
It worked.
Perhaps you could explore the OEM restore CDs on another computer and see if
any contain a similar function before you try this method.

I don't have any other ideas but then I'm no expert.

treehugger
Lauri,
What ceedee describes above *does* work. My brother has just helped someone to do this where the computer was shutting down before the login. So, Ctrl, Alt + Delete brings up the task manager then "File" from the menu then "New Task (Run)" and type shutdown -a
You can keep on adding tasks such as cmd, regedit or services.msc in the same way.

treehugger
 
Back
Top