FIX: "Requirement" type work items take a long time to save in TFS 2012

Applies to: Microsoft Visual Studio Team Foundation Server 2012Visual Studio Team Foundation Server Express 2012


When you create some work items of certain types in the "Requirement" category (for example, "User Story" in the MSF Agile template, "Requirement" in the MSF Formal template, or "Product Backlog item" and "Bug" in the Scrum template) in Microsoft Team Foundation Server (TFS) 2012, TFS 2012 may require an unusually long period of time to save the work items. However, the other work item types are saved quickly.


Hotfix information

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

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


 To apply this hotfix, you must have the Team Foundation Server 2012 installed.

Restart requirement

You have to restart the computer after you install the hotfix if the affected files are being used at the time of installation. We recommend that you close all Visual Studio 2012-related components before you install the hotfix.


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