The product group released the October 2021 Cumulative Update for SharePoint Server 2019 product family. SharePoint Server 2019 is patched with a language dependent and a language independent fix.
The KB article for October 2021 CU will be available at the following Location in a couple of hours:
- KB 5002028 – October 2021 Update for SharePoint Server 2019 (language independent) – This is also a security update!
- KB 5002034 – October 2021 Update for SharePoint Server 2019 (language dependent)
The download for October 2021 CU is available through the following link:
- Download October 2021 Update for SharePoint Server 2019 (language independent) – This is also a security update!
- Download October 2021 Update for SharePoint Server 2019 (language dependent)
Important: It is required to install both fixes (language dependent and independent) to fully patch a SharePoint server. This applies also to servers which do not have language packs installed. The reason is that each SharePoint installation includes a language dependent component together with a language independent component. If additional language packs are added later (only) the language dependent fix has to be applied again.
It is irrelevant which language you pick on the drop down in download center. Even the language dependent fixes are all in the same package for all languages.
After installing the fixes you need to run the SharePoint 2019 Products Configuration Wizard on each machine in the farm. If you prefer to run the command line version psconfig.exe ensure to have a look here for the correct options.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
SharePoint 2019 October 2021 CU Build Number:
Language independent fix: 16.0.10379.20000
Language dependent fix: 16.0.10379.20000
- Technet: Updated Product Servicing Policy for SharePoint Server 2019
- Blog: SharePoint Patching Best Practices
- Blog: SharePoint Patching demystified
- Blog: Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified (applies also to SharePoint Server 2019)
- Blog: SharePoint does not have a build version. Full Stop.
After installing the SharePoint 2019 CU October (5002028 &5002034). Navigation-Bar (suiteBar) in modern view is permanently black. Custom theme and default themes not working.
this is a known issue since August CU.
The issue is currently under investigation. If this is an important issue for you I would recommend to open a support case with Microsoft to ensure that you are updated on the progress.
Hello Stefan, thanks for your fast reply.
After installing the SharePoint 2019 CU October we miss our topnavigation items under subsites. Is this also known issue?
I’ve noticed that the GuestSharingEnabled is no longer functioning (by a CU change at some point since July 2020, the previous build we had). Looking at the dll, I see a false value has now been hard-coded to return.
I know it’s an unsupported feature,
is there any comment on if this feature is being removed, or why this was disabled?
this functionality is an artefact from the downporting the code from SharePoint Online to SharePoint Server 2019.
It was never intended to work or exists.
As you stated it was an unsupported feature.
Fixes an issue in which the client application can’t be started to open a non-browser-enabled InfoPath form in modern browsers. Additionally, you receive the following error message:
“This form cannot be opened in a Web browser. To open this form, use Microsoft InfoPath.”
After installing this patch the default behaviour of forms library’s “New”-button changed. Before it opened a new empty form and now it just opens a document upload window. As a workaround I needed to change the library webpart’s toolbar to “Show toolbar” and the “New” button creates a new document from the template instead of opening upload dialog.
We can live that because at least now the non-browser-enabled form opens in Infopath client application when clicking the New-button from the library.
However, there’s still one other anomaly regarding this same issue:
Before this patch we needed to open existing non-browser-enabled forms from the ellipsis by the document name and select Open in Microsoft Infopath. If tried to open by clicking just the document name it threw us the above mentioned error message even the library is set to open documents in client application.
After this patch we can now open non-browser-enabled forms just by clicking the name of the document and they open in Infopath client application, However the same error message still appears in the background in the library page and you need to click through it.
if any of these changes are causing any issue it would be required to open a support case with Microsoft to get this investigated.