none
VS 2008 debugging: console window will not close when debugging stopped

    Question

  • I am debugging C++ code in VS 2008; when I stop debugging the console window remains open and cannot be killed. 
    An active task is shown in the task manager but no process. Clicking on the window 'x', hitting "end task' in the
    task manager, or exiting VS does not kill it. If I debug again, it opens another window which again can not be killed.
    I installed the current windows updates this morning, after which this problem appeared. I have uninstalled the updates but
    have not fixed the problem. I also installed the updates on my laptop but it does not have this problem.

    VS 2008 9.0.21022 Professional edition
    .NET framework 3.5 SP1
    Windows XP Pro SP3

    Thursday, February 11, 2010 8:20 PM

Answers


  • Maybe I wasn't clear, but the problem isn't that the bitmap of the console window remains drawn on the desktop. It's still running  as a task--I can minimize the window, it's listed in the task manager, but I can't kill it. Each time I stop a debug instead of letting it complete, I get another zombie window. If the debug runs to the end of the program, the window is closed.

    I restarted my computer probably 6 times yesterday. Restarting the computer does not kill the windows either--I had to power cycle the computer to get it to shut down.

    My laptop is doing the same thing, I was mistaken yesterday.

    Adjusting the screen resolution does nothing, obviously.

    Maybe this is related to the  BSOD problems reported with Tuesday's updates?
    http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/73cea559-ebbd-4274-96bc-e292b69f2fd1/#e9b28c45-635c-4adf-8d24-817bf39c207b

    • Proposed as answer by MikeTheTv Monday, February 15, 2010 10:51 AM
    • Marked as answer by Roahn Luo Tuesday, February 16, 2010 4:16 AM
    Friday, February 12, 2010 1:09 PM

All replies

  • Hello cmcglone,

    Thanks for posting the issue here. I'm sorry to hear that there is an issue for you. But if I'm in your shoes, I will:
    1. Adjust the Screen Resolution and see if it disappears
    2. Restart my computer again

    Please have a try and tell me the result,
    Best regards
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback, please tell us.
    Welcome to the All-In-One Code Framework!
    Friday, February 12, 2010 7:00 AM

  • Maybe I wasn't clear, but the problem isn't that the bitmap of the console window remains drawn on the desktop. It's still running  as a task--I can minimize the window, it's listed in the task manager, but I can't kill it. Each time I stop a debug instead of letting it complete, I get another zombie window. If the debug runs to the end of the program, the window is closed.

    I restarted my computer probably 6 times yesterday. Restarting the computer does not kill the windows either--I had to power cycle the computer to get it to shut down.

    My laptop is doing the same thing, I was mistaken yesterday.

    Adjusting the screen resolution does nothing, obviously.

    Maybe this is related to the  BSOD problems reported with Tuesday's updates?
    http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/73cea559-ebbd-4274-96bc-e292b69f2fd1/#e9b28c45-635c-4adf-8d24-817bf39c207b

    • Proposed as answer by MikeTheTv Monday, February 15, 2010 10:51 AM
    • Marked as answer by Roahn Luo Tuesday, February 16, 2010 4:16 AM
    Friday, February 12, 2010 1:09 PM
  • I have the same problem since a few days. Sometimes when I started my Win32 Console application within the Visual Studio debugger und stops it by clicking "Debug -> Stop Debugging" the output window say: "The program '[3388] foo.exe: Native' has exited with code 0 (0x0)." But the console window stays active and cannot be closed. After that even Windows cannot be shutdown anymore.

    If the same test application is started from the command prompt it can be closed without problems.

    I have tested the same code with Visual Studio 2005 Standard and Visual Studio 2008 Express. I can even post the code of my test application (20 lines). I also think there are a problem with the Tuesday's updates.
    Friday, February 12, 2010 5:22 PM
  • I'm also getting this same issue, power cycling my computer is the only way I've found to get rid of these zombie windows. Trying to shutdown or restart the machine normally just waits at the desktop for the windows to end without any way to forcibly kill them, or even an error message that windows is unable to end them.

    Attempts to kill the windows by pressing the close window X or killing the application in Task Manager all fail.
    Both Task Manager and SysInternals Process Explorer show no active Command Prompt window processes, so I can't kill it that way.
    Killing and restarting explorer.exe doesn't appear to have any effect either.

    It also doesn't seem to matter how you stop debugging (start a build, press shift-f5, etc), anything but allowing the process to complete creates a zombie window.

    Brendan
    • Edited by CynicismRising Friday, February 12, 2010 11:00 PM Additional details
    Friday, February 12, 2010 10:56 PM
  • Same issue as other describe, zombie dos window remaining after stopping the debugger thru shift-f5 to stop debugging, which can't be terminated until machine is rebooted. Started after applying Tuesday patches.

    Only solution I found is that if I close the dos/console window using the window x/close box, then the process and the window are properly terminated.



    Friday, February 12, 2010 11:44 PM
  • How exactly are you terminating the process? what is the process name?
    • Proposed as answer by MikeTheTv Monday, February 15, 2010 10:50 AM
    Monday, February 15, 2010 10:07 AM
  • Maybe this is related to the  BSOD problems reported with Tuesday's updates?
    http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/73cea559-ebbd-4274-96bc-e292b69f2fd1/#e9b28c45-635c-4adf-8d24-817bf39c207b


    I think you may be correct on this assessment. We had this issue appear on three separate Win XP machines running VS2005. All had installed the patch set from last Tuesday.

    We tried removing patch KB977165, rebooted, and the problem seems to have gone away. At least for one of us. We will try the same solution on the other affected machines.


    Monday, February 15, 2010 10:53 AM
  • Maybe this is related to the  BSOD problems reported with Tuesday's updates?
    http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/73cea559-ebbd-4274-96bc-e292b69f2fd1/#e9b28c45-635c-4adf-8d24-817bf39c207b


    I think you may be correct on this assessment. We had this issue appear on three separate Win XP machines running VS2005. All had installed the patch set from last Tuesday.

    We tried removing patch KB977165, rebooted, and the problem seems to have gone away. At least for one of us. We will try the same solution on the other affected machines.


    Oh its back again. Maybe back out the other Tuesday updates.

    Monday, February 15, 2010 12:49 PM
  • I already backed out all the updates, didn't fix it. Not only is the update broken, but the uninstallers must be broken. 

    Has there been any Microsoft response to this? 

    Monday, February 15, 2010 1:16 PM
  • I've had the same issue as well. I tried killing all the processes one by one to see if one of them was holding the windows open. I finally got to the following processes still up and the zombies were still up:
    csrss.exe
    isass.exe
    services.exe
    smss.exe
    system
    system idle process
    taskmgr (so I could kill them killing it had no effect)
    winlogon.exe

    All these tasks refused to be killed as critical processes. I managed to get to this short list because one of the processes I killed made the system decide it was time to shut down the system. Since the shutdown process fails, and none of the processes that like to restart when killed can do so under shutdown status, this made it possible to kill them as well.

    It's beginning to look like the processes being zombied are behaving like a rootkit - their processes are being hidden from the process list interface.
    Monday, February 15, 2010 3:49 PM
  • I am also experiencing this problem with Visual Studio 2005 since I have installed the patches.  I have not found any way to kill the processes without restarting my computer.  
    Tuesday, February 16, 2010 12:41 AM
  • I'm getting it as well, with Visual Studio 2005. Hello microsoft is there any one there?

    Tuesday, February 16, 2010 1:01 AM
  • Hello,

    Thanks for reporting the issue. I noticed that the version of your VS is:
    VS 2008 9.0.21022 Professional edition

    Could you please install the SP1 of VS? It is available here.

    If it persists and still occurs, please provide us a small project or detail steps to reproduce the issue.

    Since the issue is also related to hotfixes for Windows XP SPs, I also recommend you contact Windows XP Support Center for more help.

    Thanks a lot!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback, please tell us.
    Welcome to the All-In-One Code Framework!
    Tuesday, February 16, 2010 4:15 AM
  • My system has both 2008 sp1 (version 9.0.30729.1sp) and 2005 SP2 (version 8.0.50725.762 (sp.050727-7600)).
    I get the issue running code on the 2005 version.
    Tuesday, February 16, 2010 7:32 AM
  • A colleague and I have also been experiencing this issue since last week with 3 different C++ applications of ours. We have VS2008 SP1 ("9.0.30729.1 SP") and all security updates to XP SP3. Running Windows Update offers me no updates.

    Steps to reproduce issue:
    1. Start application under debugger (F5).
    2. Press F7 in the VS2008 UI to recompile and click 'Yes' to "Do you want to stop debugging" (it's not necessary to have made code changes).
    3. The command prompt stays running, but will not respond to input and cannot be closed by any method. Windows will not reboot, it has to be powered-off.
    4. Using Sysinternals' Process Explorer to identify the process using the "target" function brings up the message "Unable to find the window's owning process in the current process list".

    I'm fairly sure that it's also happened following normal termination of the app, but "F7" is the only way I can reliably reproduce the issue.

    Running the application again under the debugger opens another window. I currently have 6 of these 'zombie' windows on my desktop...
    Tuesday, February 16, 2010 9:23 AM
  • I created a "hello world" console application and it did not reproduce there. There's some action the program has to do to make it happen. I haven't found the exact cause yet.
    BTW Shift F5 will cause it to happen as well.
    Tuesday, February 16, 2010 10:31 AM
  • I already backed out all the updates, didn't fix it. Not only is the update broken, but the uninstallers must be broken. 

    Has there been any Microsoft response to this? 

    I have uninstalled all of the Tuesday patches, listed below, and this does seem to have now fixed the problem. Perhaps you did not get all of them?

    The program I ran yesterday which zombied now exits fine (not recompiled).

    The problem has to be one of the following. May try adding each one back in and seeing if it breaks again.

        * MS10-005: Security Update for Windows Server 2003, Windows XP, and Windows 2000 (KB978706)
        * MS10-006: Security Update for Windows (KB978251)
        * MS10-007: Security Update for Windows Server 2003, Windows XP, and Windows 2000 (KB975713)
        * MS10-008: Cumulative Security Update for ActiveX Killbits for Windows(KB978262)
        * MS10-011: Security Update for Windows Server 2003, Windows XP, and Windows 2000 (KB978037)
        * MS10-012: Security Update for Windows (KB971468)
        * MS10-013: Security Update for Windows (KB975560)
        * MS10-013: Security Update for Windows Server 2003, Windows XP, and Windows 2000 (KB977914)
        * MS10-015: Security Update for Windows 7, Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP, and Windows 2000 (KB977165)

    Tuesday, February 16, 2010 11:24 AM
  • I have faced with this problem too: VS 2005 pro, Windows XP Pro SP3. Anybody found working solution?
    Tuesday, February 16, 2010 12:54 PM
  • #include <windows.h>
    #include <stdio.h>
    #include <tchar.h>
    
    int _tmain()
    {
     HANDLE hPort=CreateFile(L"COM4",GENERIC_READ|GENERIC_WRITE,0,NULL,OPEN_EXISTING,0,NULL);
    
     if(hPort==INVALID_HANDLE_VALUE)
     {
    	 printf("cannot execute the test");
    	 return 1;
     }
    
     printf("press shift+F5");
     while(true);
     return 0;
    }

    This simple code cause the problem. 

    Microsoft Visual Studio 2005
    Version 8.0.50727.762  (SP.050727-7600)

    .NET framework 3.5 SP1
    Windows XP Pro SP3
    Tuesday, February 16, 2010 1:58 PM
  • Thanks yelsma.

    I had to change "COM4" to "COM1" on my machine as CreateFile was failing, but otherwise I can confirm that this code sample reproduces the problem for me - I now have a seventh 'zombie' command prompt.
    Tuesday, February 16, 2010 2:06 PM
  • I get the same problem on windows xp sp3 with visual studio 2008 version 9.0.30729.1 SP.

    Is there any solution to this ?
    Tuesday, February 16, 2010 3:12 PM
  • Same issues, Windows XP sp3, visual studio 2008 version 9.0.21022.8 RTM. It started to happen after Tuesday's automatic update of Windows XP.
    Tuesday, February 16, 2010 3:20 PM
  • The Problem is with the KB978037
    once removed everything return to normal!


    Maybe microsoft can update the update...
     

    • Proposed as answer by Jeff Barcalow Tuesday, February 16, 2010 4:38 PM
    Tuesday, February 16, 2010 3:43 PM
  • I removed all update these update :
    • KB978262
    • KB971468
    • KB978037
    • KB975713
    • KB978251
    • KB978706
    • KB977165
    • KB975560
    • KB977914
    and it worked. I don't know which one cause problem.


    Tuesday, February 16, 2010 4:19 PM
  • Same as Myrkull. After removing all the 2/10/10 updates, it works like it used to. 

    What is interesting is that two of my colleagues also have the updates installed and this does not happen to them.
    Tuesday, February 16, 2010 4:21 PM
  • galcmp reported that the error come from KB978037 .

    After testing i found also that the problem is with the KB978037 .
    • Proposed as answer by ahesa Friday, February 19, 2010 5:19 PM
    Tuesday, February 16, 2010 4:43 PM

  • Uninstalling KB978037 also fixed it for me.


    Can someone from Microsoft escalate this?

    We have sample code (see yelsma's post above) that reproduces the behaviour and uninstalling an "Important" security update solves the issue.
    • Proposed as answer by ilankl Thursday, February 18, 2010 10:37 AM
    Tuesday, February 16, 2010 4:59 PM
  • It appears to me to be a combination of not having VS 2008 SP1 and one or more of the updates. After updating VS with SP1 and removing all the updates on one of my machines, it now works normally. On another machine I updated to VS 2008 SP1 and removed KB977165, which is the one being blamed for the BSOD. This machine still has 978037, but now works fine. 

    It's odd that SP1 hadn't been installed, since I do automatic updates ( or at least used to!) but it didn't install automatically until yesterday. 

    Given some time I may play around with the updates some more, but I hate to mess with success. 


    Tuesday, February 16, 2010 8:15 PM
  • It appears to me to be a combination of not having VS 2008 SP1 and one or more of the updates. After updating VS with SP1 and removing all the updates on one of my machines, it now works normally. On another machine I updated to VS 2008 SP1 and removed KB977165, which is the one being blamed for the BSOD. This machine still has 978037, but now works fine. 

    It's odd that SP1 hadn't been installed, since I do automatic updates ( or at least used to!) but it didn't install automatically until yesterday. 

    Given some time I may play around with the updates some more, but I hate to mess with success. 



    I've had SP1 installed for many months so it's not likely relevant.
    I got rid of the problem by uninstalling KB978037and two other fixes (KB978262, 971468) that were dependent on it.
    Not sure removing the extra two is relevant or needed.
    Thursday, February 18, 2010 10:41 AM

  • I also don't think SP1 is directly relevant (since I've had it installed a long time too), but it's possible that there are software combinations that make it a factor.
    Thursday, February 18, 2010 10:45 AM
  • I am still having this problem and I don't think SP 1 is relevant either.  Here is the information from my about box.

    Microsoft Visual Studio 2008
    Version 9.0.30729.1 SP
    Microsoft .NET Framework
    Version 3.5 SP1

    Installed Edition: Professional

    Microsoft Visual Basic 2008   91605-270-2048662-60832
    Microsoft Visual Basic 2008

    Microsoft Visual C# 2008   91605-270-2048662-60832
    Microsoft Visual C# 2008

    Microsoft Visual C++ 2008   91605-270-2048662-60832
    Microsoft Visual C++ 2008

    Microsoft Visual Studio 2008 Tools for Office   91605-270-2048662-60832
    Microsoft Visual Studio 2008 Tools for Office

    Microsoft Visual Web Developer 2008   91605-270-2048662-60832
    Microsoft Visual Web Developer 2008

    Crystal Reports    AAJ60-G0MSA4K-68000CF
    Crystal Reports Basic for Visual Studio 2008


    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB944899)   KB944899
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/944899.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB945282)   KB945282
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/945282.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB946040)   KB946040
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/946040.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB946308)   KB946308
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/946308.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB946344)   KB946344
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/946344.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB946581)   KB946581
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/946581.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB947171)   KB947171
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/947171.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB947173)   KB947173
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/947173.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB947180)   KB947180
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/947180.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB947540)   KB947540
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/947540.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB947789)   KB947789
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/947789.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB948127)   KB948127
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/948127.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB953256)   KB953256
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/953256.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB971092)   KB971092
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/971092.

    Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB974479)   KB974479
    This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/974479.

    Microsoft Visual Studio 2008 Professional Edition - ENU Service Pack 1 (KB945140)   KB945140
    This service pack is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this service pack will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/945140.

    Microsoft Visual Studio 2008 Professional Edition - ENU Service Pack 1 (KB947888)   KB947888
    This service pack is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this service pack will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/947888.

    Microsoft Visual Studio 2008 Professional Edition - ENU Service Pack 1 (KB948484)   KB948484
    This service pack is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this service pack will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/948484.

    Microsoft Visual Studio 2008 Professional Edition - ENU Service Pack 1 (KB948560)   KB948560
    This service pack is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this service pack will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/948560.

    Security Update for Microsoft Visual Studio 2008 Professional Edition - ENU (KB972222)   KB972222
    This security update is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this security update will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/972222.

    Security Update for Microsoft Visual Studio 2008 Professional Edition - ENU (KB973675)   KB973675
    This security update is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this security update will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/973675.

    SQL Anywhere Explorer   
    SQL Anywhere Explorer

    Update for Microsoft Visual Studio 2008 Professional Edition - ENU (KB956453)   KB956453
    This update is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this update will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/956453.

    Update for Microsoft Visual Studio 2008 Professional Edition - ENU (KB967143)   KB967143
    This update is for Microsoft Visual Studio 2008 Professional Edition - ENU.
    If you later install a more recent service pack, this update will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/967143.

    Visual Studio Package Load Analyzer   1.0
    A utility that analyzes package load failures in Visual Studio.

    Windows Installer XML   Version 3.0
    Votive - Windows Installer XML (WiX) Toolset, Version 3.0.4318.0
    Copyright © Microsoft Corporation. All rights reserved.
    Thursday, February 18, 2010 4:59 PM
  • Confirming this issue. Really annoying to shut down PC by power button. Since i'm a dev i end up having over 5-10 zombies a day. Lucky me it happens only randomly.
    Thursday, February 18, 2010 10:54 PM
  • Finally solve the problem by removing all files related to the KB978037 update.  It works just fine now.

    I work on two versions of the same program and each time I was running one of them I was getting a zombie. Yesterday I ended up with 40 zombies.  And not being able to reboot... aweful. 

    So a big Ya! for galcmp.
    Friday, February 19, 2010 5:23 PM
  • If you detach from your program rather than killing it, the os cleans up the window normally.

    Since you can detach at any point, this has allowed me to continue without continually spawning zombie command windows.
    • Edited by CynicismRising Friday, February 19, 2010 11:39 PM spelling edit
    Friday, February 19, 2010 9:55 PM
  • Well now that have deleted the files KB978037, it's spawning a lot less windows. But I do get zombies when I put a break point or if the software crashes instead of ending normally. The "detach" solution seems kinda inappropriate in this case (I usually run the software in release mode). Keep looking I guess..
    Friday, February 19, 2010 11:00 PM
  • This happened to me also. I agree it is due to an update.

    I'm using Visual Studio 2008version 9.0.21022.8 RTM. with .NET Framework version 3.5 SP1. My program is a Win32 Console Application. It uses TCP/IP WSASockets. When I run the program in debug mode everything is fine, but when I stop the debug session the Console window does not close. Then when I restart my computer the system will not finish shutting down. I have to power cycle.

    This all started after I loaded the latest Microsoft updates around 2/15/10. I did a system restore and that fixed it. On 2/18/10 the updates automatically re-installed and the problem came back. So I did another system restore and that fixed it.

    The updates are:
    KB978262, KB978207, KB976881, KB971468, KB975560, KB975713, KB977914, KB978037, KB978251, KB978706, KB977713, KB890830

    I see that 8037 is one of them and it has been suggested that is the culprit. There are some updates ready now, when I get brave I'll try installing all but that.

    • Proposed as answer by eddyq Saturday, February 20, 2010 9:28 PM
    Saturday, February 20, 2010 8:53 PM
  • This happened to me also. I agree it is due to an update.

    I'm using Visual Studio 2008version 9.0.21022.8 RTM. with .NET Framework version 3.5 SP1. My program is a Win32 Console Application. It uses TCP/IP WSASockets. When I run the program in debug mode everything is fine, but when I stop the debug session the Console window does not close. Then when I restart my computer the system will not finish shutting down. I have to power cycle.

    This all started after I loaded the latest Microsoft updates around 2/15/10. I did a system restore and that fixed it. On 2/18/10 the updates automatically re-installed and the problem came back. So I did another system restore and that fixed it.

    The updates are:
    KB978262, KB978207, KB976881, KB971468, KB975560, KB975713, KB977914, KB978037, KB978251, KB978706, KB977713, KB890830

    I see that 8037 is one of them and it has been suggested that is the culprit. There are some updates ready now, when I get brave I'll try installing all but that.


    Yup, that was it ... I removed the check mark on KB978037 then installed all other updates. Until Microsoft announces a fix, my recommendation is to turn off Automatic Updates. Then when you see the install shield then remove the check mark on KB978037. But the problem is ... how do we know when Microsoft has fixed it. Microsoft ... if you are out there can you please post to this thread when you have fixed KB978037?
    Saturday, February 20, 2010 9:32 PM

  • I have now raised this under the Windows Update forums at:

    http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/64edc1fe-94dc-4f44-8e17-03331a203ac8

    Perhaps this will help in progressing the issue...
    Monday, February 22, 2010 9:34 AM
  • same situation with these zombie windows happen with intel fortran compiler in debug mode. not only c++.

    when trying to examine the window with the processexplorer (using the target cross), there is an error with "no process found with this id".
    Wednesday, February 24, 2010 2:16 PM
  • Just adding my confirmation of this issue. We have two machines at our company that started exhibiting this issue last Wednesday morning (17th February). VS2008 SP1, XP SP2 32bit.
    Wednesday, February 24, 2010 5:58 PM
  • FYI ... I have had a problem with the Windows Installer on Win Server 2K8 Enterprise, SP1 ... the installer was failing, causing services to shut down but never restart, etc. I believe I have narrowed my problem on 3 different (thankfully mostly similar) Win 2K8 installs to KB978207. I have avoided re-installing it and have at least been able to keep my platforms current.

    Tom Winans
    Thursday, February 25, 2010 3:39 AM
  • Just adding a "me too". XP SP2 32 bit, Visual Studio 2008 SP1. Removing KB978037 made it go away. Looks like they broke csrss.exe (that's the process that owns console windows).
    Thursday, February 25, 2010 3:43 PM
  • Hi, Just wanted to let you know that the Visual Studio debugger team is actively looking into this issue. I'll post updates as things progress. Thanks, Brad Sullivan
    Brad Sullivan - Program Manager - Visual Studio Debugger http://blogs.msdn.com/brads
    Tuesday, March 02, 2010 1:44 AM
    Owner
  • Thanks Brad, glad to hear it!
    Tuesday, March 02, 2010 8:21 AM
  • Brad, be aware that it's not just a Visual Studio problem; I've had a couple of these zombie windows appear since I updated on 02/12, and I don't use VS.  For me, the problem has appeared when I was running a .BAT file in a command window.  Both times the batch file executed an EXIT /B command but the window failed to close.  The window displayed the EXIT command line and nothing else, and I had to reboot to get rid of it.  I sometimes run that same batch file several times a day, so the problem is very rare for me.
    Tuesday, March 02, 2010 3:37 PM
  • We've been able to reproduce this issue locally.  As a few of you have mentioned, this issue is likely not in Visual Studio since it also occurs in scenarios where Visual Studio is not present.  We are in the process of handing over our investigation to the Windows Servicing team.

    Thanks.
    Brad Sullivan - Program Manager - Visual Studio Debugger http://blogs.msdn.com/brads
    Tuesday, March 02, 2010 10:31 PM
    Owner
  • We've been able to reproduce this issue locally.  As a few of you have mentioned, this issue is likely not in Visual Studio since it also occurs in scenarios where Visual Studio is not present.  We are in the process of handing over our investigation to the Windows Servicing team.

    Thanks.
    Brad Sullivan - Program Manager - Visual Studio Debugger http://blogs.msdn.com/brads

    thank you, Brad:

       we've also seen this when Console Apps launched from a DOS-batch file.
    Tuesday, March 02, 2010 10:54 PM
  • Thanks for investigating Brad. Will we get any visibility of progress on this issue once it's handed over?

    Thursday, March 04, 2010 9:26 AM
  • Thanks,

    I'm also having this issue with Visual Studio 2008/C++ and I have a small example to reproduce it
    (Console hangs after exiting debug-modus under XP and Server 2003):

     

    #include "stdafx.h"

    #include <iostream>

     

    using namespace std;

     

    int _tmain(int argc, _TCHAR* argv[])

    {

         int i;

         FILE *datf;

         fopen_s(&datf,"test.txt","w");

         for (i=0;i<200000;i++) {

               fprintf(datf,"i = %d\n",i);

         }

         fprintf(datf,"i = %d\n",-1);     // Breakpoint here

         fclose(datf);

         return 0;

    }


    Friday, March 05, 2010 8:53 AM
  • Any updates on this matter?

    We have 4 machines here at work that does this "zombie" console windows. Mostly mine since I am doing the most dev work at the moment, often resulting in 8-10 zombie windows at the end of the day.

    As with everyone else this happened after that tuesday update a few weeks ago.
    Monday, March 08, 2010 11:08 AM
  • We have 3 developers affected by this issue.

    Has Microsoft responded with a fix yet?
    David
    Monday, March 08, 2010 3:05 PM
  • One way for me to get around the problem is not to click "Stop Debugging" but rather close the console window using its "x" button (it's so hard to get into the habit of doing it though...)
    Monday, March 08, 2010 8:20 PM
  • I've been fighting this on my systems also. Removing the security update KB978037, rebooting stops the problem (until MS updates re-loads the update AGAIN..)
    Thursday, March 11, 2010 2:18 PM
  • I've created a blog post for this issue here: http://blogs.msdn.com/debugger/archive/2010/03/11/help-my-console-windows-won-t-go-away.aspx We will post updates there as soon as we get them. At this time, I do not have any dates from the Windows team that I can share. Additionally, we have not been able to reproduce the issue locally without just a batch script. While that may not be strictly necessary to create a fix, we do want to make sure that the fix is tested against this scenario as well. If anybody has a batch file that could be shared, please let us know. Thanks.
    Brad Sullivan - Program Manager - Visual Studio Debugger http://blogs.msdn.com/brads
    Thursday, March 11, 2010 10:13 PM
    Owner
  • We've been experiencing the same issue for sometime at our workplace.  However, I did figure out that if you kill winlogon.exe with process explorer or whatever, your computer will restart normally (no need for hard reset).  Hopefully that eases the pain for some of you while we wait for a resolution.
    Friday, March 26, 2010 7:27 PM
  • I have also seen this issue with some of our developers who use the C++ debugger on VS 2005...

    Does anyone also experience this... ?

     

    Also, has anyone removed both KBs below or just the top one.. (KB978037)

        * MS10-011: Security Update for Windows Server 2003, Windows XP, and Windows 2000 (KB978037)
        * MS10-015: Security Update for Windows 7, Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP, and Windows 2000 (KB977165)

     

    Removing both KBs resolves the frozen command window for our developers.

     

    Thanks in advance.

    Monday, March 29, 2010 4:32 PM
  • I'm using Microsoft Visual Studio 2005 Version 8.0.50727.762 (SP.050727-7600) and have the same problem.

    Removing the patch KB978037 solved the problem, I also had to reboot using the power switch.

    However the patch was automatically applied again and the problem came back.

    thanks,
    Martin.
    Thursday, April 15, 2010 10:04 AM
  • VS2008 SP1 (9.0.30729.1 SP)

    But also happens during regular application use since our application opens command line window for informational / debug messages.

    Uninstalling the mentioned KB patch is not an option because of company policy.

    Any updates on this issue at all?

    Thanks

    Friday, April 16, 2010 4:21 PM
  • The Windows team is currently working on a fix for this, however they have not announced the date this fix will be available yet
    Best Regards, Andrew Hall. Visual Studio Debugger.
    Monday, April 19, 2010 8:41 PM
    Moderator
  • This is more than known now. Are the any news about this? Power cycling is even worse than not having that patch, is it? Is there an official position or are they just being silent till everyone gets tired of complaining. Not cool.

    Wednesday, April 28, 2010 5:36 PM
  • Uninstalling the patch works. I also installed an application called Taskbar Helper to hide windows and their tab in the task bar. Doesn't solve the problem, but its better than having the zombie windows in the way.

     

    Thursday, April 29, 2010 9:16 PM
  • I am not sure about the status on this problem. Has it been fixed already? But I also had this problem under VS 2005 .... I removed the KB978037 and that solved the problem.

    Friday, May 14, 2010 6:55 PM
  • This defect has been around for a long time now (> 2 months).. It is surprising that MSFT allows VS users to live with something as annoying as this. Looking forward to a fix at the earliest !!

    Monday, May 17, 2010 6:26 PM
  • man, this is a really annoying bug. lets see how long Windows  team will let us live with this. 
    Sunday, May 23, 2010 7:34 PM
  • Microsoft should disable that patch. This is really annoying especially for those people like me who use remote control and are not able to power cycle the computers. I have wasted tens of hours because of this bug. I do not understand why several months have passed and Microsoft has not done anything yet.
    Tuesday, May 25, 2010 9:57 PM
  • Still no news?

    Some people are posting here as well: http://blogs.msdn.com/b/debugger/archive/2010/03/11/help-my-console-windows-won-t-go-away.aspx but the poster in that blog (brads) hasnt bothered to post any updates lately.

    From Andrew B Hall (Moderator) in this forum we learn that a fix is in progress. That was April 19. That is like 49 days ago. Hello! We are a bunch of people still waiting, hoping, praying that this issue will be resolved.

    /Mikael

    Monday, June 07, 2010 12:03 PM
  • I'm still praying and hoping ...

    That's all we can do, XP is over.

    Wednesday, June 09, 2010 12:13 PM
  • It is not just XP, I managed to get this in win 7 also. However in win7 when i resumed to login screen the windows dissapeared so i did not had to shut down the PC by killing the power.

    It is sad that on my XP the desktop is messed up, had to run hard disk scan a few times because all the force shutdowns.

     

    Where is the customer support support when you need one ? :(

    Wednesday, June 09, 2010 1:01 PM
  • You cannot close a console window of an application after you stop debugging the application in Visual Studio on a computer that is running Windows XP:
    http://support.microsoft.com/kb/982551
    • Proposed as answer by Adam Miles Sunday, June 13, 2010 11:20 AM
    Thursday, June 10, 2010 3:08 AM
  • Is there someone who tests the hotfix ? Does it work well ?
    Monday, June 14, 2010 9:48 AM
  • Is there someone who tests the hotfix ? Does it work well ?
    I don't imagine Microsoft would have released a fix without testing it.
    Monday, June 14, 2010 10:34 AM
  • This is working great for my 32 bit machines,  Any prognosis on a hotfix for 64bit?

     

    thanks 

    Monday, June 14, 2010 7:54 PM
  • Still no updates for a x64 hotfix? This is a major pain for developers, and quite bad for hardware since the machine cannot be rebooted normally. I am astonished that MS don't take this seriously.
    Tuesday, June 29, 2010 4:22 PM
  • Looks like there is a fix available:

    http://support.microsoft.com/kb/982551

    Tuesday, July 06, 2010 11:56 AM
  • The hotfix quoted above seems to be for x86 only. So let me throw in one more request from a stranded x64 developer. Wake up, Redmond!

    Regards,

    Tomasz

    Tuesday, August 03, 2010 11:00 AM
  • It is extremely annoying not to have a fix for x64!

    I think everyone would have expected Microsoft to fix such a defect swiftly; which obviously is not the case.

     

    Regards

    Friday, August 13, 2010 10:38 AM
  • The fix worked for me (x86). No need anymore to press the pc power button. :)

    Thanks,

    Andre

    Monday, August 16, 2010 5:24 AM
  • Is there a time line for when will the x64 fix be ready ???
    • Proposed as answer by D_Rider Thursday, August 26, 2010 3:20 PM
    Tuesday, August 17, 2010 2:19 PM
  • Microsoft, do you propose to provide a fix for x64 users, or are you going to leave us hanging?
    Thursday, August 26, 2010 3:23 PM
  • This is quoted from the email from hotfix@microsoft.com regarding this hotfix:

     

    "WARNING   This hotfix has not undergone full testing. Therefore, it is intended only for systems or computers that are experiencing the exact problem that is described in the one or more Microsoft Knowledge Base articles that are listed in "KB Article Numbers" field in the table at the end of this e-mail message. If you are not sure whether any special compatibility or installation issues are associated with this hotfix, we encourage you to wait for the next service pack release...."

     

    Apparently,  this is not an official fix, not fullly tested.

    • Edited by Moby_xzl Thursday, September 02, 2010 3:36 AM the format is wrong
    Thursday, September 02, 2010 3:35 AM
  • This can be repro-ed with high chance by pressing SHIFT+F5 (stop debugging) during debug with VS05 or VS08. In fact there is no process attached the window, so the window can not be closed any longer.
    Monday, September 13, 2010 6:11 AM
  • AFAIK, Windows XP Pro x64 uses the same csrsrv.dll file as Windows Server 2003 x64, but the updater doesn't know that....   Please edit the Windows Server 2003 x64 (SP2QFE) version of the KB982551 hotfix so that it can also apply to Windows XP Professional x64 (SP2GDR) as well.  (Or can anyone here go inf hacking to make the updater run correctly?)

    I can grab the file manually from the hotfix by looking into the hotfix's temporary directory before closing the error message, but without any knowledge of how to install the security catalog, Windows File Protection is being a jerk and overwriting it. :(

    • Edited by AySz88 Friday, September 24, 2010 9:42 PM reword
    Friday, September 24, 2010 9:41 PM

  • Hi galcmp,
     
    As a solution, it has been suggested to uninstall KB978037
     
    I searched for it and my machine found this file:  KB978037.cat    (date modified 14/12/2009)
     
    Do you actually mean removing this file, by going to its directory and deleting it???
     
    Thanks,
     
    Friday, May 06, 2011 10:20 AM
  • Thanks that worked for me too... didn't expect to find a fast solution.
    Andreas Glaser
    SharePoint Tutorial
    Install SharePoint
    SharePoint Designer
    Saturday, June 11, 2011 1:45 PM