August 2019 CU for SharePoint Server 2019 is available for download

The product group released the August 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 August 2019 CU will be available at the following Location in a couple of hours:

  • KB 4475555 – August 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

The download for August 2019 CU is available through the following link:

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

Language independent fix: 16.0.10349.20000

Related Links:


  1. Hi Stefan,
    you do list a security fix for OOS in your post “SharePoint security fixes released with August 2019 PU and offered through Microsoft Update”, but not here.
    Cheers, Sven


    1. Hi Sven,

      That is correct. OOS is neither belongs to the SP2019 nor to the SP2016 product family as it can be used with both versions. In the past I listed the fix in both SharePoint posts which caused confusion with some readers. Then I listed the fix only with SP2019 which again caused confusion with users of SP2016 asking if there is no fix for OOS for SP2016. So I decided not to list it in either of the posts and only list it in the security fix post as all OOS fixes contain security fixes.



  2. I see, I was wondering because you state above “There was no fix for Office Online Server released this month.” and thought you forgot to post the link.


    1. Yeah – sorry for that and thanks for the hint! That is an artefact I forgot to remove.


  3. Hello Stefan.
    I have spotted in above mentioned blog ( that this update requires reboot of server. I ran this update on my test farm with Trevor Seward´s script ( where it is ran with /norestart switch. I got the message “Patch sts2019-kb4475555*.exe installed with Exit Code 0” and reboot was not claimed – there was only “The installation is complete.” message. I went towards with SP Configuration Wizard and finished the patching process without rebooting my server. What do you think abou it? Are there reboots required, especially after 1st phase (installing binaries) of patching? When I checked my farm there was 0 errors and 0 warnings in “Update status” a “No action required” within “Review database” status page in Central Administrattion.


    1. Hi Ladislav,
      SharePoint fixes only require a restart if a file that needs to be updated is in use.
      The update process stops all SharePoint processes before applying the installation. So the files should not be in use and no restart should be required.
      Exceptions can be if there are other custom processes around which have the files in use.


      1. May these exceptions be “silenced” with /norestart switch? I mean there is need to restart, but I do not know because I have supressed the reboot message? Thanks for your previous quick response 🙂


        1. Sorry, I have never used a /norestart switch. Not sure if this suppresses any messages.


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.