June 2019 CU for SharePoint Server 2016 is available for download

The product group released the June 2019 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 2019 CU are available here:

  • KB 4464594 – June 2019 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 4461507 from April 2019

The download for June 2019 CU is available here:

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 2019 CU Build Numbers:

Language independent fix: 16.0.4861.1000

To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.

Related Links:


  1. For applying the June 2019 CU, Upgrade-SPContentDatabase gives: ” does not need to be upgraded”. I’ve never seen this before, as updating the database schema was always required after installing the bits. This is of course prior to running psconfig on any of the SharePoint servers. Is this expected for this CU?


    1. I don’t know for the June CU but not all fixes require an upgrade of the content database schema. Other databases might still require a schema upgrade – or not.
      It is up to the specific fixes that are included.


      1. I have applied the June CU to another farm that had the March 2019 CU (KB4462211) today. That did upgrade the content databases. My earlier post was for a farm that had May 2019 CU, so the previous patch levels made the difference. It would be very helpful if you/Microsoft could tell ahead of time whether the database schema upgrade is needed or not for each CU release, as it would affect the maintenance window greatly for those who have terabytes of data. Thanks.


  2. Soundn’t the Office Online server update be listed here also? I see that there is an update listed for SharePoint 19 but not here for 16.


    1. There is no Office Online Server 2016 or 2019. Just one Office Online Server. It is a so called “evergreen product”. Office Online Server can be used with SharePoint Server 2019 and 2016.
      I once posted the update in both articles (for SharePoint Server 2016 and 2019) and it caused confusion as it looked as if there are two different versions for both products. So I decided to post Office Online Server updates with SharePoint Server 2019 only.



  3. Big problems with SP 2016 June 2019 CU. When applied every Sharepoint in a test farm (2 Web FrontEnd with Distributed Cache + 2 Application + 2 Search) are broken. Every single SharePoint service (except Administration Service) fail on start with no clear error code (no error code at all). The Psconfig fail at step 2 with the error “the local farm is not accessible”. Same Error for PowerShell cmdlet.
    The machines are all 2012 R2. The updates are executed by Windows Update and include others (58) WIndows component updates (security and .NET). Maybe the error correlated with this big number of Windows updates execute with the June 2019 CU? The machine was backuped before update and restored as previous state and the farm come back to operation but the DB was updated with new version number.


    1. Hi Gabriele,
      this is not a known issue. I would recommend to open a support case to get this analyzed.


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.