A new cumulative update (December 2022 CU) has been released for SharePoint Server 2019.
SP Build:
16.0.10394.20016 (Language independent CU)
16.0.10393.20000 (Language dependent CU)
SharePoint 2019 CU – KB articles describing the CU:
- KB 4461512 – December 2022 Update for SharePoint Server 2019 (language independent)
- KB 5002310 – December 2022 Update for SharePoint Server 2019 (language dependent)
SharePoint Server 2019 CU – CU download links:
- Download December 2022 Update for SharePoint Server 2019 (language independent)
- Download December 2022 Update for SharePoint Server 2019 (language dependent)
After installation, remember to run the SharePoint 2019 Products Configuration Wizard or the following command:
PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install
Important notes
Always install both packages in this order:
- language independent components (core CU)
- language-dependent components (language CU)
For language-dependent packages, the language you select does not matter because each package contains updates for all languages.
If you install a new language pack on a SharePoint Server 2019 farm, you must reinstall the language-dependent update afterwards.
Remember to keep Distributed Cache updated as well as SharePoint. See How to update Distributed Cache correctly (in Czech).
Note for this CU:
The original core update KB5002311, build 16.0.10393.20000, was replaced by KB 4461512, released on December 22, 2022. Install the corrected package over the original if it is already installed; otherwise install the corrected package directly. In either case, KB 5002310 is also required.
SharePoint Server 2019 must be installed. Installation may require restarting the computer.
The original security package specifies the release version of SharePoint Server 2019 as its prerequisite.
The original December CU could show incorrect people-field information across site collections. Web applications containing just one site collection should not be affected, and other SharePoint versions are unaffected. The correction changes only the language-independent component; the language-dependent package was not affected.
Browsing to a SharePoint website can fail with an invalid-URL error when its URL ends with a string matching a file extension blocked by that web application. See KB5023406.
Microsoft lists the April 11, 2023 SharePoint Server 2019 security update KB 5002373 as the fix for this URL problem.
Included fixes and improvements
The following overview summarizes the fixes and improvements in this CU based on the official Microsoft KB articles.
SharePoint Server 2019
-
The December security release addresses the SharePoint Server remote code execution vulnerability CVE-2022-44690.
-
The December security release addresses the SharePoint Server remote code execution vulnerability CVE-2022-44693.
The corrected December CU includes the following SharePoint Server 2019 fixes and changes:
-
Person fields in lists from different site collections could display the wrong user. KB 4461512 corrects this problem.
-
In the classic experience, a URL produced by Get a link could send the user to the default zone.
-
Adding a link file through + New > Link could result in access being denied.
-
A key collision in
User Profile to SharePoint Synchronization for Groupscould prevent the group name from updating automatically in Active Directory. -
On My Site, editing the Top link bar or Quick launch page could trigger a Site Settings exception.
-
Liking a list item could take a long time when many other users had already liked it.
-
The Active Directory profile import timer job could omit synchronization of the
assistantproperty. -
Secure access is enabled for
WorkflowTaskPane.aspx. -
Comments could be missing from exported content or from the destination site after export and import. The new
-IncludeUserSecurityparameter addresses this when used with bothExport-SPWebandImport-SPWeb, for example:Export-SPWeb -Identity "http://spse/sites/team_test1" -Path "C:\exported\exported.cmp" -Force -IncludeUserSecurityImport-SPWeb -Identity "http://spse/sites/team_test1" -Path "C:\exported\exported.cmp" -IncludeUserSecurity -
Uploading a file whose name contained invalid characters could produce the wrong error message.
The following fixes require both KB 5002310 and the corrected core update KB 4461512:
-
Filtering a taxonomy column could return only 140 terms.
-
Filtering a view by a managed metadata column could make breadcrumb navigation show an ID in place of a label.
-
A lookup field’s
DateTimefilter could fail when regional settings used a region other than the US. -
The modern People web part could omit photos for trusted users and forms-based authentication (FBA) users.
-
On the Change the look settings page, navigating with the up or down arrow did not automatically select theme radio buttons.
-
In Project Server, restoring metadata in Project Web App (PWA) could cause the reporting database refresh to fail.
-
While one user published a project, other users could be unable to start Project desktop and connect to Project Server, open their own projects or projects for read-only access, or open the schedule web part. Team members could lose access to their tasks page, and administrators to the Force Check-in Enterprise Objects page.
Komentáře