How to get rid of "orphaned" console windows?

[WSinc]

Sometimes when a program I am debugging is aborted, it leaves the console window behind.

I can open it, and minimize and scroll it, but I can't close it, or putting anything into it.

A Ctl-C has no effect.

The only way to get rid of it is to do a reboot, otherwise it hangs around forever.

Is there any another way to close it down?

Does anyone know why this would happen?

[Glenn1]

Please view the thread dated February 19, 2010 titled: '"Stop Debugging" stops debugging but does not terminate and close debug execution window.'

Likely it is the same issue caused byWindows Automatic Update KB978037.

[IDZ_A_Intel · Accepted solution]

I have found that Process Explorer from www.sysinternals.com is better than TaskManager at identifying running processes (along with memory Working Set, I/Oetc) and I have been able to find and "kill" rogue programs when that has happened to me.

Les