Consider the following scenario:

  • You build a Microsoft .NET Framework 3.5-based application in debug mode. For example, in the Web.config file for a .NET Framework 3.5-based Web application, you set the debug option as follows:


  • You use Microsoft Visual Basic 2008 as the programming language.

  • The application depends on many assemblies and references.

In this scenario, the Visual Basic compiler (Vbc.exe) may use 100 percent of the CPU resources. Additionally, you may receive an error message that resembles the following:

Object '/32eba493_7a69_40af_bfe6_52887ab07396/jdkqqpvt_pufe5n+ogossdnv_258.rem' has been disconnected or does not exist at the server.


This issue may occur because the CPU computes lots of debug data when you build the application in debug mode. How much debug data is computed depends on the size of the project and on the number of references. In some cases, the debug data is computed multiple times.


Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Note After you install this hotfix, the CPU computes the debug data only one time. This change minimizes the workload for the compiler and resolves the issue that is mentioned in the "Symptoms" section. To completely resolve the problem, we recommend that you also install the Visual Basic 2008 hotfix that is provided in the following Microsoft Knowledge Base article:

951708 The Visual Basic compiler (VBC.exe) may use 100 percent of the CPU resources when you build a Visual Basic 2008 application that has a lot of assemblies and references


To apply this hotfix, you must have the .NET Framework 3.5 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File name

File version

File size























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

Method 1

Build the application in release mode.

Method 2

If you are trying to build a Web application, set the debug option as follows in the Web.config file:



Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!