A new cumulative update for SharePoint Server 2016 has been released (April 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: independent CU: 16.0.4678.1001, dependent CU: 16.0.4678.1000
SharePoint 2016 CU – KB articles describing the CU:
- KB 4018336 – April 2018 Update for SharePoint Server 2016 (language independent)
- KB 4018340 – April 2018 Update for SharePoint Server 2016 (language dependent fixes)
- No Office Online Server 2016 update was released with this CU
SharePoint Server 2016 CU – CU download link:
- Download April 2018 Update for SharePoint Server 2016 (language independent)
- Download April 2018 Update for SharePoint Server 2016 (language dependent fixes)
- No Office Online Server 2016 update was released with this CU
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 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 the following Microsoft Common Vulnerabilities and Exposures CVEs:
This security update contains improvements and fixes for the following nonsecurity issues in SharePoint Server 2016:
- The look-up fields such as FileRef and FileDirRef fields cannot be filtered by using SharePoint Representational State Transfer (REST) APIs.
- When you select the See conversations link of a followed user, you receive the following error message:
Looks like somebody deleted this conversation.
- You still receive status report reminders even after you are removed from the response list.
- This update fixes an issue that a double hash tag symbol (##) displays in an information message in all languages when you start following a hash tag (#).
Project Server 2016
This security update contains improvements and fixes for the following nonsecurity issues in Project Server 2016:
- Portfolio Analysis View displays incorrect availability and requirements information in certain conditions, depending on data and planning horizon settings.
- You cannot see Queue Job status because duplicated Project Publish reporting causes the Manage Queue page not to be loaded. In addition, you receive the following error message:
Sorry, something went wrong
An unexpected error has occurred - The Capacity Planning Views don’t always display project assignments for each selected resource.
- When you change the definition of the Task Status field in the Task content type, the “In Progress” value that was deleted previously still appears occasionally.
- When the assignment actual work is missing in the published database, the timesheets pages don’t load in single entry mode. In addition, you receive the following error message:
The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.
- When you create resource engagements from Project Web App(PWA), the PWA always uses 8 hours for one day instead of the expected setting from Enterprise Global.
- When you open projects from Project Center in Project Web App by using Internet Explorer 11 in Windows 7, you receive the following error message in the browser:
Action Not available -Project Professional needs to be installed to open the project. Install project and try again
- The title of Project Detail Pages displays encoded Unicode characters unexpectedly. For example, the character “&” in the title becomes “&”.
- You cannot create customer views that are based on filtering and grouping in Project Web App.
Komentáře