SharePoint security fixes released with April 2025 PU and offered through Microsoft Update

12 Comments

1. 

   Suno API
   On 9. April 2025 Permalink

   Thanks for detailing the April PU — always helpful to have the specific KBs broken down. We’ve run into issues before when only applying the security patches, so the CU recommendation is a good reminder.

   Reply
2. 

   Welf Alberts
   On 9. April 2025 Permalink

   Hi all.

   Sharepoint 2016 on Server 2016 does not install KB 5002692 here. The logfile does not tell me anything useful apart from error 1603. All previous sharepoint updates installed alright, first time that I am stuck with no clue.
   Hints for previous updates that had 1603 included „please stop certain services (IIS, Appfabric Cache,…), then retry“ didn’t work for me.

   Anyone else seeing this?

   Reply
   1. 

      Guillermo Beltran
      On 10. April 2025 Permalink

      Same here. Performed a graceful stop on the distributed cache, stopped IIS, cleared the configuration cache, turned off the AMSI on the web applications… no clue.

      Reply
   2. 

      Dude
      On 10. April 2025 Permalink

      There is a wrongly signed file in the package. We will all have to wait for Microsoft to correct and re-release the KB.

      If you check your user local %temp% and open sts-x-none_MSPLOG.LOG you will see:

      MSI (s) (AC:B8) [09:11:37:838]: Assembly Error:Strong name signature verification failed for assembly ‘%1’. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key.

      Reply
3. 

   Greg Hutson
   On 10. April 2025 Permalink

   I copied Welf Alberts comment, as we are seeing the exact same issue….
   Sharepoint 2016 on Server 2016 does not install KB 5002692 here. The logfile does not tell me anything useful apart from error 1603. All previous sharepoint updates installed alright, first time that I am stuck with no clue.
   Hints for previous updates that had 1603 included „please stop certain services (IIS, Appfabric Cache,…), then retry“ didn’t work for me.

   We’re thinking bad patch. It’s effecting multiple servers in multiple domains. It would have to be the patch, right?

   Reply
   1. 

      Primos
      On 13. April 2025 Permalink

      I have been struggling with same problem but today I have noticed this:
      https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-sharepoint-enterprise-server-2016-april-8-2025-kb5002692-fc39103a-9fb7-4003-bdd3-9e61ed93359d

      Reply
4. 

   Pawel Odya
   On 11. April 2025 Permalink

   Great website! Do you know how to solve issue when after installing March/April CU there is no longer option to search Crawling menu?

   I have an error: “the remote certificate is invalid according to the validation procedure.”

   Before march 2025 KB everything was working fine :/ I know about new TLS implementation from MS with March 25 CU but I don’t know yet how to restore full access to search Crawling menu.

   How should I reconfigure Sharepoint SE Central Administration and/or SQL to restore fully functionality? Implementing HTTPS on CA?

   Reply
   1. 

      Stefan Goßner
      On 13. April 2025 Permalink

      Hi Pawel,
      that might require a detailed analysis of your servers.
      Best would be to open a support case with Microsoft to get assistance.
      Cheers,
      Stefan

      Reply
5. 

   Brian
   On 15. April 2025 Permalink

   Hi i have a strange problem SharePoint links with ; have stopped working, there link is is changed to %3b
   It started around the last March 2025 CU.

   Tried this one, still the same 🙁

   SharePoint 2019.

   Reply
6. 

   Welf Alberts
   On 16. April 2025 Permalink

   FYI: KB 5002692 has been revised and “should” work now. Anyone tested already? Will let you know tonight or tomorrow.

   Reply
   1. 

      Yunisss
      On 16. April 2025 Permalink

      I tested it and it works. You can also download it.

      Reply
7. 

   Welf Alberts
   On 16. April 2025 Permalink

   The new version installed alright on two servers here.

   Reply