Update for SharePoint Server 2016 (March 2018 CU)

A new cumulative update for SharePoint Server 2016 has been released (March 2018 CU).
This CU includes both Feature Pack 2, which has been included since the September CU (September 2017 CU), and the previous Feature Pack 1.

SP Build: 16.0.4666.1002 (language independent)
SP Build: 16.0.4666.1000 (language dependent)

SharePoint 2016 CU – KB articles describing the CU:

KB 4018293 – March 2018 Update for SharePoint Server 2016 (language independent)
KB 4011687 – March 2018 Update for SharePoint Server 2016 (language dependent fixes)
KB 4011023 – March 2018 Update for Office Online Server 2016

SharePoint Server 2016 CU – CU download link:

After installation, remember to run the SharePoint 2016 Products Configuration Wizard (SharePoint 2016 Products Configuration Wizard), or the following command:
PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install

Notice

Feature Pack 2 also includes all functionality from Feature Pack 1.

Always install both packages in this order:

language independent (updates language-independent components and increases the SP Build version)
language dependent (updates language-dependent components)

For language-dependent packages, it does not matter which language you select, as each package contains updates for all languages.

If you install a new language pack on your SharePoint Server 2016 farm, you must then reinstall the language-dependent update package.

Remember that Distributed Cache must also be updated alongside SharePoint; see How to update Distributed Cache correctly and for Office Online Server, you must have the current RTM release; see How to update Office Online Server.

Included fixes and improvements

This CU includes the following fixes and improvements.

SharePoint Server 2016

This security update contains improvements and fixes for the following nonsecurity issues in SharePoint Server 2016:

After updating and upgrading a SharePoint 2016 farm by using a Public Update, some servers may still report that they’re in the “Upgrade Required” state, even though upgrade had completed successfully. This issue is fixed in this update.
When you use Norwegian (Bokmål) or any other locale that has the same separator for dates and times, you receive the following error message when you verify the date and time fields:

index was outside the bounds of the array
You cannot open a followed document online if its filename contains the ampersand character (&). Additionally, you receive the following error message:

Error happened:
Item does not exist. It may have been deleted by another user.
The default PDF parser doesn’t parse correctly some documents that are created by Arbortext PDF Creator.
When you add a user to a SharePoint group through the REST APIs, you receive an “UnauthorizedAccessException” error message even though the operation is completed.
After migration from SharePoint Server 2013 to SharePoint Server 2016, the InfoPath forms that use the User Profile Service web service (UserProfile.asmx) are not working as expected.
In lists that have a Multiple Lines of Text column, when the Enhanced rich text (Rich text with pictures, tables and hyperlinks) option is selected, data in tables cannot be used for searching.
When the Version column in a list is indexed, you cannot add or update an item or a document in the SharePoint document library list. Additionally, you receive an error message that resembles the following:

The URL ‘Shared Documents/filename.doc‘ is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.
This update improves the indexing compatibility for some malformed PDF files.
This update changes the hotfix files to make sure that all files that are required for SharePoint Framework (SPFx) are included.

This update contains the following improvements:

Corrects the translation when you follow a hashtag in the German version of SharePoint Server 2016.
Provides translation for the UI setting for the Search Web Part loading behavior in SharePoint Server 2016.

Project Server 2016

This security update contains improvements and fixes for the following nonsecurity issues in Project Server 2016:

When the Project permission “View the Project Schedule Details in Project Web App” is enabled, you may see views and data that you don’t have permission to see.
Actual work that’s applied as a part of a status updates approval doesn’t always appear in the given project.
When you open and edit a project, and then save back to Project Server 2016, you may see an error message in the Unified Logging System (ULS) logs that resembles the following:

[PS_AC][Number] Invalid bool pid 188745088 (B400580) for container Task
- When you open and edit a project, and then save it in Project Server 2016, you may receive an error message that has some of the following elements in it:
  
  ActiveCacheQueuedMessageExecutionError
  error=”System.InvalidCastException: Specified cast is not valid”
- Consider the following scenario:
  - You have a Project Web App (PWA) site and Project Server 2016 in your organization.
  - You log on to a PWA instance, and then create an enterprise custom field for the resource entity and another enterprise custom field for the project entity.
  - You start Project Professional 2016 and connect to Project Server 2016. Then, you add a resource and set a value for the custom field of the resource.
  - You save the project and check it in.
  - In PWA, you locate the Project Center, drill into the project, and then select a Project Details Page (PDP), if you have not already selected it.
  - You make a change to the project custom field, and then you save the project from the PDP.
  - In Project Professional 2016, you open the project and view the custom field value.
  In this situation, the value of the resource custom field is missing.

Office Online Server 2016

This security update resolves vulnerabilities in Microsoft Office that could allow remote code execution if a user opens a specially crafted Office file. To learn more about these vulnerabilities, see Microsoft Common Vulnerabilities and Exposures CVE-2018-0919.