G
Guest
Hello -
I have looked for years for any hint of a suggestion as to the cause of this
issue, and have only found it mentioned cursorily in some older posts.
I use the cmd shell as much as possible to execute commands both locally and
remotely, nslookups, pings, iisresets, and for telnet. Yes, I know that
hyperterminal is a better telnet client, but cmd is easier to type into start
I always open the cmd prompt from start >> run, or from a shortcut, rather
than, for instance, typing nslooukp at start >> run, and having the cmd
prompt automatically open.
The issue that occasionally ensues is one that I've noticed ever since win2k
with no service packs. When I have completed the command line tasks that I
would have just gone through, and have come back to a blinking cursor next to
the c:\> prompt, the window will not close, and then hangs such that it
accepts no more user input.
When I look into taskman, it shows no cmd.exe process running. The cursor
blinks, but I cannot move it by any keystroke. Efforts to close the window
by clicking on the X button in the upper right hand corner are unrewarded. I
assumed at one point that it was because something hung within explorer, so I
killed and restarted explorer.exe from taskman, to no avail.
The end result is that I can not shut down the computer after this happens.
I try doing start >> shut down - the computer prompts me to choose the usual
things, but then will not actually shut down. Then, if I attempt to launch
any more apps, it tells me that they won't open because the workstationg is
shutting down. I've tried every programmatic way to shut down the machine
after this, with the exception of running an iisreset /reboot (which i just
thought of now), but that won't help on the machines on which this has
occurred which do not have IIS installed.
I end up forcing a power-off shutoff, which is obviously not advisable. The
main problem with this issue is that it's inconsistently expressed by the OS,
and doesn't leave any real traces because the process that opens the window
in the first place (cmd.exe) is already long dead by this time. It's kind of
like trying to kill an explorer window that's open and not responding without
killing the main explorer process itself, when you don't have folders opening
in thier own process.
The next time it happens, what should I try, and is there any log or output
which I should save for troubleshooting purposes?
Thanks...
- Eric McWhorter
I have looked for years for any hint of a suggestion as to the cause of this
issue, and have only found it mentioned cursorily in some older posts.
I use the cmd shell as much as possible to execute commands both locally and
remotely, nslookups, pings, iisresets, and for telnet. Yes, I know that
hyperterminal is a better telnet client, but cmd is easier to type into start
I always open the cmd prompt from start >> run, or from a shortcut, rather
than, for instance, typing nslooukp at start >> run, and having the cmd
prompt automatically open.
The issue that occasionally ensues is one that I've noticed ever since win2k
with no service packs. When I have completed the command line tasks that I
would have just gone through, and have come back to a blinking cursor next to
the c:\> prompt, the window will not close, and then hangs such that it
accepts no more user input.
When I look into taskman, it shows no cmd.exe process running. The cursor
blinks, but I cannot move it by any keystroke. Efforts to close the window
by clicking on the X button in the upper right hand corner are unrewarded. I
assumed at one point that it was because something hung within explorer, so I
killed and restarted explorer.exe from taskman, to no avail.
The end result is that I can not shut down the computer after this happens.
I try doing start >> shut down - the computer prompts me to choose the usual
things, but then will not actually shut down. Then, if I attempt to launch
any more apps, it tells me that they won't open because the workstationg is
shutting down. I've tried every programmatic way to shut down the machine
after this, with the exception of running an iisreset /reboot (which i just
thought of now), but that won't help on the machines on which this has
occurred which do not have IIS installed.
I end up forcing a power-off shutoff, which is obviously not advisable. The
main problem with this issue is that it's inconsistently expressed by the OS,
and doesn't leave any real traces because the process that opens the window
in the first place (cmd.exe) is already long dead by this time. It's kind of
like trying to kill an explorer window that's open and not responding without
killing the main explorer process itself, when you don't have folders opening
in thier own process.
The next time it happens, what should I try, and is there any log or output
which I should save for troubleshooting purposes?
Thanks...
- Eric McWhorter