An update rollup is available for the testing tools in Visual Studio 2010 SP1


An update rollup is available that resolves the following issues for the testing tools in Microsoft Visual Studio 2010 Service Pack 1 (SP1).

Issue 1
When you run tests on the test agent that is installed on a computer that has Visual Studio 2010 SP1 installed, the tests may not run, and the following error is logged: 
Attempted to access an unloaded AppDomain. (Exception from HRESULT: 0x80131014)
Issue 2
When you run a playback of a coded UI test on certain Windows Presentation Foundation (WPF) controls, a Microsoft.VisualStudio.TestTools.UITest.Extension.UITestControlNotFoundException exception occurs, and then you receive the following error message:
"Search may have failed at '<name>' <control type> as it may have virtualized children. If the control being searched is descendant of '<name>' <control type> , including it as the parent container may resolve the problem."
  • This exception may be generated because the WPF controls are deep in the UI control hierarchy. Therefore, the control cannot be addressed in the recorded QuerID UI control hierarchy in the UI map. After you install this update, the control can be addressed.
  • After you install this update, the following key is added to CodedUITestBuilder.exe.config/MTM.exe.config files in order to resolve this issue: 
    <add key="MaxLevelsForItemContainer" value="<desiredLevel>"/>
  • UI Test Framework searches the UI hierarchy until it reaches an instance of <desiredLevel> to identify a parent container. By default, <desiredLevel> is set to 2. Set <desiredLevel> to an appropriate value for your situation. 
  • If you set <desiredLevel> to a high value, performance may be affected when a recording operation occurs.

Issue 3
Assume that you try to create a work item from the Test Results pane in Visual Studio 2010 after you connect to a Team Foundation Server (TFS) server. In this situation, a System.OutOfMemory exception occurs, and the creation operation fails. This issue frequently occurs if the TFS server has many builds.

Issue 4
When some tests run in a build operation, some builds that are queued in a TFS server stop responding. Additionally, the following error is logged in the build log:
Waiting to publish...

Publishing results of test run <build name> to http://<TFS server address>:8080/tfs/DefaultCollection...

The process cannot access the file '<directory>\data.coverage' because it is being used by another process.

Publish failed or canceled.
Note This issue occurs because the Mstest.exe process crashes. When a non-test thread encounters an assertion failure or a nonfatal exception that is unhandled, the Mstest.exe process crashes if code-coverage collector is enabled for the test run. 

This issue may occur when tests run in an MSBuild script. MSBuild scripts skip the test run step.

More Information

Update information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, 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 website:Note 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 You can also download this update from the following Microsoft website:


To apply this update, you must have Visual Studio 2010 Service Pack 1 (SP1) installed.

Restart requirement

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

Update replacement information 

This update does not replace a previously released update. 

File information

The global version of this update 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 nameFile versionFile sizeDateTimePlatform


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