Visual Studio debugging console sometimes remains open and cannot be closed

Question

EDIT # 3: Microsoft has released a fix for this issue, which is available here . I did not have time to check it out, but I, those who want, can leave their feedback here!

Sometimes, when I start an application from Visual Studio, it crashes or I stop it using the stop button in the debug menu (Debug-> Stop Debugging (Shift-F5)), the application console remains open ... and never closes . I can’t close it by clicking the “x” button in the upper right corner. I can not kill the process, because it is not even specified in taskmgr.

I saw that this problem has been documented in various places on the Internet, but there is no solution yet.

I am running Windows XP SP3 using visual studio 2008 w / SP1.

1- What could be causing this?
2- Is there a fix?

Many thanks.

x

EDIT: The MyApp.vshost.exe process does not close, and closing the visual studio also does not close the console. Even worse, if I try to restart the computer, the windows will hang and never close, I need to make a forced close.

EDIT # 2: (from Brad Sullivan, Program Manager - Visual Studio Debugger March 2)

[...] this problem is most likely not in Visual Studio, since it also occurs in scenarios where Visual Studio is missing. We are in the process of transferring our investigation to the Windows Servicing team.

But for now, uninstalling the KB978037 update and related files seems to have worked.

Answer 1

Microsoft has released a fix for this issue, which is available here . I did not have time to check it out, but I, those who want, can leave their feedback here!

Answer 2

This is a bug that appeared in security update KB978037. Return this update and you will return to normal.

Also see here:

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

Answer 3

There are several things that can happen here. Try closing the next process and see which one, if any, close the console application.

• Hosting process: usually called YourExecutable.vshost.exe
• Visual studio

If closing the hosting process fixes the problem, then one quick job is to turn off the hosting process itself.

Right click on the project → Properties → Debugging → Uncheck the hosting process

If closing Visual Studio fixes the problem, it may cause an error in Visual Studio. Please indicate a connection error.

http://connect.microsoft.com

Answer 4

The Visual Studio debugging team has already acknowledged these issues on its blog. check the url below.

http://blogs.msdn.com/debugger/archive/2010/03/11/help-my-console-windows-won-t-go-away.aspx