Logging On

[Guest]

I had a virus go through a 2000 Server running as a Stand Alone. Now when I re-boot the computer it will come up to the logon screen and allow me to enter the User Name and Password however it then changes the cursor to an Hourglass and will not logon to the Desktop.

Any help would be appreciated

 

[Steven L Umbach]

The virus infection may require a reinstall, though you should be able to salvage
data if you need to by putting the hard drive in another computer as a
secondary/slave, scanning the drive first for viruses using that computer's virus
program. Also try booting into safe mode. --- Steve

I had a virus go through a 2000 Server running as a Stand Alone. Now when I re-boot

the computer it will come up to the logon screen and allow me to enter the User Name
and Password however it then changes the cursor to an Hourglass and will not logon to
the Desktop.

 

[Guest]

Thanks Steven

I can still access the files I need over the network so that is not a problem. I was hoping not to have to re-install (I have tried booting in safe mode - that was not successful) and wonder if yourself or others know what files 2000 Server try to load during the logon process that the virus may have corrupted and I may be able to restore using the files from another Windows 2000 Server installation

Look forward to your assistance

----- Steven L Umbach wrote: ----

The virus infection may require a reinstall, though you should be able to salvag
data if you need to by putting the hard drive in another computer as
secondary/slave, scanning the drive first for viruses using that computer's viru
program. Also try booting into safe mode. --- Stev

I had a virus go through a 2000 Server running as a Stand Alone. Now when I re-boo

the computer it will come up to the logon screen and allow me to enter the User Nam
and Password however it then changes the cursor to an Hourglass and will not logon t
the Desktop

 

[Steven L Umbach]

The files it loads vary based on computer configuration and you problem could also be
related to registry corruption, permission problems, etc. Try to use Computer
Management to connect to it to view Event Viewer on it to see if any pertinent errors
are shown that may point you in the right direction. Of course the best solution is
to reinstall, but here are a few more things to try.

Download the very neat Psexec from SysInternals which allows you to open a command
prompt on a remote computer assuming you have admin credentials. Then try running
System File Checker on your hosed computer by using the " sfc /quiet /scannow "
command being sure to put the install cdrom in the cdrom drive first. You will see a
lot of hard drive activity if it works. However you will not be able to see when it
is done, so give it at least half an hour and when it is done drive activity light
will go back to normal and then reboot to see if it helps. You can also use pslist
and pskill to view and try to kill processes on that computer remotely. If that does
not help, you may want to consider first a fast repair installation and it that does
not work an upgrade installation that will require reinstall first on the service
pack and then critical updates. See links below for related info. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;222471
http://www.sysinternals.com/ntw2k/freeware/psexec.shtml
http://www.sysinternals.com/ntw2k/freeware/pstools.shtml
http://support.microsoft.com/default.aspx?scid=kb;EN-US;238359
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175

Thanks Steven,

I can still access the files I need over the network so that is not a problem. I

was hoping not to have to re-install (I have tried booting in safe mode - that was
not successful) and wonder if yourself or others know what files 2000 Server try to
load during the logon process that the virus may have corrupted and I may be able to
restore using the files from another Windows 2000 Server installation.

 

[Guest]

Thanks Steven

----- Steven L Umbach wrote: ----

The files it loads vary based on computer configuration and you problem could also b
related to registry corruption, permission problems, etc. Try to use Compute
Management to connect to it to view Event Viewer on it to see if any pertinent error
are shown that may point you in the right direction. Of course the best solution i
to reinstall, but here are a few more things to try

Download the very neat Psexec from SysInternals which allows you to open a comman
prompt on a remote computer assuming you have admin credentials. Then try runnin
System File Checker on your hosed computer by using the " sfc /quiet /scannow
command being sure to put the install cdrom in the cdrom drive first. You will see
lot of hard drive activity if it works. However you will not be able to see when i
is done, so give it at least half an hour and when it is done drive activity ligh
will go back to normal and then reboot to see if it helps. You can also use pslis
and pskill to view and try to kill processes on that computer remotely. If that doe
not help, you may want to consider first a fast repair installation and it that doe
not work an upgrade installation that will require reinstall first on the servic
pack and then critical updates. See links below for related info. --- Stev

http://support.microsoft.com/default.aspx?scid=kb;en-us;22247
http://www.sysinternals.com/ntw2k/freeware/psexec.shtm
http://www.sysinternals.com/ntw2k/freeware/pstools.shtm
http://support.microsoft.com/default.aspx?scid=kb;EN-US;23835
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q29217

Thanks Steven

was hoping not to have to re-install (I have tried booting in safe mode - that wa
not successful) and wonder if yourself or others know what files 2000 Server try t
load during the logon process that the virus may have corrupted and I may be able t
restore using the files from another Windows 2000 Server installation