The product group released the February 2025 Cumulative Update for SharePoint Server 2016 product family.
This CU also includes Feature Pack 1 which was released with December 2016 CU and Feature Pack 2 which was released with September 2017 CU.
The KB articles for February 2025 CU should be available at the following locations in a couple of hours:
- KB 5002685 – February 2025 Update for SharePoint Server 2016 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002671 from January 2025 CU.
If this is not yet installed on your Farm, you need to install it together with the language independent fix.
The downloads for February 2025 CU are available through the following links:
- Download February 2025 Update for SharePoint Server 2016 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002671 from January 2025 CU.
If this is not yet installed on your Farm, you need to install it together with the language independent fix.
Important: It is required to install both fixes (language dependent and independent) to fully patch a SharePoint server. This applies also to servers which do not have language packs installed. The reason is that each SharePoint installation includes a language dependent component together with a language independent component. If additional language packs are added later (only) the language dependent fix has to be applied again.
It is irrelevant which language you pick on the drop down in download center. Even the language dependent fixes are all in the same package for all languages.
After installing the fixes you need to run the SharePoint 2016 Products Configuration Wizard on each machine in the farm. If you prefer to run the command line version psconfig.exe ensure to have a look here for the correct options.
SharePoint 2016 February 2025 CU Build Numbers:
Language independent fix: 16.0.5487.1000
To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
Related Links:
- Technet: Updated Product Servicing Policy for SharePoint Server 2016
- Blog: SharePoint Patching Best Practices
- Blog: Common Question: What is the difference between a PU, a CU and a COD?
- Blog: SharePoint Patching demystified
- Blog: Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SharePoint Server 2016 Patch Build Numbers Powershell Module
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified
- Blog: SharePoint does not have a build version. Full Stop.
Permalink
Hi Stefan,
We noticed an issue while installing February CU binaries on different SP2016 farms.
While running binaries we are getting event id 1000/1001 and finally id 11935 with error message:
Product: Microsoft SharePoint Foundation 2016 Core — Error 1935. An error occurred during the installation of assembly component {5EB5ED6A-3FC6-4EE4-A12C-62716067DFC7}. HRESULT: 0x800700B7. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: Microsoft.SharePoint,fileVersion=”16.0.5487.1000″,version=”16.0.0.0000000″,culture=”neutral”,publicKeyToken=”71E9BCE111E9429C”,processorArchitecture=”MSIL”
Installation progress status bar is frozen at the end and final status is: The installation of package failed.
We can not see any more comments with same issue and we’d like to exclude possibility of general issue with KB.
Kind Regards,
Kamil
Permalink
We have 6 SharePoint servers in 2 Test farms. When I installed that update it failed on two of those servers with the same message ( The installation of package failed.). However trying a second time let me install those updates on all servers.
Either way, I am slightly hesitant to install those on our productive environment.
Permalink
We also encounter the same issue as Kamil. Installation would proceed, gets stuck at the end for some time and then the pop up for the package installation failed. Failed on one of our WFE and a couple of Application Servers.
Permalink
We get the same issue. Works on one of our servers but not on the other one. Same error message. The status bar freeze and after a while we get the message that the installation was failed. Tried installed both in CU downloaded under Update & Security and Installation from downloaded file (Run as administrator)
Hope for a quick solution
Thanks
Regards Kerstin
Permalink
Hi,
We get the same issue on one of our servers. The other one installed without issues. The Status Bars freeze and after a while the message appears that the installation failed.
Looking forward to a quick solution on this.
Permalink
Hi
We have the same problem as Kamil.
We have a SharePoint farm with two servers. On one server it was possible to install CU on the other server we got, The installation of the package failed.
In the event viewer, we have below error message
Product: Microsoft SharePoint Foundation 2016 Core — Error 1935. An error occurred during the installation of the assembly component {5EB5ED6A-3FC6-4EE4-A12C-62716067DFC7}. HRESULT: 0x800700B7. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: Microsoft.SharePoint,fileVersion=‘16.0.5487.1000’,version=‘16.0.0.0000000’,culture=‘neutral’,publicKeyToken=‘71E9BCE111E9429C’,processorArchitecture=‘MSIL’.
Do you have any idea what causes this problem and how to solve it?
Best Regards
Eva
Permalink
Hi Stefan,
Same issue i am also facing in sharepoint 2016 farm. we were able to install the patch on few of the servers but few are pending due to installation getting failed.
Could you please suggest if there is any issue with this Feb 2025 month security update?
Regards,
Ganesh P.
Permalink
Hi all,
We are in the same situation. Installation worked on some servers but one server got message Failed. Have not run the Configuration Wizard in the environment with the server that failed. Have installed successfully in two test environments and run the Configuration Wizard with no issues on them.
Permalink
We’re also facing the installation issue. It’s working on some servers but not on some other servers.
Permalink
Hi Stefan,
I have also encountered a similar issue like others. I was able to install this KB to almost all of my sharepoint farm servers except for one. The error I receive is the following:
“Windows Installer installed an update. Product Name: Microsoft SharePoint Foundation 2016 Core. Product Version: 16.0.4351.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Update Name: Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002685) 64-Bit Edition. Installation success or error status: 1603.”
The installation fails even after several reboots of the affected server.
Best regards,
James
Permalink
Hi Stefan,
Same issue here, i am also facing in sharepoint 2016 farm, installation getting failed.
Any feedback about this problem?
Thank you in advanced.
Permalink
We had the same issue as well: “The installation of this package failed” It was failing mostly on Application servers. Other servers were fine. Seems to be related to the patch installer not able to overwrite some assembly files probably because they were used by some processes. We worked with a Microsoft support, the fix for us was to:
1. Restart the computer
2. Disable all SharePoint related Services, IIS Admin Service and World Wide Web Publishing Service
3. Try installing the package again.
Cheers!
Seybou
Permalink
Thanks for the suggestion. This did help. I also stopped distributed cache too. I am not sure if it was needed, but I tried it again and the update installed.
Permalink
We are facing the same issue with updates failing during install. A second try did the trick and were able to install the updates and run the config wizard.
Is this a general issue with this update?
BTW: Trying for the third time to post this info here….
Permalink
Hi Stefan,
Same issue i am also facing in sharepoint 2016 farm due to installation getting failed.
Any feedback?
Thank you
Permalink
I too got installation failed on my front end servers (but not application servers). I found I had to stop the distributed cache service before running the patch installer after which installation was successful.
Permalink
Hi Stefan,
Same issue here.
Started with error 1935:
Product: Microsoft SharePoint Foundation 2016 Core — Error 1935. An error occurred during the installation of assembly component {5EB5ED6A-3FC6-4EE4-A12C-62716067DFC7}. HRESULT: 0x800700B7. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: Microsoft.SharePoint,fileVersion=”16.0.5487.1000″,version=”16.0.0.0000000″,culture=”neutral”,publicKeyToken=”71E9BCE111E9429C”,processorArchitecture=”MSIL”
After several attempts error changed to 1603
Windows Installer reconfigured the product. Product Name: Microsoft SharePoint Foundation 2016 Core. Product Version: 16.0.4351.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 1603.
Regards,
Carlos Gonçalves
Permalink
We can also confirm the problems described: On some servers the installation of the patch KB5002685 runs smoothly, but on other SharePoint servers the update takes an unusually long time and then simply cancels with the message ‘Error installing the package’.
This happens when executing directly the file and also when executing in the ISE (with stopping the search, timer, and CA Service).
The eventlog shows the following event:
Product: Microsoft SharePoint Foundation 2016 Core – Update ‘Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002685) 64-Bit Edition’ could not be installed. Error code 1603.
We also recognise al lot of Warnings in eventviewer from RestartManager like:
Application ‘C:\Windows\System32\inetsrv\w3wp.exe’ (pid 2420) cannot be restarted – Application SID does not match Conductor SID..
The SecurityEvent Log shows a lot of this entries: ID4689 “A process has exited”
Permalink
We have the same problems with installing the Febr 2025 Patch on SharePoint 2016 Servers. The Installation fails on some server with the error:
Fehler beim Installieren dieses Pakets.
And there are a lot of warnings from RestarManager ID 10010 …cannot be restarted -Application SID does not match Conductor SID..
Permalink
We followed the instructions from SEYBOU to get rid of the installation problems:
Restart the computer
Stop/Disable all SharePoint related Services, IIS Admin Service and World Wide Web Publishing Service
(Maybe you need to stop other running services, which Pop-Upped during the installation)
Try installing the package again.
Then the installation finished successfully!
re-enable the services again – and reboot
Permalink
Hello everyone.
I don’t know how about you, but I probably won’t be the only one who is impatiently waiting for Stefan’s reaction and his opinion on whether this issue is critical and how to eliminate it. On this Thursday I will be installing this CU on our production farm.
Several of you confirm that it is necessary to stop SharePoint related services.
I haven’t done this for several years, so far I have patched SharePoint 2016 in a “running” state without problems. I did this earlier, that is with SharePoint stopped, in the style of the script from SPJeff
https://github.com/spjeff/sppatchify/blob/master/Install%20CU%20Faster.ps1
This script stops only 5 services: OSearch16, SPSearchHostController, SPTimerV4, IISADMIN, W3SVC.
Has anyone experienced that this set is insufficient and needs to be expanded, for example with AppFabricCachingService or SPAdminV4?
Maybe there is nothing to worry about and the installation of this CU will go smoothly.
I have a feeling that most of the problems are encountered by those admins who have their farms not quite “standard”, but somehow customized with various third-party products, or with their own coded applications.
Looking forward for continuation of the story.
Permalink
Hello everyone,
We have now installed this update on our productive Sharepoint environment and we have noticed exactly the same behavior as during the installation on our test environment. The installation stopped several times on only one server in our farm with an “error installing the package”. Even after a restart and after we had stopped several Sharepoint services, the installation did not seem to work.
After I followed the example of Andreas and Seybou and turned off the following services (IIS Admin Service and World Wide Web Publishing Service), besides all Sharepoint related services. In any case, I noticed one thing.
After extracting the update was completed, a popup appeared that AppFabricCachingService was still accessing something and it had to be stopped for the update to continue. Unfortunately, confirming the termination of the service via this call did not help. The error appeared again.
Only on the next attempt (after a reboot and after all Sharepoint services including IIS Admin Service and World Wide Web Publishing Service were stopped) did I also decide to stop the AppFabricCachingService.
Suddenly the install went through successfully!
It was also interesting to note that both servers affected by this issue use the AppFabricCachingService. This could at least be an indication that the service is causing some form of interruption during installation.
For now, everything appears to be running smoothly.
I hope that our experience with this update can help you guys 🙂
Permalink
I will add my another two cents to discussion.
When I read the article “Solving the extended install time for SPSE CUs” (https://blog.stefan-gossner.com/2024/03/08/solving-the-extended-install-time-for-spse-cus/) there is a statement that “… for SharePoint Server 2019 CUs the installer stops all relevant SharePoint and IIS Windows Services before invoking the fix installation while the services fail to be stopped for SPSE CUs. The root cause here is that the method used to stop the services no longer works with SPSU. This leads to performance problems when the installer tries to update assemblies in the global assembly cache due files being in use.”
Is this the case also for SharePoint 2016 CUs (security fixes installers)?
Adding another aspect of issue: what about the situation when I have no control over SharePoint CU installation? I mean when my Windows Update layer on Windows Server is offering me the SharePoint CU, along with Windows Server CU, despite Microsoft Update (MU) is turned off.
Under MU I mean configurable choice named “Give me updates for other Microsoft products when I update Windows” in Advanced options of Windows Update settings.
Permalink
Hi All,
Yes it worked for me. Please follow below steps,
1) Stop all SharePoint services in services.msc ( IIS Admin, World wide web publishing, SP Timer, AppFabric caching, SharePoint Search host cont. , SharePoint server search 16).
2) Copy the downloaded KB on server and open (Run as Administrator) and start installation.
3) Once installation completed, start all the services again which you have stopped in step 1.
3) Please run PSCONFIG command or SharePoint 2016 Configuration Wizard on all servers.
4) Please check whether SharePoint 2016 farm upgraded to version 16.0.5487.1000
Thanks !
Cheers,
Ganesh P.
Permalink
I notice the CU download is not available any more. Has it been pulled by MS?
Permalink
Hi Steve,
I just tested and the download works for me.
Cheers,
Stefan
Permalink
The link gives me a 404 error…
http://www.microsoft.com/download/details.aspx?familyid=46fe26d2-4dab-4891-97dc-80aa5585c8ee
Permalink
I also get a ‘404’ message here. Do you maybe have any update to share regarding this apparently broken update file?
Permalink
Hi folks.
Yes, you are right, from related KB page (https://support.microsoft.com/en-us/kb/5002685) the link under “Method 3: Microsoft Download Center” is not working (error 404). But Stefan announced, see up here in this article, direct link to download CU installer here (https://www.microsoft.com/en-us/download/details.aspx?id=106398) and it is working, CU is available.
What I miss is Stefan’s reaction to the need of all of these services start/stop manoeuvres… especially with Distributed Cache service (AppFabricCachingService) I don’t like to messing around.
Permalink
Hi eLKey,
sorry for lack of response – I’m currently away from work so I’m currently not able to verify or comment on details for the services start/stop manoeuvres.
Really great to see that the community here identified a workaround and the passion of people to help each other.
Cheers,
Stefan
Permalink
Hi Stefan,
Is there an official fix or workaround for this issue?
Permalink
Not related to SharePoint specifically, however I was dealing with a different product installer which was yielding very similar error messages:
Error 1935. An error occurred during the installation of assembly ‘{PRODUCT_ASSEMBLY}”‘. Please refer to Help and Support for more information. HRESULT: 0x800700B7. assembly interface: IAssemblyCacheItem, function: Commit, component: {F27E369C-C0DB-4BFF-9076-10474CD0C6FC}
After much painful digression testing, it turned out that the main culprit was the latest windows cumulative updates, specifically the last two (Server 2019 in our case):
Doesn’t work: ❌ 2025-02 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5052000)
Doesn’t work: ❌ 2025-01 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5050008)
I then rolled back the windows update until it worked, which was on the Dec 2024 update:
Works: ✅ 2024-12 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5048661)
Works: ✅ 2024-11 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5046615)
Works: ✅ 2024-10 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5044277)
…
Applicable windows updates found here: https://www.catalog.update.microsoft.com/Search.aspx?q=%22Cumulative%20Update%20for%20Windows%20Server%202019%22
Generally we found that running the installer twice on systems with the latest windows patches would work, so it would fail the first time and work the second time. Rebooting the server in-between installer executions would cause the issue to reoccur the first time every time. Not sure if that would be specific to our product.
We have yet to find a way to perform any sort of pre-clean step that will allow the installer to execute w/o issue on the FIRST run. We could of course just rollback all our servers to the unaffected cumulative updates, but we’d be missing out on whatever security fixes were released on those patches.
Since the March 2025 update is a week away, I’m planning to retest my findings then. So hopefully Microsoft will have this fixed. However if it’s still broken, then we’ll need to come together as a community and get Microsoft to look into this. From my research, this is affecting other software installers such as y’all and Exchange Server:
https://support.microsoft.com/en-us/topic/file-version-error-when-you-try-to-install-exchange-server-november-2024-su-a650da30-f8fb-469d-a449-47396cab0a15
Permalink
Per my preliminary testing, March 2025 updates for Server 2019 (KB5053596) seem to have fixed the issue. More testing needed to confirm for sure 🤞. Again can’t speak to the SharePoint specific install, just referring to the core issue of “An error occurred during the installation of assembly…”.