The product group released the June 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 June 2021 CU are available here:
- KB 5001946 – June 2021 Update for SharePoint Server 2016 (language independent) – This is also a security update!
- KB 5001922 – June 2021 Update for SharePoint Server 2016 (language dependent) – This is also a security update!
The download for June 2021 CU is available here:
- Download June 2021 Update for SharePoint Server 2016 (language independent) – This is also a security update!
- Download June 2021 Update for SharePoint Server 2016 (language dependent) – This is also a security update!
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 June 2021 CU Build Numbers:
Language independent fix: 16.0.5173.1000
Language dependent fix: 16.0.5173.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.
- 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.
Hi Stefan, just want to ask you if there is any issues reported for SharePoint 2016 June 2021 CU? We are planning to install this CU, but just want to play it safe to check with you first.
thats not the right question as we get reports for issues for nearly every CU – while most of them affect only a small number of customers it is impossible to predict if there is one which might affect your environment.
In addition you potentially need to look beyond issues for June CU if your current patch level is older than May 2021 CU. You would need to look at all known issues between the current patch level of your system and the CU you are planning to upgrade to. That means if you are currently on April CU you would need to look for known issues in May CU AND June CU and not just in June CU.
As it is impossible for Microsoft to test all combinations of features and integration with custom or 3rd party solutions we recommend to evaluate each CU in a test environment against all business critical functions before installing it on a production system.
I want to present you with an issue.
In the KB 5001946 – June 2021 Update for SharePoint Server 2016 (language independent), in the Improvements and Fixes section says that:
“Fixes an issue in which you receive the following error message when you try to clear a filter by using indexed columns in a SharePoint list that has many items:
Cannot show the value of the filter. The field may not be filterable, or the number of items returned exceeds the list view threshold enforced by the administrator.”
Before applying this CU we didn’t have this issue (the product was patched with May 2021 CU), but after applying the June CU’s we have this exact issue. So, we didn’t have it before, to be fixed, but we have it now.
We have 2 different instances of Sharepoint Server 2016 that both present this issue now.
Do you know of similar cases ?
I haven’t heard about this behavior.
The fix should resolve the issue and from the implementation of the fix it is unclear to me how it would lead to the opposite behavior.
My recommendation would be to open a support case with Microsoft as that requires a more detailed analysis.
Thanks Stefan, I totally understand it is impossible to predict if there is any issue will affect our environment. FYI, I normally check your blog first and make sure there is no major issue posted here. Your blog is a great help for us before we install any CU in our environments. Thanks again for your help as always.
CVE-2021-34520 Microsoft SharePoint Server Remote Code Execution Vulnerability was reported on 13th July 2021.
Can you please let us know which CU we need to install, as per above blog its asking to install KB5001976 however we should always install Language independent & Language dependent fix.
Can you please suggest and when July 2021 CU will be released.
July 2021 CU for SP2016 was released yesterday:
So in Order to mitigate Server Remote Code Execution Vulnerability we need to apply July 2021 CU as i can see the same KB in it.
Please correct me if i am wrong.
KB 5001976 – July 2021 Update for SharePoint Server 2016 (language independent) – This is also a security update!
KB 5001981 – July 2021 Update for SharePoint Server 2016 (language dependent) – This is also a security update!
After installing KB5001981 SP2010 Workflows will not start after pause tasks 🙁
please see here:
It solved the problem when I did the $farm.EnablePreParseSecurityCheckForWorkflow = $false
I will contact MS … Thanx 🙂
Do you know if the following issue/functionality introduced with the July CU also affects the execution of Nintex workflows? As far as I know, Nintex Workflow uses the SP2010 workflow engine.
„After you install the following July security updates for SharePoint Server, existing Microsoft SharePoint 2010 workflows stop functioning. When this issue occurs, “c42q8,” “c42ra,” or “c42rh” event tags are logged in the SharePoint Unified Logging System (ULS) log.“
it would be great if you would post your comment in the appropriate CU article – your question is about July CU but you posted into June CU.
About your question: the answer is yes and Nintex has already provided guidance on this:
my comment refers to the following link that you posted on 22. July 2021 in June CU. For that reason, I posted my comment there as well. The link refers to July CU.
As expected, no Nintex workflows could be published after the installation of July CU. In the SharePoint Unified Logging System (ULS) log, the event tags “c42q8,” “c42ra,” or “c42rh” were logged as described by Microsoft.
After the extension of the web.config described by Nintex, the Nintex workflows could be published successfully again.
This for information.
Thanks Stefan for the quick reply with the helpful information on Nintex regarding the July CU.
We have updated our test environment with June CU a couple of weeks back. And we started seeing the below 2 issues.
Any update to office documents via edit in browser (we have OOS setup) takes almost 5 minutes to show up. i.e, the modified by and modified date/time shows only the previous version.
We see “virus found” error when uploading items inconsistently. The same file will get uploaded with a retry.
Wanted to see if you know of any similar issues?
I haven’t seen any similar reports. The fact that you see “virus found” indicates that you have a virus scanner integrated with SharePoint. It might be that this virus scanner has a problem which leads to the delays. This could also explain why you see random virus found messages. My suggestion would be to verify if disabling the virus scanner resolves the issue.