May 2025 CU for SharePoint Server 2016 is available for download

22 Comments

1. 

   Volodymyr Yupin
   On 19. May 2025 Permalink

   After installation on Testing Environment, I have built number 16.0.5500.1000 not a 16.0.5500.1001 as it was written in this post.

   Reply
   1. 

      Stefan Goßner
      On 21. May 2025 Permalink

      Hi Volodymyr,
      16.0.5500.1001 is correct. I assume you are looking at the wrong place.
      Please have a look at this article:
      https://blog.stefan-gossner.com/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/
      Cheers,
      Stefan

      Reply
2. 

   Venkata Nakka
   On 21. May 2025 Permalink

   Hi Stefan,
   Good Day!!!

   any issue with KB5002712 for SharePoint Server 2016 (language dependent)??

   Updating our environment issue details here – while installing the May 2025 security update (KB5002712) for SharePoint 2016 server the language pack is not installed on 2 regions out of 6. The languages were Spanish and Portuguese pack installation failed.

   Package details – wssloc2016-kb5002712-fullfile-x64-glb.

   Error message – The installation of this package is failed.

   Farm Information:

   Current Configuration database version: 16.0.5500.1000 (DEV/TEST)

   Previous Configuration database version: 16.0.5478.1000

   Reply
   1. 

      Stefan Goßner
      On 21. May 2025 Permalink

      Hi Venkata,
      did you try to apply the fix again?
      Sometimes a file is locked and running the install a second time allows the installation to succeed.
      Cheers,
      Stefan

      Reply
      1. 

         Venkata Nakka
         On 21. May 2025 Permalink

         Hi Stefan,
         yep, we tried couple of times but no luck and rebooted the machine as well as same results.

         Highlighted as ##(KB5002544) & time stamp 1/22/2025

         Here are the installation details in Installed Updates section.

         Language Pack for SharePoint and Project Server 2016 – French/Français (1)
         Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002712) 64-Bit Edition Language Pack for SharePoint and Project Server 2016 – German/Deutsch (1)
         Language Pack for …
         Microsoft
         5/20/2025

         Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002712) 64-Bit Edition Language Pack for SharePoint and Project Server 2016 – Italian/Italiano (1)
         Language Pack for …
         Microsoft
         5/20/2025

         Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002712) 64-Bit Edition Language Pack for SharePoint and Project Server 2016 – Portuguese/Português (Brasil) (1)
         Language Pack for …
         Microsoft
         5/20/2025

         ##Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002544) 64-Bit Edition Language Pack for SharePoint and Project Server 2016 – Spanish/Español (1)
         Language Pack for …
         Microsoft
         1/22/2025

         ##Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002544) 64-Bit Edition Microsoft SharePoint Server 2016 (2)
         Language Pack for …
         Microsoft
         1/22/2025

         Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002712) 64-Bit Edition
         Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002722) 64-Bit Edition
         Microsoft SharePoi… Microsoft SharePoi…
         Microsoft
         5/20/2025
         Microsoft
         5/20/2025

         Reply
3. 

   Venkata Nakka
   On 22. May 2025 Permalink

   Hi Stefan,
   We opened the MS case for the seam – here is the findings

   When tried to install the patch using Oputil.vbs we ran into the below error in our test lab,

   Produto: Microsoft SharePoint Foundation 2016 1046 Lang Pack — Erro 1937. Erro ao instalar o assembly ‘microsoft.sharepoint.portal.intl.resources,fileVersion=”16.0.5491.1000″,version=”16.0.0.0000000″,culture=”pt-BR”,publicKeyToken=”71E9BCE111E9429C”,processorArchitecture=”MSIL”‘. A assinatura ou o catálogo não é válido ou não pôde ser verificado. HRESULT: 0x80131045. interface de assembly: IAssemblyCacheItem, função: Commit, componente: {84EA9C5E-47A9-4B98-B203-32E48E0F592E}

   We have escalated the issue internally with our Escalation engineers, we will keep you posted with the findings ASAP.

   Reply
   1. 

      Stefan Goßner
      On 28. May 2025 Permalink

      Hi Venkata,
      can you please send me the SR number using the “Contact the blog author” option at the top right of this page?
      Cheers,
      Stefan

      Reply
      1. 

         Stefan Goßner
         On 28. May 2025 Permalink

         Ok, just found the case and connected with the case owner. 🙂

         Reply
4. 

   Anand
   On 23. May 2025 Permalink

   Hi, we missed out Apr 2025 CU in SP2016 to be installed.

   Shall we go directly to install May 2025 CU update in SP2016. or we first want to update Apr 2025 CU installed then with May 2025 CU

   Reply
   1. 

      Stefan Goßner
      On 25. May 2025 Permalink

      Hi Anand,
      SharePoint fixes are cumulative. So May CU includes all fixes from April CU and there is no need to install April CU first.
      You can directly install May 2025 CU.
      Cheers,
      Stefan

      Reply
5. 

   Rune Svenning
   On 26. May 2025 Permalink

   Hi Stefan,

   I am geting following error when runing config wizard.
   Upgrade [SearchAdminDatabase Name=TEST_Search] failed.
   Exception: Cannot find the object ‘proc_MSS_PutAzureDocumentIntoCrawlQueue’, because it does not exist or you do not have permission.Cannot find the object ‘proc_MSS_PutAzureDocumentIntoCrawlQueue’, because it does not exist or you do not have permission.

   I see that i does not exists in the Database.
   What can be the problem?

   Regards

   Rune

   Reply
   1. 

      Stefan Goßner
      On 26. May 2025 Permalink

      Hi Rune,
      I haven’t seen this. Please open a support ticket with Microsoft to get this investigated.
      Cheers,
      Stefan

      Reply
      1. 

         Rune Svenning
         On 27. May 2025 Permalink

         Hi Stephan,

         For Microsoft Support i got help.
         Runing following script did get me 1 step further.
         $ssa = Get-SPEnterpriseSearchServiceApplication
         Upgrade-SPEnterpriseSearchServiceApplication -Identity $ssa

         Then, I needed to run this as well.
         $contentDatabases = Get-SPContentDatabase
         foreach ($db in $contentDatabases)
         {
         Write-Host “Upgrading content database: $($db.Name)” -ForegroundColor Yellow
         Upgrade-SPContentDatabase -Identity $db.Id -Confirm:$false
         }

         Runing Configuration wizard did then complete successful.

         Reply
6. 

   Alex
   On 27. May 2025 Permalink

   Hi Stefan,

   I installed the May CU Update for SharePoint and also Nintex on our SP2016 and SPSE Test farm. On both farms we are facing Nintex issues again – everything else is working. I know the troubles with workflows with earlier CU updates and everytime your trending issue saved me. Right now some site workflows are failing to start on schedule but also starting them manually does not work.
   I opened a Nintex case and they said that my ows timer and also web configs are fine and contain the required authorized types. Also the new types which are listed here are there:https://blog.stefan-gossner.com/2024/12/11/resolved-trending-issue-problems-with-workflows-after-applying-september-2024-cu-for-sharepoint-2016-2019-se/

   The only thing that helps is to set “EnablePreParseSecurityCheckForWorkflow = $false”. Right now I am waiting with the installation on our prod farm. Also I will open a Microsoft case to help to analyze this issue. Just wanted to share my experiance with the May update – maybe someone else has these issues.

   In the ULS log you can find this:
   w3wp.exe Block the namespace: clr-namespace:Microsoft.SharePoint.WorkflowActions;Assembly=Microsoft.SharePoint.WorkflowActions, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, type: RootWorkflowActivityWithData 6be6a0a1-09b3-3068-22c6-32c507841d81
   0x2188 SharePoint Foundation Legacy Workflow Infrastructure c42q0 High Potentially malicious xoml

   Regards
   Alex

   Reply
   1. 

      Alex
      On 5. June 2025 Permalink

      If anyones interested, we were missing one authorized type in the web / ows timer config. Now the Nintex workflows are running fine again:

      Hope that helps anyone who has the same troubles.

      Regards,
      Alex

      Reply
      1. 

         Alex
         On 5. June 2025 Permalink

         authorizedType Assembly=”Microsoft.SharePoint.WorkflowActions, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” Namespace=”Microsoft.SharePoint.WorkflowActions” TypeName=”*” Authorized=”True”

         Reply
7. 

   Peter Geebelen
   On 3. June 2025 Permalink

   Hi Stefan

   I have a similar invalid signature issue as Venkata Nakka with the language dependent May 2025 CU, but for the Dutch language pack (NL):

   Product: Microsoft SharePoint Foundation 2016 1043 Lang Pack — Fout 1937. Er is een fout opgetreden tijdens de installatie van het onderdeel microsoft.sharepoint.portal.intl.resources,fileVersion=”16.0.5491.1000″,version=”16.0.0.0000000″,culture=”nl”,publicKeyToken=”71E9BCE111E9429C”,processorArchitecture=”MSIL”. De handtekening of catalogus kan niet worden gecontroleerd of is ongeldig. HRESULT: 0x80131045. onderdeelinterface: IAssemblyCacheItem, functie: Commit, naam van onderdeel: {A3B1B428-EF23-4E91-A1F7-136206C38EA5}

   Do you think the CU is going to be corrected and re-released for all languages, or do I have to submit my own support ticket with Microsoft?

   Regards,
   Peter

   Reply
   1. 

      Stefan Goßner
      On 3. June 2025 Permalink

      Hi Peter,
      Dutch and Portuguese (Brazilian) are affected.
      A fix is currently planned to be included in July 2025 CU.
      Cheers,
      Stefan

      Reply
      1. 

         Peter Geebelen
         On 4. June 2025 Permalink

         Thanks for the info, Stefan.
         In the meanwhile, what would be your suggestion ? Uninstall the May language independent package that was already applied, and go for the April CU’s ?
         Regards,
         Peter

         Reply
         1. 

            Stefan Goßner
            On 4. June 2025 Permalink

            Hi Peter,
            there is not much you can do as SharePoint fixes cannot be uninstalled.
            Cheers,
            Stefan

            Reply
            1. 

               Peter Geebelen
               On 17. June 2025 Permalink

               Hi Stefan,

               Yes, of course, but were working on a small REF farm and we rolled-back by restoring cold VM snapshots… The farm is ready for update again, but my question is now, which CU do you advise, April 2025 or June 2025? We are getting delay on this project and pressure from security, but are still a little bit at loss with the poor quality and the issues of the recent CU’s released by Microsoft…

               Kr,
               Peter

            2. 

               Stefan Goßner
               On 18. June 2025 Permalink

               Hi Peter,
               I cannot give you a clear yes/no answer here. Just some guidance:
               – A version mix between language dependent and independent fixes is not recommended and can lead to errors.
               – If Dutch or Portuguese (Brazil) language pack is installed the language dependent fix cannot be installed.
               – On the other hand not installing the language independent fixes means that important security fixes are not installed on your system.
               I would recommend to evaluate the risk of missing security fixes against the risk of problems with mixed patch levels between language independent and language dependent fixes.
               Cheers,
               Stefan