Hello. I am having an issue with the Windows command prompt window staying
open even when there are no cmd.exe process running in the back ground. In my
job it is often necessary for me to have multiple instances of this open.
What happens is that I will either close the window by clicking the "X" or I
will type exit. After doing that, the process "cmd.exe" will close but the
window will stay open. I have tried looking for the processes with Process
Explorer but find nothing. As I am typing this, I have 4(four) of these
windows locked open. I am able to minimize them and maximize them but not
close them. Any Ideas?

The date and time was 2/7/2008 12:41 PM, and on a whim, Dan pounded out
on the keyboard:

> Hello. I am having an issue with the Windows command prompt window staying
> open even when there are no cmd.exe process running in the back ground. In my
> job it is often necessary for me to have multiple instances of this open.
> What happens is that I will either close the window by clicking the "X" or I
> will type exit. After doing that, the process "cmd.exe" will close but the
> window will stay open. I have tried looking for the processes with Process
> Explorer but find nothing. As I am typing this, I have 4(four) of these
> windows locked open. I am able to minimize them and maximize them but not
> close them. Any Ideas?

Hi Dan,

Does it make a difference whether you're running full screen or not
(alt-Enter), and then typing exit? Are you unable to type anything in
the window after you click the X or type exit? How are you launching
it, by a created shortcut or Windows key-R? Does the same thing happen
in Safe Mode?

These kinds of things are hard to t-shoot without being able to replicate.

--
Terry R.

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.

"Terry R." wrote:

> The date and time was 2/7/2008 12:41 PM, and on a whim, Dan pounded out
> on the keyboard:
>
> > Hello. I am having an issue with the Windows command prompt window staying
> > open even when there are no cmd.exe process running in the back ground. In my
> > job it is often necessary for me to have multiple instances of this open.
> > What happens is that I will either close the window by clicking the "X" or I
> > will type exit. After doing that, the process "cmd.exe" will close but the
> > window will stay open. I have tried looking for the processes with Process
> > Explorer but find nothing. As I am typing this, I have 4(four) of these
> > windows locked open. I am able to minimize them and maximize them but not
> > close them. Any Ideas?
>
> Hi Dan,
>
> Does it make a difference whether you're running full screen or not
> (alt-Enter), and then typing exit? Are you unable to type anything in
> the window after you click the X or type exit? How are you launching
> it, by a created shortcut or Windows key-R? Does the same thing happen
> in Safe Mode?
>
> These kinds of things are hard to t-shoot without being able to replicate.
>
> --
> Terry R.
>
> ***Reply Note***
> Anti-spam measures are included in my email address.
> Delete NOSPAM from the email address after clicking Reply.
>
Hi Terry,

Generally I launch via Window Key-R but sometimes with shortcut. I don't run
them in full screen mode and I am unable to type in them. Safe Mode status is
unknown. unfortunately the issue doesn't occur every time. I may have 6
prompt windows open and 1 or 2 won't close sometimes, and other time they
will all close. Also I have to manually shut down the PC when this happens.
If I try to log off, shut down, or reboot, the system hangs and then I have
to hold in the power button to turn it off.

"Dan" <Dan@discussions.microsoft.com> wrote in message
news:753E6D68-3944-4419-AFD7-69B2D902D2CC@microsoft.com...
> Hello. I am having an issue with the Windows command prompt window staying
> open even when there are no cmd.exe process running in the back ground. In
> my
> job it is often necessary for me to have multiple instances of this open.
> What happens is that I will either close the window by clicking the "X" or
> I
> will type exit. After doing that, the process "cmd.exe" will close but the
> window will stay open. I have tried looking for the processes with Process
> Explorer but find nothing. As I am typing this, I have 4(four) of these
> windows locked open. I am able to minimize them and maximize them but not
> close them. Any Ideas?

My first step would be to ensure that I'm really executing
c:\windows\system32\cmd.exe
and not some other program that happens to call itself "cmd" - which is
often the case with malware. To do so you must create a new shortcut
that specifies the full path.

"Pegasus (MVP)" wrote:

>
> "Dan" <Dan@discussions.microsoft.com> wrote in message
> news:753E6D68-3944-4419-AFD7-69B2D902D2CC@microsoft.com...
> > Hello. I am having an issue with the Windows command prompt window staying
> > open even when there are no cmd.exe process running in the back ground. In
> > my
> > job it is often necessary for me to have multiple instances of this open.
> > What happens is that I will either close the window by clicking the "X" or
> > I
> > will type exit. After doing that, the process "cmd.exe" will close but the
> > window will stay open. I have tried looking for the processes with Process
> > Explorer but find nothing. As I am typing this, I have 4(four) of these
> > windows locked open. I am able to minimize them and maximize them but not
> > close them. Any Ideas?
>
> My first step would be to ensure that I'm really executing
> c:\windows\system32\cmd.exe
> and not some other program that happens to call itself "cmd" - which is
> often the case with malware. To do so you must create a new shortcut
> that specifies the full path.
>
>
>

Here is the Path : %SystemRoot%\system32\cmd.exe

The date and time was 2/7/2008 1:28 PM, and on a whim, Dan pounded out
on the keyboard:

>
> "Terry R." wrote:
>
>> Does it make a difference whether you're running full screen or not
>> (alt-Enter), and then typing exit? Are you unable to type anything in
>> the window after you click the X or type exit? How are you launching
>> it, by a created shortcut or Windows key-R? Does the same thing happen
>> in Safe Mode?
>>
>> These kinds of things are hard to t-shoot without being able to replicate.
>>
>>
> Hi Terry,
>
> Generally I launch via Window Key-R but sometimes with shortcut. I don't run
> them in full screen mode and I am unable to type in them. Safe Mode status is
> unknown. unfortunately the issue doesn't occur every time. I may have 6
> prompt windows open and 1 or 2 won't close sometimes, and other time they
> will all close. Also I have to manually shut down the PC when this happens.
> If I try to log off, shut down, or reboot, the system hangs and then I have
> to hold in the power button to turn it off.

Can you test it for a while in Safe Mode? Sounds like something is
causing cmd to hang, and Safe Mode would be a start. Are you sure that
whatever you're doing in all the windows has completed before closing
them? What requires the use of multiple windows rather than just using
one? Does it happen with only one window open? Are you using switches
with your commands?

--
Terry R.

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.

"Dan" wrote:

> Hello. I am having an issue with the Windows command prompt window staying
> open even when there are no cmd.exe process running in the back ground. In my
> job it is often necessary for me to have multiple instances of this open.
> What happens is that I will either close the window by clicking the "X" or I
> will type exit. After doing that, the process "cmd.exe" will close but the
> window will stay open. I have tried looking for the processes with Process
> Explorer but find nothing. As I am typing this, I have 4(four) of these
> windows locked open. I am able to minimize them and maximize them but not
> close them. Any Ideas?

Anyone else out there with any ideas?

Try a clean boot to see if it is a Windows problem or caused by a third
party app.

"Dan" <Dan@discussions.microsoft.com> wrote in message
news:FFD07A84-954D-47B0-B7ED-5EA35BA8E18D@microsoft.com...
>
>
> "Dan" wrote:
>
>> Hello. I am having an issue with the Windows command prompt window
>> staying
>> open even when there are no cmd.exe process running in the back ground.
>> In my
>> job it is often necessary for me to have multiple instances of this open.
>> What happens is that I will either close the window by clicking the "X"
>> or I
>> will type exit. After doing that, the process "cmd.exe" will close but
>> the
>> window will stay open. I have tried looking for the processes with
>> Process
>> Explorer but find nothing. As I am typing this, I have 4(four) of these
>> windows locked open. I am able to minimize them and maximize them but not
>> close them. Any Ideas?
>
> Anyone else out there with any ideas?

The date and time was 2/8/2008 10:37 AM, and on a whim, Dan pounded out
on the keyboard:

>
> "Dan" wrote:
>
>> Hello. I am having an issue with the Windows command prompt window staying
>> open even when there are no cmd.exe process running in the back ground. In my
>> job it is often necessary for me to have multiple instances of this open.
>> What happens is that I will either close the window by clicking the "X" or I
>> will type exit. After doing that, the process "cmd.exe" will close but the
>> window will stay open. I have tried looking for the processes with Process
>> Explorer but find nothing. As I am typing this, I have 4(four) of these
>> windows locked open. I am able to minimize them and maximize them but not
>> close them. Any Ideas?
>
> Anyone else out there with any ideas?

Did you try any of my last suggestions? If so, I missed your response.

--
Terry R.

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.

"Terry R." wrote:

> The date and time was 2/8/2008 10:37 AM, and on a whim, Dan pounded out
> on the keyboard:
>
> >
> > "Dan" wrote:
> >
> >> Hello. I am having an issue with the Windows command prompt window staying
> >> open even when there are no cmd.exe process running in the back ground. In my
> >> job it is often necessary for me to have multiple instances of this open.
> >> What happens is that I will either close the window by clicking the "X" or I
> >> will type exit. After doing that, the process "cmd.exe" will close but the
> >> window will stay open. I have tried looking for the processes with Process
> >> Explorer but find nothing. As I am typing this, I have 4(four) of these
> >> windows locked open. I am able to minimize them and maximize them but not
> >> close them. Any Ideas?
> >
> > Anyone else out there with any ideas?
>
> Did you try any of my last suggestions? If so, I missed your response.
>
> --
> Terry R.
>
> ***Reply Note***
> Anti-spam measures are included in my email address.
> Delete NOSPAM from the email address after clicking Reply.
>

Sorry, I did miss your last response. In answer, running in safe mode would
be unlikely at best. I suppose I could stay late or try on Sunday. Yes, I
work in voice equipment and I always exit after I have left the the equipment
and am sitting at a command prompt. Sometime it happens with a single window
open but I'm not sure if it's just due to the law of averages that I only see
it single windows infrequently. I am often required in the couse of
troubleshooting an issue with the equipment to have multiple windows open to
trace down the issue. No switches, standard command prompt.

"Colin Barnhorst" wrote:

> Try a clean boot to see if it is a Windows problem or caused by a third
> party app.
>
> "Dan" <Dan@discussions.microsoft.com> wrote in message
> news:FFD07A84-954D-47B0-B7ED-5EA35BA8E18D@microsoft.com...
> >
> >
> > "Dan" wrote:
> >
> >> Hello. I am having an issue with the Windows command prompt window
> >> staying
> >> open even when there are no cmd.exe process running in the back ground.
> >> In my
> >> job it is often necessary for me to have multiple instances of this open.
> >> What happens is that I will either close the window by clicking the "X"
> >> or I
> >> will type exit. After doing that, the process "cmd.exe" will close but
> >> the
> >> window will stay open. I have tried looking for the processes with
> >> Process
> >> Explorer but find nothing. As I am typing this, I have 4(four) of these
> >> windows locked open. I am able to minimize them and maximize them but not
> >> close them. Any Ideas?
> >
> > Anyone else out there with any ideas?
>

Continues to happen even after a fresh boot.

If by "fresh" boot you mean a clean boot via msconfig then while in a clean
boot state could you tell which process was likely to be keeping the windows
open? I was suggesting that you use a clean boot as a diagnostic tool.

"Dan" <Dan@discussions.microsoft.com> wrote in message
news:7D3563E1-F234-468E-A201-B446C38442B8@microsoft.com...
>
>
> "Colin Barnhorst" wrote:
>
>> Try a clean boot to see if it is a Windows problem or caused by a third
>> party app.
>>
>> "Dan" <Dan@discussions.microsoft.com> wrote in message
>> news:FFD07A84-954D-47B0-B7ED-5EA35BA8E18D@microsoft.com...
>> >
>> >
>> > "Dan" wrote:
>> >
>> >> Hello. I am having an issue with the Windows command prompt window
>> >> staying
>> >> open even when there are no cmd.exe process running in the back
>> >> ground.
>> >> In my
>> >> job it is often necessary for me to have multiple instances of this
>> >> open.
>> >> What happens is that I will either close the window by clicking the
>> >> "X"
>> >> or I
>> >> will type exit. After doing that, the process "cmd.exe" will close but
>> >> the
>> >> window will stay open. I have tried looking for the processes with
>> >> Process
>> >> Explorer but find nothing. As I am typing this, I have 4(four) of
>> >> these
>> >> windows locked open. I am able to minimize them and maximize them but
>> >> not
>> >> close them. Any Ideas?
>> >
>> > Anyone else out there with any ideas?
>>
>
> Continues to happen even after a fresh boot.

The date and time was 2/8/2008 12:00 PM, and on a whim, Dan pounded out
on the keyboard:

>
> "Terry R." wrote:
>
>> The date and time was 2/8/2008 10:37 AM, and on a whim, Dan pounded out
>> on the keyboard:
>>
>>> "Dan" wrote:
>>>
>>>> Hello. I am having an issue with the Windows command prompt window staying
>>>> open even when there are no cmd.exe process running in the back ground. In my
>>>> job it is often necessary for me to have multiple instances of this open.
>>>> What happens is that I will either close the window by clicking the "X" or I
>>>> will type exit. After doing that, the process "cmd.exe" will close but the
>>>> window will stay open. I have tried looking for the processes with Process
>>>> Explorer but find nothing. As I am typing this, I have 4(four) of these
>>>> windows locked open. I am able to minimize them and maximize them but not
>>>> close them. Any Ideas?
>>> Anyone else out there with any ideas?
>> Did you try any of my last suggestions? If so, I missed your response.
>>
>> --
>> Terry R.
>>
>> ***Reply Note***
>> Anti-spam measures are included in my email address.
>> Delete NOSPAM from the email address after clicking Reply.
>>
>
> Sorry, I did miss your last response. In answer, running in safe mode would
> be unlikely at best. I suppose I could stay late or try on Sunday. Yes, I
> work in voice equipment and I always exit after I have left the the equipment
> and am sitting at a command prompt. Sometime it happens with a single window
> open but I'm not sure if it's just due to the law of averages that I only see
> it single windows infrequently. I am often required in the couse of
> troubleshooting an issue with the equipment to have multiple windows open to
> trace down the issue. No switches, standard command prompt.

I think the only way you can t-shoot this is to eliminate anything that
might be causing the issue. Safe Mode would do that. Do you have the
latest display driver? Buggy drivers cause weird things to happen.
Safe Mode would bypass that also.

--
Terry R.

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.

Dan;524652 Wrote:
> Hello. I am having an issue with the Windows command prompt window
> staying
> open even when there are no cmd.exe process running in the back ground.
> In my
> job it is often necessary for me to have multiple instances of this
> open.
> What happens is that I will either close the window by clicking the "X"
> or I
> will type exit. After doing that, the process "cmd.exe" will close but
> the
> window will stay open. I have tried looking for the processes with
> Process
> Explorer but find nothing. As I am typing this, I have 4(four) of these
>
> windows locked open. I am able to minimize them and maximize them but
> not
> close them. Any Ideas?

Dan, I'm hoping you found a solution to this. I am having the same
issue and have been having it for some time. I use Command Prompts
frequently for remote connectivity over slow connections. It doesn't
happen as often for me but probably once every couple weeks and the only
way to get rid of it is to hard boot. I've tried only using the exit
command and that didn't work, I also tried just hitting X and no luck
there. I've scanned my PC for everything and no luck there either. I
have noticed that it seems to only have occured when I have multiple
cmd's open but I've only seen it where one session stays up all the
others close fine. I can even open another prmopt and close it fine. I
haven't tried the safe mode suggestion cause I can't reproduce it. It
just seems to happen randomly. If/when I can reproduce it I will post
that here. I think if I was able to reproduce it though I could figure
out a solution. The system I'm having the issues on is XP and fully
patched and having no other issues.

Hi All,

Like Dan and Yonder, I too have had this issue for over 3 years now.

This is not a graphics, driver, memory, safemode, yada blah and etc
issue (not to be disrespectful) but is rather an issue on how a telnet
session termination is handled.

I am an experienced and professional IT person and have used a few
different latops and desktop systems in the last 3 years - all of which
show the same problem when it does 'by chance' happen. These systems
differ in make and configuration (note: even my colleague has had this
happen in his WinXP vmware guest). What we need is a 'Microsoft' IT
expert to track this down.

I work with networking gear and as such have several 'cmd.exe' windows
open with a telnet session established to remote devices. And this is
when the issue 'can' occur. The issue is not reproducible all the time
but happens when a user (in this case me) is logged in to a remote
device via telnet.

If the telnet session is terminated via a remote device timeout (as is
the case with cisco gear for security reasons) the 'cmd.exe has a good
chance of hanging - not always - no way to predict when. Then the only
way to close the window (and subsequently turn off the computer b/c as
mentioned it won't shut down) is to power off the machine via holding
the power button. The machine operated fine aside from not being able to
close the window or shutdown the machine. (so to summarize, open cmd.exe
window, issue a telnet to remote device. Login. Do some work, turn and
talk to someone wanting to discuss how they painted the deck on the
weekend, turn back to the computer to find the session has expired do to
a lack of activity. type exit.. nothing.. click the 'x' and nothing.
Cllick start shutdown.. processes start to close but no full shutdown
happens.)

I have tired waiting for MS to release a hotfix as I just don't see it
coming. I find it hard to beleive that this hasn't been called into MS
or fixed yet. Strange!!!

Any MS experts out there that can shed some light on why this session
termination is not handled properly and is causing this to happen?

Cheers!