CMD.exe does not end properly

[Julian I Spring]

We recently had our NAS go down in the middle of the day.
Since then, I have seen several of our Windows 2000 Pro
systems display an End Program box when shutting down
stating that windows can not end cmd.exe. I have tried to
reinstall SP4 hoping that it would correct the issue with
the cmd.exe but that has not worked. Does anyone know how
to fix the cmd.exe?

Thanks.

 

[Matthias Tacke]

We recently had our NAS go down in the middle of the day.
Since then, I have seen several of our Windows 2000 Pro
systems display an End Program box when shutting down
stating that windows can not end cmd.exe. I have tried to
reinstall SP4 hoping that it would correct the issue with
the cmd.exe but that has not worked. Does anyone know how
to fix the cmd.exe?

Thanks.

Hello Julian,

I don't belive it's the cmd.exe itself causing the message, but may be
a batch, a program started in that shell.
I'd abort the shutdown and try to track down (with reskit tools or free
pstools from www.sysinternals.com) what program/process is (not) running
properly.

If it is in fact related to your NAS system I'd ask there.

HTH

 

[Julian I. Spring]

Thanks for the suggestion, what exactly should I be
looking for when I run the tools from sysinternals?

 

[Matthias Tacke]

Thanks for the suggestion, what exactly should I be
looking for when I run the tools from sysinternals?

It's difficult to decide from here what is unusual for your environment
and common to the pc's having used the nas. pslist for example will
show you the programs/processes running along with some time statistics
which might help identify the problem.

 

[Mark V]

Thanks for the suggestion, what exactly should I be
looking for when I run the tools from sysinternals?

Any CMD processes that have a Child Process/Thread running and no
visible window? Perhaps.