August 2019 CU for SharePoint Server 2016 is available for download

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

  • KB 4475549 – August 2019 Update for SharePoint Server 2016 (language independent) – This is also a security update!
  • KB 4464553 – August 2019 Update for SharePoint Server 2016 (language dependent)

The download for August 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 August 2019 CU Build Numbers:

Language independent fix: 16.0.4888.1000
Language dependent fix: 16.0.4888.1000

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

Related Links:


  1. Hi Stefan,

    after installing the latest security update am missing all custom managed properties in the Sort-Dropdown in the Query Builder (Search Result Webpart). There seems to be some kind of a kill switch for the custom properties. Is there any way to determinate if this switch is active or not on my platform? Right now I don’t know if this switch is the reason for it or if there are other reasons I need to look into.

    Unfortunally I don’t know when those managed properties disappeared, since I really didn’t look into that webpart for some time. I installed the CU (+language dependent) and executed the SPCW (command line, then UI) but it the properties seem still not to be shown.


    1. Hi Joerg,
      I would recommend to open a support case with Microsoft to get this issue analyzed.


  2. Hi Stefan,

    Office Online Server Patch is not released for SharePoint 2016 this Aug 2019?



  3. Hi Stefan,

    Thanks for reply.

    but when i check the file name it seems to be for Server2019.

    File Name: wacserver2019-kb4475528-fullfile-x64-glb.exe

    please let us know is there any link that we can get for 2016



    1. Hi Praveen, the name does not matter.


  4. Hi Stefan,

    we have SP 2016 with OOS but while running the patch we are seeing error “expected version of the product was not found on the system”



    1. A new release of OOS was published in November 2018. All patches after that require the November 2018 release.


  5. Stefan, I plan on installing the security patch but if I don’t install the language dependent patch will it be picked up next time I install a CU?


    1. Hi Nicola,
      You can install the security fix without the language dependent fix.
      I’m not sure what you mean with “will it be picked up”.


  6. Hi Stefan,

    Some “general” questions. Hope it’s ok in this blogpost.

    In an old post you said that you only posted the link to the Uber packages. Thus, always meaning that the CU now truly is cumulative for all services. If it’s not an Uber package, then the “CU” only means Cumulative for the services that are being patched, i.e excel services, is that correct? Should you, in your blog posts state, “The KB articles for August 2019 UBER CU are available here” or is that redundant?
    When you add “This is also a security update!” for a link to Uber CU, what should we do with that information? Does it impact our routine when patching sharepoint or is it just an FYI?
    Is there a correct order when applying patches? Both in terms of which type of server (WFE/app) and language dependant/independant?
    We have 4 server.
    2 App/CA
    2 WFE/DC
    Which patchfile should we run first and on which server first?
    In what order should we run PSCONFIGGUI? Is it one at a time and on which server first?

    After these questions I guess the farm is patched? 🙂


    1. Hi Daniel,
      question 1: yes that would be redundant.
      question 2: this is just FYI
      question 3: it is usually recommended to start patching with one of the the servers hosting the central admin. it does not matter if you first install language dependent or independent.
      question 4: again I would start on one of the servers hosting the central admin. you need to wait for this psconfig run to complete before executing it on other machines to prevent update conflicts. After psconfig is completed on the first machine you need to run it on all other machines to perform local changes. you can run psconfig in parallel on all of these machines now as the database updates were completed by the first run already. Of course if you are making use of zero downtime patching you can only run it on those machines which you removed from the load balancer.


      1. Excellent answers! Thank you.


  7. Hi Stefan!
    Any documentation somewhere or is it possible getting some more details about what has improved, from the statement “Improved SharePoint search compatibility with PDF files.”? Currently we struggle with searching large PDFs, so we’re curious.

    Cheers, Gunnar


    1. Hi Gunnar,
      there is no additional documentation around this.
      The fix addresses a very specific problem when the file trailer dictionary in a PDF file contains string literals, with an escaped backslash character sequence that precedes a closing parenthesis. This caused an internal error which prevents such a document from being indexed.


  8. Hello,

    Kindly asking for opinion on my suggestion.
    We all know that after we install CU and before we run „SharePoint 2016 Products Configuration Wizard“, we have to run in SharePoint 2016 Management Shell (as Administrator) command „ Get-SPContentDatabase | Upgrade-SPContentDatabase“. Is that right?
    If so, pls Stefan can You in You documentation for every next monthly CU ( August 2019 CU for … available for download) where You writte about procedure „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.“ Also writte about the command „Get-SPContentDatabase | Upgrade-SPContentDatabase“.

    Many tnx with kind regards,


    1. Hi Petra,
      your statement is not correct. PSConfig will perform all required database upgrades and running Upgrade-SPContentDatabase before is not a required.
      On the other hand running Upgrade-SPContentDatabase before running PSConfig can have a benefit in case you have a large number of databases as you can run upgrade-spcontentdatabase in parallel in different PowerShell windows while PSConfig sequentially upgrades the databases. So the time to upgrade all DBs is much shorter. On the other hand for SP2016 it does not matter as – unlike SP2013 and earlier – there is no downtime during database upgrade.


      1. Many tnx for clarification!!


      2. Hi Stefan!

        I have some questions/observations:

        1) My findings confirm Petra’s experience above. For example, after installing the Aug 2019 CU for SharePoint 2016 (KB4475549 and KB4464553) on my farm, the Configuration Wizard GUI gave me the error:

        “Upgrade Timer job is exiting due to exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: The upgraded database schema doesn’t match the TargetSchema”

        The only solution was to then run “Get-SPContentDatabase | Upgrade-SPContentDatabase” and then re-try the Configuration Wizard GUI. Then it completed successfully.

        2) Is Microsoft still releasing small “security only”-fixes for SharePoint? Or is the monthly CU the only delivery mechanism in use? The CU:s seem to contain a little bit of everything: security fixes, bugfixes and improvements… 🙂

        3) I know you mention above that the CU “is also a security update”, but a very confusing thing is that the update KB4475549 – which is half of Aug 2019 CU – is just modestly labeled “Security Update” in WSUS… 🙁

        4) Microsoft’s Servicing Policy page calls all updates PU, but you (and we all) call them CU… who’s right? 🙂

        Thanks for a great resource!


        1. Hi Will,
          1) I haven’t seen this on any of the farms I tried the CU. If this is a concern for you and you still have a farm where that occurs I would recommend to open a support ticket with Microsoft to get this analyzed.
          2) Microsoft has never released security only fixes for SharePoint. The packages which included security fixes always also included all non-security fixes for the patched component since RTM.
          What has changed with SharePoint 2016 and 2019 is that we no longer have 30+ components which could be patched individually but only 2 components. If a security fix is released for one of these components then – as always – all the non-security fixes for the patched component will be patched as well. Of course the granularity of patching has gone done from 30+ components to just 2.
          3) yes I agree – wording can be confusing here here but see 2) for the technical details
          4) both. all patches we release for SharePoint are cumulative. Always. So all are CUs. When the decision was done to release hotfixes no longer from a separate hotfix server but from download center the product group changed the naming to “public updates” as everything on download center is seen “public”. But that conflicts with the earlier meaning of public updates where was reserved for the security updates. I just kept the original wording to be able to separate those packages which include (new) security fixes from the other. As you noticed for SharePoint 2016 and 2019 the difference is small as usually 50% of the CU (and with September 100% of the CU) also includes security fixes.


          1. Hy Will,

            yesterday I was installing August 2019 CU on my test ShP2016 farm. After instaling KB 4475549 and restar, I run wizard SharePoint 2016 Products Configuration Wizard. The wizard finished with error. The same error I recived last time and the same error as you. 🙁 The I run command “Get-SPContentDatabase | Upgrade-SPContentDatabase”. And the wizard finish OK. That was my result from yesterday. Because od the answer of Stefan on my post, I have shame to writte again today. But when I find you post and read about your situation, I decidet to writte. My ShP farm exist of 1 ShP server and 1 dedicated SQL server.

            Kind regards, Petra 🙂

          2. Hi Petra,
            I would recommend to open a support case when you experience such issues to get this analyzed.

Leave a Reply

Your email address will not be published. Required fields are marked *

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