July 2025 CU for SharePoint Server Subscription Edition is available for download

10 Comments

1. 

   Chandu
   On 9. July 2025 Permalink

   Hi Stefan,

   Just following up on the ongoing issues we discussed earlier.

   I wanted to highlight that with the release of the July cumulative update KB5002751, it appears Microsoft has addressed both the User Profile Language Synchronization Job failure and the Query Logging Job timeout issue. We are in the process of applying the update to validate the resolution on our end.

   Would appreciate any confirmation you might have from the product group regarding this fix being officially included in KB5002751.

   Thanks again for your support.

   Regards,
   Chandu

   Reply
   1. 

      Stefan Goßner
      On 9. July 2025 Permalink

      Hi Chandu,
      please verify. Because from the info I have the User Profile Language Synchronization Job failure is planned to be fixed in August 2025 CU and the Query Logging Job job was already fixed June 2025 CU.
      Cheers,
      Stefan

      Reply
      1. 

         Toufik Abdous
         On 10. July 2025 Permalink

         Hi Stefan, Chandu,
         If I remember the User Profile Language Synchronization Job failure is related for CU March 2025.

         Reply
2. 

   Edmond BRASSEUR
   On 23. July 2025 Permalink

   Subject: Ongoing Issue with new cloud hybrid search on SharePoint SE

   Hello Stefan,

   Back in June, I contacted you regarding an issue with the new cloud hybrid search feature on a SharePoint SE server.

   I opened a support ticket via admin.cloud.microsoft, but the only response I received was a referral to the following documentation :
   https://learn.microsoft.com/en-us/sharepoint/hybrid/configure-cloud-hybrid-searchroadmap.

   They were unwilling to provide any further assistance.

   Since the July 2025 CU, the feature is now available in the Standard release ring (“Enables flight for the new Hybrid Search feature in the Standard release ring.”).

   However, I’ve never managed to get it working, even after running the latest script included in Cloud_Hybrid_Search_Scripts_July2025.zip :
   https://www.microsoft.com/en-sg/download/details.aspx?id=51490&msockid=010d185ab02064b8219a0dfeb199652f.

   I keep encountering the same error during crawl operations :

   07/23/2025 11:09:22.69 mssearch.exe (0x044C) 0x0FC4 SharePoint Server Search Crawler:Azure Plugin 4ktik High CAzurePlugin::SubmitTaskToSPOONSInternal caught com error 0x80004003 [azurepiobj.cxx:985] src\search\native\gather\plugins\azurepi\azurepiobj.cxx
   07/23/2025 11:09:22.69 mssearch.exe (0x044C) 0x0FC4 SharePoint Server Search Crawler:Common 15y3 High >>>> Exception hr=0x80004003 eip=00007FF9901AAE3C module=src\search\native\gather\plugins\azurepi\azurepiobj.cxx line=986
   07/23/2025 11:09:22.69 mssearch.exe (0x044C) 0x0FC4 SharePoint Server Search Crawler:Azure Plugin axchc High CAzurePlugin::SubmitTask caught NLBaseException ComError hr=80004003 [azurepiobj.cxx:731] src\search\native\gather\plugins\azurepi\azurepiobj.cxx
   07/23/2025 11:09:23.21 mssearch.exe (0x044C) 0x18FC SharePoint Server Search Crawler:Gatherer Plugin e5e0 High advising status change NSC_FLUSH (74c08330-2238-4e27-98ea-ab789476b2cc-crawl-0 Portal_Content crawl -1) [gatherobj.cxx:5581] src\search\native\gather\server\gatherobj.cxx

   Interestingly, hybrid search is still working correctly on SharePoint 2019, even though support was supposed to end on June 30, 2025.

   Do you have any insight into this SubmitTaskToSPOONSInternal error ?
   Have you heard of any clients successfully enabling the new hybrid search on SharePoint SE ?

   I’ve not been able to get it working since the initial release back in March 2025.

   Also, many thanks for sharing the documentation regarding CVE-2025-53770 and CVE-2025-53771.
   I have applied the latest CUs (KB5002754, KB5002753, and KB5002768) to both my SharePoint 2019 and SE farms.

   Thank you in advance for your response.

   Best regards,

   Reply
   1. 

      Stefan Goßner
      On 23. July 2025 Permalink

      Hi Edmond,
      unfortunately not. My suggestion would be to contact Microsoft Support to get assistance.
      Cheers,
      Stefan

      Reply
      1. 

         Edmond BRASSEUR
         On 28. July 2025 Permalink

         Hello Stefan,

         To simplify the installation, I set up another SharePoint SPSE farm using the setup.exe directly. This farm was configured with a single service account, sp_farm, and in this case, the new cloud hybrid search works correctly.

         However, in my production farm, the installation was done using AutoSPInstaller, following Microsoft’s recommended best practices. As a result, multiple service accounts are used. In this setup, the SharePoint Server Search 16 service (OSearch16) runs under the sp_services account.

         In this case, crawling fails with the following error: CAzurePlugin::SubmitTaskToSPOONSInternal caught com error 0x80004003.

         After investigation, I found that for the new cloud hybrid search to function properly with the sp_services account, it must be added to the machine’s local Administrators group. This account is already a member of WSS_ADMIN_WPG and WSS_WPG, but that is not sufficient.

         Although this goes against Microsoft’s recommendations, I will proceed with adding the account to the local Administrators group because I need to index my farm.

         Best regards,

         Reply
3. 

   Paul Fox
   On 23. July 2025 Permalink

   Do the Cumulative Updates also include all of the Feature Updates ? I am looking to install a new SharePoint SE Farm

   Reply
   1. 

      Stefan Goßner
      On 23. July 2025 Permalink

      Hi Paul,
      yes. It is cumulative so it includes everything released before including the feature updates.
      Cheers,
      Stefan

      Reply
4. 

   JustaSimpleSharepointGuy
   On 3. October 2025 Permalink

   Hi Stefan

   We have a large SharePoint Farm with July 2025 CU installed and are experiencing still problems with the Query Logging Job. The Job runs but won’t stop anymore – last time over 93 hours. Only a restart of the SharePoint timer service will quit the job. I can start the job but won’t find any clues in the logs what’s going wrong.

   Before I open a ticket with Microsoft premium support – maybe you can provide me a possible clue ?

   Best Regards

   JustaSimpleSharepointGuy

   Reply
   1. 

      Stefan Goßner
      On 3. October 2025 Permalink

      Sorry – I think you need to open a ticket.
      Cheers,
      Stefan

      Reply