cmd windows closes immediately

  • Thread starter Thread starter bamikeb
  • Start date Start date
B

bamikeb

I have a machine on my network where cmd windows do not stay open. We
discovered this by realising that the login script is not running. It
is also impossible to run batch files.

We rolled the system back to a restore point and it has run ok for a
couple of days (without reboot) but with the users logging on and off.

This morning the pc crashed and on reboot the problem is back.

This smells alot like a virus but we've scanned the machine and it
comes up clean and the installed virus software was (and is) up to date
anyway so a virus shouldn't have got onto the machine.

We've also run sfc and not found anything untoward.

Any ideas?

Cheers

Mike
 
I have a machine on my network where cmd windows do not stay open. We
discovered this by realising that the login script is not running. It
is also impossible to run batch files.

We rolled the system back to a restore point and it has run ok for a
couple of days (without reboot) but with the users logging on and off.

This morning the pc crashed and on reboot the problem is back.

This smells alot like a virus but we've scanned the machine and it
comes up clean and the installed virus software was (and is) up to date
anyway so a virus shouldn't have got onto the machine.

We've also run sfc and not found anything untoward.

Any ideas?
Click to expand...


See if you can locate a file called "cmd.com". If you do, delete this file.
It is probably residing in the system32 folder.
 
Thanks for the reply, I did actually track this problem down to a
corrupt (don't know how, virus maybe) cmd.exe file. I copied the file
from a good machine and the problem has gone away. I guess your
suggestion was not far away from finding the problem.

Regards

Mike
 
Thanks for the reply, I did actually track this problem down to a
corrupt (don't know how, virus maybe) cmd.exe file. I copied the file
from a good machine and the problem has gone away. I guess your
suggestion was not far away from finding the problem.

Regards

Mike
Click to expand...

Are you saying that sfc.exe failed to identify the corrupt
command processor?
 
I haven't actually said this but I agree that it seems odd that sfc
didn't pick this up.
The only explanation I can come up with is that we were rolling the pc
back to previous restore points which was solving the problem until the
next reboot. Maybe we ran sfc while the pc was ok after we'd restored
from a restore point and so we missed the corruption. Seems a bit
unlikely but maybe...
My bigger concern is how cmd.exe was getting overwritten/corrupted
without our antivirus (Authentium) or MS antispyware complaining.

Pc has been fine since feb 4th

Mike
 
Back
Top