The product group released the June 2019 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 June 2019 CU will be available at the following Location in a couple of hours:
- KB 4475512 – June 2019 Update for SharePoint Server 2019 (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 4462221 from April 2019
- KB 4475511 – June 2019 Update for Office Online Server – This is also a security update!
The download for June 2019 CU is available through the following link:
- Download June 2019 Update for SharePoint Server 2019 (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 4462221 from April 2019
- Download June 2019 Update for Office Online Server – 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 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.
SharePoint 2019 June 2019 CU Build Number:
Language independent fix: 16.0.10346.20001
Related Links:
- Technet: Updated Product Servicing Policy for SharePoint Server 2019
- 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.
Permalink
Permalink
Hi Stefan, I have a naive question regarding the update process. Some monthly CU have a language dependent update that needs to be installed together with the CU, but not all. And I understand that CU are cumulative. Let’s say I have already installed the February CU, and now I would like to install the June CU, which does not have a language dependent update. Do I only have to install the June CU (which has no language dependent update available), or should I also install the latest available language patch (April 2019) together with the June CU ?
Thank you very much
Permalink
Hi Jerome,
you should install the most recent language dependent fix as well.
Cheers,
Stefan
Permalink
Hello there,
the question is what sequence is correct: install sts2019-kb4464518 and wssloc2019-kb4462221 (both from 4/2019) with SPCW and later the sts2019-kb4475512 (from 6/2019) with SPCW, or skip sts from 4/2019 and install the combination sts2019-kb4475512 with wssloc2019-kb4462221 followed by SPCW? I went the first alternative on my farm, with great Trevor Seward´s script https://github.com/Nauplius/SharePoint-Patch-Script.
Best regards,
Ladislav
Permalink
I’m not sure what SPCW is but aside of that you only have to install the most recent for each of these files. No need to install an older one.
So skip sts2019 from 4/2019 and install sts2019 from June and wssloc2019 from April.
Permalink
Thanks for reply, Stefan.
Just to clarify: SPCW stands for SharePoint Products Configuration Wizard (psconfigui.exe).
I installed fixes on my test farm on two runs, because I thought that they are “tight” together somehow – I mean sts and wssloc from 4/2019 – both with build number 16.0.10343.20000. It seems I was wrong – they are not “in synchro” and I should save myself from one run of SPCW. Now I have KB4464518 superseded by KB4475512 in CA´s Manage Patch Status page.
Permalink
The last release of OfficeOnlineServer is from November 2018. Since then, some patches have been tagged as Security fixes.
Are those patches still cumulative? So can i move from November 2018 to June 2019 directly?
Permalink
Yes.
Permalink