Microsoft KB Archive/888474

= Your program stops responding when you run it in debug mode in Visual Studio .NET or in Visual Studio 2005 =

Article ID: 888474

Article Last Modified on 2/10/2006

-

APPLIES TO


 * Microsoft Visual Studio 2005 Professional Edition
 * Microsoft Visual Studio 2005 Standard Edition
 * Microsoft Visual Studio .NET 2003 Professional Edition
 * Microsoft Visual Studio .NET 2003 Enterprise Architect
 * Microsoft Visual Studio .NET 2003 Enterprise Developer
 * Microsoft Visual Studio .NET 2003 Academic Edition
 * Microsoft Visual Studio .NET 2002 Professional Edition
 * Microsoft Visual Studio .NET 2002 Enterprise Architect
 * Microsoft Visual Studio .NET 2002 Enterprise Developer
 * Microsoft Visual Studio .NET 2002 Academic Edition

-



Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect your system.





SYMPTOMS
In Microsoft Visual Studio .NET or jn Microsoft Visual Studio 2005, you may notice that your program stops responding (hangs) when you run it in debug mode. When this behavior occurs, you do not receive any error messages.



CAUSE
This behavior may occur if you have a third-party firewall program installed. You cannot work around this behavior by disabling the firewall program. Also, you cannot work around this behavior by setting the firewall program option to trust Visual Studio .NET or Visual Studio 2005 or to trust the Machine Debug Manager.



WORKAROUND
To work around this behavior, use one of the following methods.

Method 1
Warning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.

Use the System Configuration Utility (Msconfig.exe) to configure your computer to start in Selective Startup mode. The System Configuration Utility only starts the services that are required to run Windows. The System Configuration Utility is included with Microsoft Windows XP and Microsoft Windows Server 2003.

Note The System Configuration Utility is not included with Microsoft Windows 2000. However, you can use a copy of the System Configuration Utility from a Windows Server 2003-based computer or from a Windows XP-based computer. Typically, the System Configuration Utility is located in the following folder:

c:\%WINDIR%\System32

To use the System Configuration Utility, follows these steps:
 * 1) Click Start, click Run, type msconfig in Open box, and then click OK.
 * 2) On the General tab of the System Configuration Utility dialog box, click Selective Startup. If Load System Services and Load Startup Items are not selected, click to select them.
 * 3) On the Services tab, click the Service column header to alphabetically sort the services. If Machine Debug Manager and Windows Installer are not selected, click to select them.
 * 4) Click Apply. When the changes are completed, click Close. Click Yes to restart your computer.
 * 5) After your computer restarts, click OK in the System Configuration Utility Information dialog box. If the System Configuration Utility dialog box appears, click the Close button. If you receive a message to restart the computer, click Exit Without Restart.

Now you can run your program in debug mode in Visual Studio .NET.

To take your computer out of Selective Startup mode, follow these steps:
 * 1) Click Start, click Run, type msconfig in Open box, and then click OK.
 * 2) On the Selective Service tab, click to select Normal, click Apply, and then click OK.
 * 3) Restart your computer.

Method 2
Warning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.

Uninstall the third-party firewall program. We recommend that you quit Visual Studio .NET before you uninstall the third-party firewall program.



Steps to reproduce the behavior

 * 1) Install a third-party firewall program.
 * 2) Install Visual Studio .NET or Visual Studio 2005
 * 3) Build a new project.
 * 4) On the Debug menu, click Start to run your program in debug mode.

Additional query words: Content Maintenance 25806

Keywords: kbtshoot kbprb kbvs2005applies kbvs2005swept KB888474

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.