July 2025 CU for SharePoint Server 2019 is available for download

13 Comments

1. 

   Desmond Kung
   On 13. July 2025 Permalink

   Has anyone met an issue like this when running psconfig? Started from June’s CU “An exception of type System.UnauthorizedAccessException was thrown. Additional exception information: Access to the path ‘d:\inetpub\EIP_vti_pvt\service.cnf’ is denied.”

   Reply
   1. 

      Emiel
      On 14. July 2025 Permalink

      Hi Desmond,

      We’ve installed the June CU on two multi-server environments and haven’t encountered this psconfig error.

      That UnauthorizedAccessException for the service.cnf file points to a permissions issue. I’d suggest checking that the account you’re using to run the wizard has “Full Control” permissions on the d:\inetpub\EIP_vti_pvt\ directory. It’s also crucial that you’re running the psconfig command or UI from a shell that was launched with “Run as administrator”, as the update process requires elevated privileges.

      Hope you get it sorted out.

      Reply
2. 

   Robert
   On 18. July 2025 Permalink

   Does the WSS_ADMIN_WPG or WSS_WPG account have permissions? https://learn.microsoft.com/en-us/sharepoint/install/account-permissions-and-security-settings-in-sharepoint-server-2016#group-permissions

   Reply
   1. 

      Stefan Goßner
      On 18. July 2025 Permalink

      Hi Robert,

      the answer is Yes. As well in the registry and on file system. See here:
      https://learn.microsoft.com/en-us/sharepoint/install/account-permissions-and-security-settings-in-sharepoint-server-2016

      search for WSS_WPG and WSS_ADMIN_WPG to find the detailled permissions.

      Cheers,
      Stefan

      Reply
3. 

   Willie
   On 22. July 2025 Permalink

   @Stefan, I’ve inherited a SP farm that is currently on May 2024 CU. Can I go directly to installing July 2025 CU

   Reply
   1. 

      Stefan Goßner
      On 22. July 2025 Permalink

      Yes.

      Reply
4. 

   Shubham
   On 18. August 2025 Permalink

   Post this update, is anyone facing issues with modern pages in SP2019? The edit page button is missing and is not editable even after appending ?Mode=Edit in the URL. Also, the left navigation is missing and the options such as Getting started, Site Permissions, Change the look on settings button do not work. On creation of new site page, there is no option to edit/publish the page.

   Reply
   1. 

      Stefan Goßner
      On 18. August 2025 Permalink

      Hi Shubham, some questions:
      – did you install the language independent and the language dependent fix for July CU?
      – did you run the configuration wizard after installing both patches?
      – are you using side-by-side patching? If yes, did you update the side-by-side token after running the configuration wizard?
      – if yes, try if disabling side-by-side patching solves the issue.

      If you still have problems I would recommend to open a ticket with Microsoft support.

      Cheers,
      Stefan

      Reply
5. 

   Tiago
   On 3. October 2025 Permalink

   Hello Stefan,

   I’m facing the same issues that Shubham as, but I have a little more info to bring on the subject:

   In my scenario, I’ve installed both Core and LanguagePack CU updates, because we use Portuguese Language Pack on all our Farms.

   Farm 1, installed the binaries, and made a sucessfull clean PSconfig upgrade. – The problem with editing homepages of modern sites (Publish and Edit buttons missing). Make Homepage button setting disappears, etc is there.

   Farm 2, installed only the binaries, haven’t run PSconfig – The problem is there…

   Farm 3, Only has DEC 2023 CU – no problems editing modern site pages or setting a new noe with the “Make Homepage”, because its all working fine.

   One relevant or not diference between farms is that, farm 1 and 2 are windows server 2022 std, and farm 3 has windows server 2019 std

   My questions for you are:

   Farm 1 – is it possible to go back with the upgrade, without any backup?

   Farm 2 – Can I uninstall the CU binaires, going back to the previous CU version?

   I’m openning a support case first thing tomorrow, but I would much like your input and much solid expertice.

   Do you have any sugestions for me?

   Cheers,
   Tiago R. Santos

   Reply
   1. 

      Stefan Goßner
      On 3. October 2025 Permalink

      Hi Tiago,
      SharePoint fixes cannot be uninstalled. So you cannot go back.
      The only supported ways to go back would be
      – a desaster recovery restore from a farm backup (including binaries and SQL) or
      – by restoring a cold snapshot of all SharePoint Servers and SQL servers.
      Cold snapshot means that all these machines are shutdown when the snapshot was taken to ensure that all data is in sync.

      Did you open a support case with Microsoft to get this analyzed?

      Cheers,
      Stefan

      Reply
6. 

   Tiago
   On 3. October 2025 Permalink

   Hello Stefan,

   Ok, unfortunally, you just confirmed what I learned over the years about the product. No “miracle’s” there.

   If yo don’t have a good backup/restore strategy in place, and individual envirements (QUA, PRD). Even with HA scenarios, CU implementations can be a “drama”, if testing is not done properly.

   Yes I did open the support case. And they will get back to us, if not today, Monday, first thing.

   But it was actualy after more digging arround, that I noticed that this “issue” has being repeated by Microsoft, through some CU’s deployment, over the years. (traced it back to 2020, and similar issues with the 2016 version)

   One of the articles is actually yours:

   https://blog.stefan-gossner.com/2022/05/31/trending-issue-left-navigation-missing-after-applying-may-2022-cu-for-sharepoint-server-2019/

   https://learn.microsoft.com/en-us/answers/questions/134136/left-navigation-not-loading-on-sharepoint-server-2?orderby=newest&page=2#answers

   https://learn.microsoft.com/en-us/answers/questions/5495733/issues-after-applying-sharepoint-2019-updates-kb50?orderby=newest&page=2#answers

   In our scenario its related to the sp-pages-assembly.js and some other components that I haven’t understood yet… But I’m a Infrastructure guy, not dev.

   the only “fix” that I found until now, that actually changes something. Was to replace, the “sp-pages-assembly.js”, after a proper backup of course, by the version existing in the default folder, as described on the second article of the list.

   Never the less, its not a solution, because de command’s are not “masked” with labels, but as “CommandBar_Edit”, for example instead of “Edit”, but it does solve de functional part

   Lets see what Microsoft is going to say about it this time. I’ll post more updates.

   Thank you for your fast reply.

   PS: I follow your blog since the moss version. Introduced by a former MS Sharepoint PFE. It is my first post, but let me say, that your work over the years, has been priceless. Regarding Sharepoint products, and the tech community.

   Keep it up

   Reply
7. 

   Tiago
   On 22. October 2025 Permalink

   Hello Stefan,

   As promissed. And after a few troubleshooting sessions with MS support, we concluded that it is related with the language pack update.

   The recomendation to fix it, is to deploy October CU’s. And it does.

   Thank you for your feedback and support.

   Best regards

   Reply
   1. 

      Stefan Goßner
      On 22. October 2025 Permalink

      👍

      Reply