Sasser Disaster

[Guest]

Archived from groups: microsoft.public.win2000.file_system (More info?)

The stupidest thing I ever did. I was trying to remove
the sasser virus manually because stinger could not find
it but my machine kept rebooting. In my zeal, I started
renaming all of hte lsass.exe files. I got to the last
one and when I rebooted windows did not come up. Now I
cannot boot in safe mode, safe mode with command prompt,
regular bootup or anything. I get to the windows is
starting up progress bar, it goes to the end and nothing
else happens. someone please help. thanks for any
suggestions.

 

[Guest]

Archived from groups: microsoft.public.win2000.file_system (More info?)

Try renaming them back from the recovery console.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"super77cab" wrote:
| The stupidest thing I ever did. I was trying to remove
| the sasser virus manually because stinger could not find
| it but my machine kept rebooting. In my zeal, I started
| renaming all of hte lsass.exe files. I got to the last
| one and when I rebooted windows did not come up. Now I
| cannot boot in safe mode, safe mode with command prompt,
| regular bootup or anything. I get to the windows is
| starting up progress bar, it goes to the end and nothing
| else happens. someone please help. thanks for any
| suggestions.

 

[Guest]

Archived from groups: microsoft.public.win2000.file_system (More info?)

Great idea but I can't even get to a dos prompt. I have
NTFSpro available but did not have it today when I was at
the computer. Got any ideas on how to get to a dos prompt
in W2K?
>-----Original Message-----
>Try renaming them back from the recovery console.
>
>--
>Regards,
>
>Dave Patrick ....Please no email replies - reply in
newsgroup.
>Microsoft Certified Professional
>Microsoft MVP [Windows]
>http://www.microsoft.com/protect
>
>
>"super77cab" wrote:
>| The stupidest thing I ever did. I was trying to remove
>| the sasser virus manually because stinger could not
find
>| it but my machine kept rebooting. In my zeal, I started
>| renaming all of hte lsass.exe files. I got to the last
>| one and when I rebooted windows did not come up. Now I
>| cannot boot in safe mode, safe mode with command
prompt,
>| regular bootup or anything. I get to the windows is
>| starting up progress bar, it goes to the end and
nothing
>| else happens. someone please help. thanks for any
>| suggestions.
>
>
>.
>

 

[Guest]

Archived from groups: microsoft.public.win2000.file_system (More info?)

I am not sure how to use the recovery console
>-----Original Message-----
>Try renaming them back from the recovery console.
>
>--
>Regards,
>
>Dave Patrick ....Please no email replies - reply in
newsgroup.
>Microsoft Certified Professional
>Microsoft MVP [Windows]
>http://www.microsoft.com/protect
>
>
>"super77cab" wrote:
>| The stupidest thing I ever did. I was trying to remove
>| the sasser virus manually because stinger could not
find
>| it but my machine kept rebooting. In my zeal, I started
>| renaming all of hte lsass.exe files. I got to the last
>| one and when I rebooted windows did not come up. Now I
>| cannot boot in safe mode, safe mode with command
prompt,
>| regular bootup or anything. I get to the windows is
>| starting up progress bar, it goes to the end and
nothing
>| else happens. someone please help. thanks for any
>| suggestions.
>
>
>.
>

 

[Guest]

Archived from groups: microsoft.public.win2000.file_system (More info?)

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks.
Press ENTER at the "Setup Notification" screen. Press R to repair a Windows
2000 installation, and then press C to use the Recovery Console. The
Recovery Console then prompts you for the administrator password. If you do
not have the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Once the password has been
validated, you have full access to the Recovery Console, but limited access
to the hard disk. You can only access the following folders on your
computer: %systemroot% and %windir%

The one that matters is in
C\winnt\system32

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


<anonymous@discussions.microsoft.com> wrote:
|I am not sure how to use the recovery console

 

[Guest]

Archived from groups: microsoft.public.win2000.file_system (More info?)

>-----Original Message-----
>To start the Recovery Console, start the computer from
the Windows 2000
>Setup CD or the Windows 2000 Setup floppy disks. If you
do not have Setup
>floppy disks and your computer cannot start from the
Windows 2000 Setup CD,
>use another Windows 2000-based computer to create the
Setup floppy disks.
>Press ENTER at the "Setup Notification" screen. Press R
to repair a Windows
>2000 installation, and then press C to use the Recovery
Console. The
>Recovery Console then prompts you for the administrator
password. If you do
>not have the correct password, Recovery Console does not
allow access to the
>computer. If an incorrect password is entered three
times, the Recovery
>Console quits and restarts the computer. Once the
password has been
>validated, you have full access to the Recovery Console,
but limited access
>to the hard disk. You can only access the following
folders on your
>computer: %systemroot% and %windir%
>
>The one that matters is in
>C\winnt\system32
>
>--
>Regards,
>
>Dave Patrick ....Please no email replies - reply in
newsgroup.
>Microsoft Certified Professional
>Microsoft MVP [Windows]
>http://www.microsoft.com/protect
>
>
><anonymous@discussions.microsoft.com> wrote:
>|I am not sure how to use the recovery console
>
>
>.
>Thanks, I'll try that.