Fix-SeptemberCU-Permission-Problem.ps1
Alternatively you can also remove the NT Authority\system account from WSS_WPG and IIS_IUSRS local security groups of the SharePoint machines.
For more details check this article: Trending Issue: SharePoint fixes fail to install after installation of September 2025 CU
The product group released the June 2026 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 2026 CU should be available at the following locations in a couple of hours:
- KB 5002880 – June 2026 Update for SharePoint Server 2016 (language independent)
This is also a security update! - KB 5002881 – June 2026 Update for SharePoint Server 2016 (language dependent)
This is also a security update!
The downloads for June 2026 CU are available through the following links:
- Download June 2026 Update for SharePoint Server 2016 (language independent)
This is also a security update! - Download June 2026 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 2026 CU Build Numbers:
Language independent fix: 16.0.5556.1005
Language dependent fix: 16.0.5556.1005
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
Hello Stefan,
This is the last CU regarding SP2016 or we’ll have the last one in July?
Permalink
Hi Julien,
there will most likely be another one in July.
Cheers,
Stefan
Permalink
Hi Stefan,
The same like for the SPSE package – the two SP2016 binaries hash doesn’t match the KB’s file hash.
Secondly in the Microsoft Update Catalog the KB5002880 is in higher publication date:
File Name: wssloc2016-kb5002881-fullfile-x64-glb.exe
https://www.microsoft.com/en-us/download date published: 6/5/2026
https://www.catalog.update.microsoft.com date published: 6/9/2026
Can we proceed with the installation or should we wait for update?
Permalink
I am getting differing SHA256 hashes for these patches:
sts2016-kb5002880-fullfile-x64-glb.exe
Expected hash: 9C2F4B450370EA2473221C5CF54F6AFEC76062FA2365E70012CB3B7207049BB5
Download hash: 580F514A69C9DFA55884A5AD9CD28DA9CFBC59EE61C18595E26F5C0891C58C18
wssloc2016-kb5002881-fullfile-x64-glb.exe
Expected hash: 276BF917B2918664CEBC68DC603161C0BFCB2F7F010C11266B7C1644A3A63C4A
Download hash: 0854CA09C2BF23049D2866699708B43DA20F65153A9B8CF66CD855F0515FD547
Previous patch downloads have always had matching hashes on my downloaded files.
Permalink
Hi Stefan,
Can we proceed with the installation of those binaries or should we wait for the hashes updates?
Thank you
Permalink
Hi all,
I have pinged the KB article author to confirm and update the file hashes if required.
Cheers,
Stefan
Permalink
Thanks Stefan – any update on this yet? Our security guys are chomping at the bit to get these applied as quickly as possible (before the Mythos monster gets us 🙂 ).
Permalink
Hi Piers,
from that I see the file hashes in the KB now match the files.
Cheers,
Stefan