The product group released the February 2021 Cumulative Update for SharePoint Server 2016 product family.
This CU also includes Feature Pack 1 which was released with December 2016 CU and Feature Pack 2 which was released with September 2017 CU.
The KB articles for February 2021 CU are available here:
- KB 4493195 – February 2021 Update for SharePoint Server 2016 (language independent) – This is also a security update!
- There was no language dependent fix released this month. The most recent language dependent fix is KB 4493167 from January 2021 CU
The download for February 2021 CU is available here:
- Download February 2021 Update for SharePoint Server 2016 (language independent) – This is also a security update!
- There was no language dependent fix released this month. The most recent language dependent fix is KB 4493167 from January 2021 CU
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 2016 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.
SharePoint 2016 February 2021 CU Build Numbers:
Language independent fix: 16.0.5122.1000
To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
Related Links:
- Technet: Updated Product Servicing Policy for SharePoint Server 2016
- Blog: SharePoint Patching Best Practices
- Blog: Common Question: What is the difference between a PU, a CU and a COD?
- 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 Patch Build Numbers Powershell Module
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified
- Blog: SharePoint does not have a build version. Full Stop.
Permalink
Hi Stephan,
Does the February 2021 CU for SharePoint Server 2016 include the fixes for these 2 issues?
RSS Webpart is broken after installing Dec 2020 CU
https://blog.stefan-gossner.com/2020/12/18/trending-issue-sharepoint-rss-webpart-is-broken-after-installing-december-2020-cu/
and Upload Of files large than 100MB October CU 2020
https://blog.stefan-gossner.com/2020/11/10/trending-issue-upload-of-files-larger-than-100-mb-fails-since-october-2020-cu/
Permalink
Hi Henry,
yes, both issues are fixed in this CU. The fix for the 100 MB issue was already included in December 2020 and January 2021 CU.
Cheers,
Stefan
Permalink
Thank you so much Stefan as well
Permalink
Hi Stefen,
we have already installed Jan 2021 CU and for Feb 2021 CU there is no language dependent fix released this month, so if we want to install this month(FEB 2021) CU then we need to install only language independent right?
Thanks
Praveen
Permalink
Hi Praveen,
yes – if you already installed the Jan 2021 CUs language dependent fix you only have to install the language independent one released in February.
Cheers,
Stefan
Permalink
Hello Stefan, we haven’t installed the January CU yet and would actually install the February CU directly. Then we wouldn’t have a language-dependent update.
Do we need to apply both January updates or can we apply the February language-independent update with the January language-dependent update?
Can you recommend us for this?
Regards
Christian
Permalink
Hi Christian,
in this case you only need to install the language independent fix from February and the language dependent fix from January.
Cheers,
Stefan
Permalink
Thank you for the recommendation.
Is there a sequence to consider?
Regards
Christian
Permalink
No.
Permalink
The February CU has a documented issue if you have the Document ID Feature enabled….links broken in the document panel ellipse for the link to document. In our lab we have determined this is the case. Any idea when they will have fix for this…the workaround just isn’t user friendly for users? Can’t apply CU tell a fix available.
Permalink
Hi Allen,
the current plan is to release a fix with March CU.
Cheers,
Stefan
Permalink
I figured that would be the case Stefan. Thanks for the confirmation.
Regards,
Allen
Permalink
Hi Mr. Stefan, so since language dependent is not included in Feb, then we need to install it from Jan, right ?
Permalink
Correct.
Permalink
Hi Stefan,
we have installed the Feb 2021 CU for sharepoint 2016 , but after the upgrade, it shows the configuration database version as 16.0.5116.1000 and not the expected version 16.0.5122.1000
Permalink
Hi Shruthi,
not all sharepoint fixes update the configuration databas schema version. As some fixes do not touch the database.
See here for details:
https://blog.stefan-gossner.com/2014/10/23/common-question-why-does-the-version-number-on-the-servers-in-farm-page-not-change-after-installing-october-cu/
https://blog.stefan-gossner.com/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/
Cheers,
Stefan
Permalink
Hi Stefan,
I applied February 2021 PU, patching is done but it failed to run PSconfig. as it shows “Failed to update “Prod_search_db” because the database is read only but it’s not. I made sure that i logged into sql server accessed my database and saw the properties it is set to “False” which is correct. Not sure why it cannot accept.
Any work arounds ?
Thanks!
Permalink
Hi DK,
I haven’t seen this. If you need assistance to resolve this issue I would recommend to open a ticket with Microsoft Support.
Cheers,
Stefan