October 11, 2016, update for SharePoint Foundation 2013 (KB3118368)

Applies to: Microsoft SharePoint Foundation 2013 Service Pack 1

This article describes update KB3118368 for Microsoft SharePoint Foundation 2013, which was released on October 11, 2016. This update has a prerequisite.

Improvements and fixes


  • Introduce a new switch to enable recall to be excluded from the link update group of search indexes that may contain unrelated content based on user queries.
  • Makes query logging to use original user query text.
  • Fixes the following issues:
    • When you edit a SharePoint page, screen readers report RTE fields as unlabeled edit.
    • When you insert embedded code and move to the delete button, screen readers report the button as a popup.
    • When the If-Modified-Since HTTP header instead of the If-None-Match HTTP header is sent, the server responds with the (304) Not Modified error even when the document is changed since the client-specified time.
    • If you have an orphaned app in the initialized state on a site and you delete the site, Health Analyzer reports that there's an error and the auto-fix doesn't work.
    • The client context builds incorrect urls if page context information isn't available yet.
    • When you send email messages with multiple attachments that have a same attachment name, the email messages are deleted and aren't saved in SharePoint Server 2013 lists.
    • If an alert with multiple user lookup fields is generated, some fields will have incorrect or missing data.
    • A Content Query Web Part may display no result for a query that includes more than 10 lists if one of the lists has more than 5000 items with unique permissions.
    • Links that are longer than 256 characters are truncated after a rename, a content type update, or a content deployment.
    • As part of SharePoint database upgrade, the members of the db_owner role are deleted from the role, except for the "dbo" user and the user performing the upgrade. This is done for enhanced security to make sure that an errant account isn't inadvertently left with the db_owner role privileges. However, there may be situations where this behavior is not desirable. For example, RBS may be broken each time upgrade is run. In this situation, a registry key is added to bypass this behavior. 

      Note Before you install this update, follow the steps in the Registry information section to create the registry key.
    • Links may begin with "//" (such as //www.microsoft.com/about/) as malformed server-relative links. After you install this update, the links are recognized as specifying the host name but keeping the same URL scheme as the referencing page.

How to download and install the update


Download Center

This update is only available for manual download and installation from the Microsoft Download Center.

Update information


Registry information

Important
Follow the steps in this section carefully. Serious problems might occur if you change the registry incorrectly. Before you change it, back up the registry for restoration in case problems occur.


After you install this update, you can follow these steps to control the metafiles optimization:
  1. Start Registry Editor:
    • In Windows Server 2012, if you're using a mouse, move it to the upper-right corner, go to Search, enter regedit in the search text box, and then select regedit.exe in the search results.
    • In Windows Server 2008, go to Start, enter regedit in the Search programs and files text box, and then select regedit.exe in the search results.
  2. Locate and then select the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\
  3. On the Edit menu, point to New, and then select DWORD Value.
  4. Enter BypassDboDropMember, and then press the Enter key.
  5. In the Details pane, press and hold (or right-click) BypassDboDropMember, and then select Modify.
  6. In the Value data box, enter 1, and then select OK.

    Note If you don't want to bypass the behavior, you can set the value to 0.
  7. Exit Registry Editor.

Prerequisite

To apply this update, you must have Microsoft SharePoint Foundation 2013 Service Pack 1 installed.

Restart information

You don't have to restart the computer after you install this update.

References


Learn about the terminology that Microsoft uses to describe software updates. The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all versions of Office.

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.