CODEWITHSUNDEEP
debuggingvisual-studio-2005consoletaskmanager
LeopardSkinPillBoxHat
LeopardSkinPillBoxHat

Reputation: 29421

Console windows that cannot be killed by closing or via Task Manager

When I run a test harness through the Visual Studio 2005 debugger, it creates a console window every time I run it.

In the past, the console window would close automatically when the test harness process terminated, but now I'm finding that the console window is hanging around afterwards.

After the test harness terminates:

So I cannot seem to kill these console windows.

Does anyone know:

  1. How these console windows can exist without a managing process?
  2. How can I can kill these console windows?

Rebooting is obviously an option, but there must be another way.

Upvotes: 5

Views: 2722

Answers (2)

an0nym0usc0ward
an0nym0usc0ward

Reputation: 1227

In Windows, "Administrator" is not the highest level user. Some processes/files/directories are only accessible by the "SYSTEM" user. See: http://hackspc.com/how-to-become-the-system-user-in-windows-xp/

This may be the reason why it is unkillable.

Upvotes: -3

Ivan
Ivan

Reputation: 1796

It's a known bug in windows, introduced with KB978037 security patch.

You can find out more here http://blogs.msdn.com/debugger/archive/2010/03/11/help-my-console-windows-won-t-go-away.aspx

and here http://social.msdn.microsoft.com/Forums/en/vsdebug/thread/e6d4a4f5-7002-401a-90e1-6174d7f9e3ca

Upvotes: 5

Related Questions