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:

25 Comments


  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?

    Reply

    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.

      Reply

      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.

        Reply

  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.

    Reply

    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.

      Cheers,
      Stefan

      Reply

      1. Hi Stefan,

        Could you please direct me to where I can find a list of all available security updates for Office Online Server (i.e. something similar to what Microsoft provides for SharePoint: https://docs.microsoft.com/en-us/officeupdates/sharepoint-updates#BKMK_2016). This is where I check for new version releases of Office Online Server: https://docs.microsoft.com/en-us/officeonlineserver/office-online-server-release-schedule, but I have not been able to find a complete lists of updates. I am getting ready to do a fresh install of Office Online Server in a soon-to-be PROD environment and want to make sure I apply all necessary patches to Build: 16.0.10338.20039 released in November 2018.

        Thanks,
        Lisa

        Reply

          1. Hi Stefan,

            Thank you for clarifying that! This link takes me directly to the July patch. Is there a central repository that I can monitor so I am able to find the new security updates, as they are released?


          2. Hi Lisa,
            sorry I don’t know.
            I’m mostly involved with SharePoint and only provide infos for Office Online Server fixes as a curtesy.
            But you can of course monitor my blog for such updates.
            Cheers,
            Stefan


  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.

    Reply

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

      Reply

  4. Update on problem. The cause is not the June 2019 CU update KB 4464594 but one of the Windows Security update. At this time i’m trying to find the update that break SharePoint.

    Reply

  5. Fixed. The problem was the deletion of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\Location registry entry.
    The maintenance group run (unwanted and unrequested) setup of Office on ALL servers (very sad)

    Reply

  6. Hi, is anyone aware of why, since installing the June 2019 CU, the logged in user’s display name no longer appears? Has anyone come across this issue and / or know of a fix?

    https://imgur.com/a/qoPuweF

    Reply


  7. Can we upgrade from SharePoint 2016 Release Candidate version 16.0.4327.1000 to SP 2016 June 2019 CU directly ?

    Reply

    1. Hi Bhavik,
      sorry, but it is unsupported to upgrade from Release Candidate to RTM or later.
      You need to uninstall SP2016 and install RTM and upgrade afterwards.
      Cheers,
      Stefan

      Reply

      1. Thanks Stefan for your prompt response. When I check Configuration Database Version on SP Central Admin it shows following version “16.0.4327.1000” which is Release Candidate.

        However when I check version of SharePoint in Control Panel – Programs & Features there it shows “16.0.4351.1000” which according to Todd Klindt’s is RTM.

        This is causing slight confusion whether the Farm is on RTM build or Release Candidate build.

        Can you help clear the confusion ?

        Reply

        1. Farm must be in Upgrade Available or Upgrade Required State. Please try running PSConfig once and check if Config database version changes to RTM. If it does then I would say you are the luckiest man on planet earth.

          Reply

          1. RTM and RC have the same config db schema version. You cannot differentiate between RC and RTM based on this criteria.


        2. Hi Bhavik,
          16.0.4327.1000 is RTM. So you don’t have a Release Candidate installed. You have RTM installed and you can directly install June 2019 CU.
          You are mixing up the configuration database schema version with the product version.
          There was no schema change between RC and RTM. We only change the schema version if something changes in the schema. With other words: do not expect the database schema version in the central admin to change when installing fixes. It might be but thats not always the case.
          See here for details:
          https://blogs.technet.microsoft.com/stefan_gossner/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/
          Cheers,
          Stefan

          Reply

          1. Hello Stefan,

            Hope you are doing great.

            I’ve installed June 2019 CU “KB4464594” on our SharePoint 2016 farm and successfully completed PSConfig.

            However instead of seeing version “16.0.4861.1000” (June 2019 CU) I am seeing “16.0.4849.1000” (May 2019 CU). I’ve checked version in Central Admin – Manage Servers in farm and version of “Microsoft.SharePoint.dll” however both shows same version.

            I understand that configuration database schema version doesn’t always change when installing updates, can you confirm if its expected to see May 2019 CU version after installing June 2019 CU ?


          2. Hi Bhavik,
            I don’t have a machine in front of me with that patch level but looking into the files that are shipped with this CU (which you can do yourself as well by downloading the csv file with the file information using the link in the KB article) I see that Microsoft.SharePoint.dll is indeed the same as with May CU:

            stsom.dll microsoft.sharepoint.dll 16.0.4849.1000 30848096 14-May-19 02:04

            Cheers,
            Stefan


  8. Hi Stefan
    After applying June 2019 CU and the CU for OOS, we have problems to open PowerPoint files and that in 4 different customer in all stages. Is this expected for this CU? Fixed in July or August? Thanks
    Sebastien

    Reply

    1. Hi Sebastien,
      I would recommend to open a support case with Microsoft to get this analyzed.
      Cheers,
      Stefan

      Reply

Leave a Reply to Gabriele Del Giovine Cancel reply

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