The product group released the August 2020 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 August 2020 CU are available here:
- KB 4484473 – August 2020 Update for SharePoint Server 2016 (language independent) – This is also a security update!
- KB 4484476 – August 2020 Update for SharePoint Server 2016 (language dependent) – This is also a security update!
The download for August 2020 CU is available here:
- Download August 2020 Update for SharePoint Server 2016 (language independent) – This is also a security update!
- Download August 2020 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 August 2020 CU Build Numbers:
Language independent fix: 16.0.5044.1000
Language dependent fix: 16.0.5044.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 Stefan,
If a SharePoint Farm is behind, like at the March or April of 2020 Patch Level, is it best to just install the August Updates? Both the Language dependent and independent updates to get it up to date and then proceed with PSConfig? Thanks!
Jess
Permalink
Hi Jess,
yes thats all you have to do.
Cheers,
Stefan
Permalink
Hi Stefan, after installing de CU august 2020 we experience issues with Internet Explorer and opening pdf files within a document library. You can click on the link, but nothing happens. the page gets refreshed. If you do the same in Edge/Chromium, it works fine. When using the SharePoint search and clicking on pdf links through the result page, it does work. The problem only appears within de SharePoint document library.
Did you hear any issues regarding pdf’s and opening in IE?
Permalink
Hi Peter,
I haven’t heard about this.
If I understand correctly that we working before you applied august CU. Which patch level did you have before applying August CU?
If you need this analyzed in more detail, please open a ticket with Microsoft Support.
Cheers,
Stefan
Permalink
Hi Stefan,
Before this update we were on the october 2019 CU update. It did work before. I did some more searching and found out 2 things
1. Changing the ‘document modus’ (pressing F12 developer bar) from 10 to 11, it works. These are plain vanilla collaboration sites with meta http-equiv=”X-UA-Compatible” content=”IE=10″. Changing this to IE=11 manually, it works again.
2. In the console log when refreshing the page in a document library I get an error about the ‘start.js’ file. this is an out of the box .js file from Microsoft.
Regards,
Peter