SharePoint 2016 - November 2016 CU Issue Fixed

In this article, we will list all the issues of SharePoint 2016 that are fixed in the November 2016 CU. This month, MSFT released two packages and we should install them both.

Special Announcement

The long awaited feature pack 1 is finally released, which is now part of this CU (November CU aka Feature pack 1). In Feature Pack 1, the following features are released:

  1. Administrative Actions Logging
  2. MinRole enhancements
  3. SharePoint Custom Tiles
  4. Hybrid Auditing (preview)
  5. Hybrid Taxonomy (preview)
  6. OneDrive API for SharePoint on-premises
  7. OneDrive for Business modern experience (available to Software Assurance customers)
Improvements and fixes

This CU brings a lot of SharePoint Server fixes, here is the list of fixes published by MSFT.

SharePoint Server 2016 Improvements

  1. The time it took to patch and upgrade to the September 2016 and October 2016 public updates was much longer than usual. This has been fully fixed for the November 2016 public update by refactoring how we package the updates.

    If you haven't installed the September 2016 or October 2016 public update, you can expect patching and upgrades to the November 2016 public update to take the same time as usual. If you have installed the September 2016 or October 2016 public update, you can expect patching to the November 2016 public updates to still take longer than usual as we convert the files installed by those updates into the new packaging format. As soon as that's complete, you can expect patching to future public updates to take the same time as usual.

  2. Improves performance when you use Content Search Web Part in Internet Explorer.

  3. Updates translations of a hashtag in Danish to make sure that the meaning is accurate in SharePoint Server 2016.

  4. Translates some terms in multiple languages to make sure that the meaning is accurate.

  5. Enables query logging to record original query text.

  6. Adds a new feature to allow the recall to be excluded from the link update group of search indexes which may contain unrelated content based on your queries.

  7. Search results aren't ranked correctly for certain queries and result sets.


  1. URLs that are copied from a search result page are invalid if multiple consecutive white spaces are included.

  2. The Alert Me link can't be hidden through PowerShell.

  3. Performance issue when you connect to a SharePoint Server 2010 Web Front End (WFE) server by using a SharePoint Server 2013 search backend.

  4. If you add a custom search vertical on a SharePoint team site, the default search verticals, such as Everything and People, disappear from the search settings. Meanwhile, this update also adds the possibility of inheriting search verticals from the parent team site.

  5. You can't request or get refiners through a remote SharePoint search result source.

  6. After you upgrade from SharePoint Server 2013 to SharePoint Server 2016, Excel Web Parts that are created in SharePoint Server 2013 can't be loaded.

  7. When you use Chinese taxonomy refiners to search items on a SharePoint Server 2016 site, the search appears broken.

  8. When you select a refiner, incorrect recall occurs if the Search UI language and the document language are mismatching.

  9. Managed account password change fails after you have KB3167679 and KB3177108 installed.

  10. In certain circumstances, an error page is displayed when you browse to an ASPX page that has a code block, despite an appropriate PageParserPath element in the web.config file. The error message that resembles the following is logged to ULS,

    System.Web.HttpException: Code blocks are not allowed in this file.
  1. If the search result source references the request URL, the sitemap generation fails for a SharePoint Publishing site collection (the Search Engine Sitemap job fails).

  2. Self-assigned timesheet lines may display an incorrect TASKUID in the OData feed.

  3. If the web.config file size is larger than 250 KB which is the default file size limit, the SharePoint farm can't be visited because IIS doesn't load the web.config file.
Language Dependent Fix
  1. Translate some terms in multiple languages to make sure that the meaning is accurate.
  2. Update translations of the hashtag in Danish to make sure that the meaning is accurate for SharePoint Server 2016.
  3. Translate field name of the custom app launcher tiles features in multiple languages for SharePoint Server 2016.
  4. Update branding names of SharePoint Server 2016 in multiple languages.

As we know, this Month MSFT Release 2 CUs (one Include the LPs and Other No LP).

  • To apply this update, you must have Microsoft SharePoint Server 2016 installed.
Restart information
  • If during the Installation of the Updates certain components of SharePoint are running then it will ask you to Restart the server. So its depend upon your server.
Schema Change
  • This update will update the database schema so that's mean schema will and Patch Version will be changed. You will see the same Patch number and Build Number.
Patch Number
  • 16.0.4456.1002
Known Issue with CU

This CU also fix the longer time issue with Installation of packages.

See Also

Please check this Wiki for the SharePoint 2016 Build Numbers.