Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


Cumulative update packages for Microsoft SharePoint Server 2013 contain hotfixes for the issues that were fixed since the release of SharePoint Server 2013. Additionally, this update improves the stability of search components in large server farms.

Note This is build 15.0.4551.1005 of the cumulative update package.

We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new release contains all the hotfixes and security updates that were included in the previous SharePoint Server 2013 update package releases.


Issues that this cumulative update package fixes

  • When you assign a task to a user whose display name contains a comma on a SharePoint Server 2013 site, you receive the following error message:

    The user does not exist or is not unique.

  • After you use SharePoint Designer 2013 to add a Dataform web part to a SharePoint Server 2013 page and enable grouping on one or more fields, you cannot expand or collapse the group.

  • The language selection drop-down list on the search page does not extended fully.

  • Consider the following scenario:

    • You create a SharePoint Server 2013 document library that has the Versioning and Required Check Out features enabled.

    • You upload a document to the document library.

    • You check in the document and then leave a version comment.

    • You check the version history of the document.

    In this situation, the version comment is blank.

  • Consider the following scenario:

    • You create a grouping view for a list that contains a managed metadata service field on a SharePoint Server 2013 site.

    • You expand all nodes for the list.

    • You apply a filter to the managed metadata service field.

    In this situation, all items are missing.

    Note This issue occurs even after you clear the filter.

  • Assume that you create a new workflow that executes many input or output (I/O) operations on a SharePoint Server site by using SharePoint Designer 2013. Then, you publish the workflow and trigger an instance. When you browse through the workflow status page, you receive the following error message:

    System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

This cumulative update package also fixes the issues that are described in the following Microsoft Knowledge Base articles:

  • 2825665 Description of the SharePoint Server 2013 hotfix package (Sts-x-none.msp): October 8, 2013

  • 2825672 Description of the SharePoint Server 2013 hotfix package (Coreserver-x-none.msp): October 8, 2013

  • 2825675 Description of the SharePoint Server 2013 hotfix package (Coreserver-x-none.msp; Coreservermui-<Language-Code>.msp): October 25, 2013

  • 2760465 Description of the Project Server 2013 hotfix package (Coreserver-x-none.msp; Projectserverwfe-x-none.msp): October 9, 2013

How to obtain the cumulative update package for SharePoint Server 2013

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

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, contact 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: 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.

SharePoint Server 2013 hotfixes that are included in the cumulative update package for SharePoint Server 2013

This cumulative update package contains all the .msp files that we released as hotfixes or as public updates for SharePoint Server 2013. This update package also targets SharePoint Foundation 2013. Therefore, you do not have to install that package separately.


You must install the following public update before you apply this cumulative update package:

2767999 Description of the SharePoint Server 2013 update: March 12, 2013

Cumulative update package information

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to resolve the issues that are listed in this article.

The global version of this cumulative update package uses a Microsoft Windows Installer package to install the cumulative update package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?

Thank you for your feedback!