August 2025 CU for SharePoint Server 2019 is available for download

20 Comments

1. 

   Jay
   On 13. August 2025 Permalink

   Have installed 2769 and 2770 on the app, WFE and search servers.
   Rebooted all 3 then ran psconfig starting with the central admin server. All claimed success.
   Our main web app is working fine but I cannot open central admin nor a different web app.
   Without access to CA I can’t see the issue with the 2 failing web apps. I have checked all services are running and rebooted the central admin server – still no good.
   I’ve checked the event viewer on the CA server and there are lots of entries that talk of database connections, claims, kerberos and the correlation ID speaks of an issue with mapilab (Harepoint – which is our monitoring software) but given the main web app is running fine I am not convinced these are the cause. Anyone else had anything similar since applying these 2 updates?

   Reply
   1. 

      Stefan Goßner
      On 13. August 2025 Permalink

      Please check the ULS log for details.
      Cheers,
      Stefan

      Reply
   2. 

      Adrian
      On 13. August 2025 Permalink

      Hi Jay,

      on my DEV machines, updating SP2016 was fine but SPSE has all web applications (CA and actual SP sites) throw and HTTP 500 Internal server error. Now onto test, my SP2016 is throwing the same.

      Only had superficial looks into the logs so far due to time constraints. So I cannot give you more than my anecdotal data point at the moment. If I fine stuff, I’ll let you know.

      Personal thought: In SPSE there was some SQL driver/client change, might be related to that? Maybe some Kerberos/TLS1.2 related stuff messing with database communication?
      I’m seeing a lot of SQL permission stuff that us usually irrelevant and due to tighter permissions. However, even giving the service accounts sysadmin temporarily does not stop them. So I’m suspecting some DB comms/protocol/driver issue?

      Reply
      1. 

         EH
         On 2. September 2025 Permalink

         Hello Adrian,

         Have you found any solution? We are experiencing the same issue and are currently blocked on our SP 2016 farm.
         Stefan, do you have any thoughts on this?

         Thanks in advance !

         Reply
2. 

   Jay
   On 13. August 2025 Permalink

   Thanks all. Should have mentioned this was 2019 on prem.
   After half a day using powershell (amazing how you are hamstrung without central admin) and googling I went back to the app server and re-ran PSCONFIG even though this was the first server I ran it on and bingo everything came back to life!

   Reply
3. 

   Balkishan Badugu
   On 13. August 2025 Permalink

   Hi Stefan,

   Along with KB5002769 and KB5002770, do we need to install KB5064829 as well?

   Reply
   1. 

      Stefan Goßner
      On 13. August 2025 Permalink

      Hi Balkishan,
      5064829 is a fix for Exchange – not for SharePoint.
      Cheers,
      Stefan

      Reply
4. 

   Adam Szafraniec
   On 21. August 2025 Permalink

   HI,

   I am installing Sharepoint August 2025 update and I get issues with Sharepoint Workflow 2010 (not 2013) ,I get info that the Workflows dosen’t run. It is installed on front at this moment.

   Reply
   1. 

      Stefan Goßner
      On 21. August 2025 Permalink

      Hi Adam, in the last couple of months a large number of restrictions for SP2010 workflows have been implemented – so to assist it would be important to know which CU was installed before you applied August CU?

      Reply
5. 

   Adam Szafraniec
   On 21. August 2025 Permalink

   Before was installed:
   KB 5002580 – April 2024 Update for SharePoint Server 2019 (language independent)
   This is also a security update!
   KB 5002538 – April 2024 Update for SharePoint Server 2019 (language dependent)

   Reply
   1. 

      Stefan Goßner
      On 21. August 2025 Permalink

      In this case chances are high that you are running into this issue from September last year:
      https://blog.stefan-gossner.com/2024/09/13/trending-issue-problems-with-workflows-after-applying-september-2024-cu-for-sharepoint-2016-2019-se/

      Reply
6. 

   Adam Szafraniec
   On 21. August 2025 Permalink

   Which webconfig file should I modify?

   Reply
7. 

   Adam Szafraniec
   On 21. August 2025 Permalink

   This?
   For all Virtiual directories and all servers ?

   Reply
   1. 

      Stefan Goßner
      On 21. August 2025 Permalink

      For all webapplocations. The best approach is to us a SPWebConfigModification operation which ensures that the changes are automatically applied to all servers – even servers added later to the farm.
      Cheers,
      Stefan

      Reply
8. 

   Adam Szafraniec
   On 21. August 2025 Permalink

   And last question: if I will do step back to April 2024 CU, all will back and WF will be working ?

   Reply
   1. 

      Stefan Goßner
      On 21. August 2025 Permalink

      Uninstalling a SharePoint CU is not possible. And it would be tremendously risky considering the CVE from last month. The correct solution is to review the ULS log and add the necessary authorized Type entries.

      Reply
9. 

   Adam Szafraniec
   On 22. August 2025 Permalink

   Stefan, Thanks for the support.
   All looks good

   Reply
   1. 

      Stefan Goßner
      On 22. August 2025 Permalink

      Perfect! 😊

      Reply
10. 

    Emmanuel Umozurike
    On 28. August 2025 Permalink

    Should we rotate machine keys after applying the August 2025 cumulative update?

    Reply
    1. 

       Stefan Goßner
       On 28. August 2025 Permalink

       Only if you did not do it after applying the July 21st security fixes.

       Reply