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.


This article describes the issues that are fixed in the Microsoft SharePoint Server 2010 hotfix package that is dated April 8, 2014.


Issues that this hotfix package fixes

  • After you install the June 2013 cumulative update for SharePoint Server 2010, you can only configure the authentication method for the whole farm.

    After you install this update, you will be able to configure the authentication method for each web application separately.

  • Assume that you have a page that contains certain reusable content. After you edit and save the page, you may find duplicate reusable content on the same page.

  • Consider the following scenario:

    • You browse to a SharePoint Server 2010 site by using Internet Explorer 9.

    • You create a navigation link that contains one or more audiences selected from EntityEditor in the Audiences list.

    In this scenario, you cannot save the navigation link. Additionally, you receive an error message.

  • When you add a user name in the People Picker filed by using the People Picker control in the profile page, a semicolon is added behind the user name unexpectedly. Additionally, you receive the following error message:

    You are only allowed to enter one item.

  • After you check out, edit (that triggers a SharePoint 2010-style workflow), and check in a document in a SharePoint Server 2013 document library, the workflow's status column displays an incorrect status.

  • When you change the views in the Project Center in Project Web App in Internet Explorer 11, the views may load incorrectly.

  • For users who have registered to receive daily digests for list alerts, make sure that all the events from a given list are combined in a single email.

  • Incoming email messages that are sent to Web applications that use Trusted Identity Providers (ADFS) resolve to a Windows Claim user and not to the ADFS Claims user.

    To resolve this issue, apply this hotfix and then run the following in Windows PowerShell to update the whole SharePoint farm or a single Web application. This disables Active Directory user resolution and enables Trusted Identity Provider (ADFS) user resolution.

    Farm-level update:

    $farm = Get-SPFarm 
    $farm.Properties["disable-active-directory-resolve"] = "true"
    $farm.Properties["enable-trusted-resolve"] = "true"

    Web application-level update:

    $w = Get-SPWebApplication 
    $w.Properties["disable-active-directory-resolve"] = "false"
    $w.Properties["enable-trusted-resolve"] = "false"

    You may also override the SharePoint farm-level settings at a specific Web application, because the Web application settings take precedence over the farm-level settings.

More Information

Hotfix information

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.


To install this hotfix, you must have either SharePoint Server 2010 Service Pack 1 (SP1) or Service Pack 2 (SP2) installed.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2510766 List of all SharePoint 2010 and Office Server 2010 SP1 packages

2687522 List of all SharePoint 2010 and Office Server 2010 SP2 packages

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 one of the hotfixes 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 hotfix package uses a Microsoft Windows Installer package to install the hotfix 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?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!