February 2026 CU for SharePoint Server Subscription Edition is available for download

16 Comments

1. 

   Stefan Winkler
   On 18. February 2026 Permalink

   Hi Stefan,
   first of all: Thank you for your great work!

   After installing the February 2026 CU for SharePoint Server Subscription Edition we experienced the following issue:
   The configuration wizard exited with

   Failed to initiate the upgrade sequence.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: One or more types failed to load. Please refer to the upgrade log for more details.
Microsoft.SharePoint.Upgrade.SPUpgradeException: One or more types failed to load. Please refer to the upgrade log for more details.
at Microsoft.SharePoint.Upgrade.SPActionSequence.LoadUpgradeActions()
at Microsoft.SharePoint.Upgrade.SPActionSequence.get_Actions()
at Microsoft.SharePoint.Upgrade.SPActionSequence.get_RunnableActions()
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunPreUpgraders(Object o, List`1 lstClass)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Administration.SPDatabase.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPManager.BootStrap(Guid sessionId, SPUpgradeOperationFlags flags)
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()"


   The upgrade log tells us:
   ERROR Exception: Could not load file or assembly ‘EcsClient, Version=2025.8.18.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.

   SPUpgradeSession bbdmv INFO Updating state for PersistedUpgradableObject: SPConfigurationDatabase Name=SharePoint_Config. This object's current status is Online. Setting it to Upgrading.
SPUpgradeSession an59k DEBUG Entering IUpgrader.PreUpgrade() for upgrader [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence] on object [SPConfigurationDatabase Name=SharePoint_Config]

   SPConfigurationDatabaseSequence ajy5v DEBUG VERSION LOG (GET): Get version 16.0.19127.20338 for Database [SharePoint_Config] from database with version Id , Status = Upgrading.
   SPConfigurationDatabaseSequence ajy5h DEBUG VERSION LOG (GET): Calling get SchemaVersion on Database SharePoint_Config, Status = Upgrading.
   SPConfigurationDatabaseSequence brrnz DEBUG VERSION LOG (GET): Get version 16.0.10.0 for Database [SharePoint_Config] from cache with version Id 60b1f2be-5130-45ab-af1d-edd34e626b5d, Status = Upgrading.
   SPConfigurationDatabaseSequence ajy5i DEBUG Returning SchemaVersion [16.0.10.0] for Database SharePoint_Config, Status = Upgrading.
   SPConfigurationDatabaseSequence ajywv DEBUG Microsoft.SharePoint, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c

   SPConfigurationDatabaseSequence ajywy ERROR Failed to call GetTypes()
   SPConfigurationDatabaseSequence ajywy ERROR Exception: Could not load file or assembly 'EcsClient, Version=2025.8.18.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
   SPConfigurationDatabaseSequence ajywy ERROR Failed to call GetTypes()
   SPConfigurationDatabaseSequence ajywy ERROR Exception: Could not load file or assembly 'EcsClient, Version=2025.8.18.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

   SPUpgradeSession an59m DEBUG Exiting IUpgrader.PreUpgrade() for upgrader [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence] on object [SPConfigurationDatabase Name=SharePoint_Config]
   SPUpgradeSession an59t ERROR Upgrade [SPConfigurationDatabase Name=SharePoint_Config] failed.
   SPUpgradeSession an59t ERROR Exception: One or more types failed to load. Please refer to the upgrade log for more details.
   SPUpgradeSession an59t ERROR at Microsoft.SharePoint.Upgrade.SPActionSequence.LoadUpgradeActions() at Microsoft.SharePoint.Upgrade.SPActionSequence.get_Actions() at Microsoft.SharePoint.Upgrade.SPActionSequence.get_RunnableActions() at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunPreUpgraders(Object o, List`1 lstClass) at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   SPUpgradeSession an59u DEBUG Elapsed time upgrading [SPConfigurationDatabase Name=SharePoint_Config]: 00:00:01.
   SPUpgradeSession an591 DEBUG Exiting upgrade for [SPConfigurationDatabase Name=SharePoint_Config]. Elapsed Time=[00:00:01]
   SPManager ajyi3 INFO Resetting the status of PersistedUpgradableObject: SPConfigurationDatabase Name=SharePoint_Config to Online.
   SPManager ajxox ERROR SPManager.Initialize failed: {0}.
   SPManager ajxox ERROR Exception: One or more types failed to load. Please refer to the upgrade log for more details.
   SPManager ajxox ERROR at Microsoft.SharePoint.Upgrade.SPActionSequence.LoadUpgradeActions() at Microsoft.SharePoint.Upgrade.SPActionSequence.get_Actions() at Microsoft.SharePoint.Upgrade.SPActionSequence.get_RunnableActions() at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunPreUpgraders(Object o, List`1 lstClass) at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Administration.SPDatabase.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.BootStrap(Guid sessionId, SPUpgradeOperationFlags flags)

   SPUpgradeSession an576 DEBUG Setting upgrade session object to offline
SPUpgradeSession an6ac DEBUG UPGRADE PERCENTAGE: 100.00000000% done, Total Elapsed Time 00:00:01.4683946.
SPUpgradeSession an577 DEBUG Releasing upgrade lock
SPUpgradeSession an578 DEBUG Stop the session maintenance thread.


   What I’ve learned so far:
   The assembly EcsClient is a component related to the Office Online Server (OOS) or Excel Services Client integrations in SharePoint. The upgrade process is trying to call GetTypes() on the SharePoint assemblies to determine which upgrade actions to run, but it’s failing because this specific DLL is missing from the Global Assembly Cache (GAC) or the SharePoint binary folders.
   We have Office Online Server (OOS) integrated with this farm and after restarting all necessary services which were stopped by the failing Config Manager, the integration still works.
   And… there’s no folder EcsClient in the GAC…

   Is this a known effect and how can we solve it to bring the farm into a stable condition again?
   Thank you for any advice,
   Stefan

   Reply
   1. 

      Stefan Goßner
      On 27. February 2026 Permalink

      Hi Stefan,
      this is not a known issue. My suggestion would be to open a support case with Microsoft to ensure this is investigated.
      Cheers,
      Stefan

      Reply
2. 

   Brett Cartwright
   On 21. February 2026 Permalink

   I finished running this patch through our test environment today. So far so good.
   Only idiosyncrasy was one of my Cache servers didn’t come back up. Service was disabled and wouldn’t come back up easily.
   I was running the Patch script from this post, https://blog.stefan-gossner.com/2024/03/08/solving-the-extended-install-time-for-spse-cus/ and I know it shuts down Dist Cache gracefully. However I think some of the new checks that kill the PS process fired because the window dropped while the patch was still installing. I was able to finally get the service back up and restored.

   I did not run into the same error that Stefan Winkler reported above.

   Reply
3. 

   Alex
   On 23. February 2026 Permalink

   Hi everybody,
   wanted to let interested people know that the Februar CU update installed without any issues on our Test and Prod environment (multiple server SP farm). I know that every SP farm can be different but maybe this helps someone in his or her decision making to wheather install this update or not.
   Also the crashes of the worker processes are gone now, which we saw in our monitoring before the update while the search was crawling.
   Thanks Stefan for this blog, otherwise we wouldn’t have all this information!

   BR Alex

   Reply
4. 

   Thomas
   On 26. February 2026 Permalink

   Hi all,
   Since we rolled out the February 2026 update in our multi server cross-services-farm environment (Content farm consuming search service in Service farm) we have issues with search queries in the Content farm.
   The Search result pane responds with an “Unknown error occured” and a Correlation ID
   The search service is running fine. The Topology shows all service components running fine (all green).

   We have performed all obvious troubleshooting steps (i.e. restart of servers and services)

   Any other out there having the same problem?

   — Shout out to Stefan for this excellent blog and goldmine of SP knowledge

   Reply
5. 

   Thomas
   On 26. February 2026 Permalink

   Hi all,
   Since we rolled out the February 2026 update in our multi server cross-services-farm environment (Content farm consuming search service in Service farm) we have issues with search queries in the Content farm.
   The Search result pane responds with an “Unknown error occured” and a Correlation ID
   The search service is running fine. The Topology shows all service components running fine (all green).

   We have performed all obvious troubleshooting steps (i.e. restart of servers and services)

   Any other out there having the same problem?

   — Shout out to Stefan for this excellent blog and goldmine of SP knowledge

   Reply
6. 

   Robin
   On 27. February 2026 Permalink

   Hi Stefan,
   Is the fix in the February 2026 CU included, that I can update my SharePoint SE Farm from the core installation to the newest version?
   Because when I installed the January 2026 CU i just got errors from the config wizard.

   Regards
   Robin

   Reply
   1. 

      Stefan Goßner
      On 27. February 2026 Permalink

      Hi Robin,
      sorry but I’m not sure which fix you mean.
      Can you elaborate?
      Also: what type of errors did you get when executing the configuration wizard?
      Cheers,
      Stefan

      Reply
      1. 

         Robin
         On 2. March 2026 Permalink

         Hi Stefan
         This error which I posted on the January 26 CU post of you:
         I installed a new SharePoint SE single server farm. Now I installed the January CU and get errors.
         1. The Server wasn’t joined to the farm anymore.
         2. When I ran the config wizard i got this error:
         – (provider: SSL Provider, error: 0 – an existing connection was forcibly closed by the remote host.)
         3. When I want to join the farm again
         – I have to fill out a DatabaseServerCertificateHostName. When I choose by encyption “optional”, I can find the Config_DB but get the same error as 2.
         – When i fill out the FQDN from the DB server I get the same error as 2.

         I installed the server certificate from both servers on both servers.

         So my question is, how do I get from the root installation of SharePoint SE to the newest patch?
         Do I have to install all Updats/Feature Updates (like 22H2, 23H1, etc.) to get to the newest patch level?

         Regards Robin

         Reply
         1. 

            Stefan Goßner
            On 2. March 2026 Permalink

            Hi Robin,
            yes the encrypt keyword problem has been addressed in February 2026 CU.
            Cheers,
            Stefan

            Reply
7. 

   Rene
   On 27. February 2026 Permalink

   Hi Stefan

   Our farms were previously on the October CU and have been updated to the February CU were now most existing text webparts cannot be edited. All the text in existing text web part disappears when edit is selected. New text web parts can be added and edited,

   Below are the page controls from Get-PnPClientSidePage for an existing text webpart and a new text webpart
   Text : Willkommen in der Abteilung BWAM
   CanvasDataVersion : 1.0

   Text : Willkommen in der Abteilung BWAM
   CanvasDataVersion : 2.0

   I see that the text webpart editor was updated at some stage
   https://learn.microsoft.com/en-us/sharepoint/sites/new-text-web-part-editing-experience-powered-by-editor-lib-five
   Was something updated recently that affects editing of text webparts?
   Regards
   Rene

   Reply
8. 

   Rene
   On 27. February 2026 Permalink

   Oops…. the difference is as shown below
   Text : Willkommen in der Abteilung BWAM
   CanvasDataVersion : 1.0

   Text : Willkommen in der Abteilung BWAM
   CanvasDataVersion : 2.0

   Reply
   1. 

      Rene
      On 27. February 2026 Permalink

      OK lets try again ….
      The CanvasDataVersion : 2.0 has HTML formatting that is not posting
      CanvasDataVersion : 1.0 has no HTML tags

      Reply
      1. 

         Stefan Goßner
         On 27. February 2026 Permalink

         Hi Rene,
         my suggestion would be to open a support case with Microsoft to investigate this.
         Feel free to send me the SR number using “Contact the blog author” at the top right of this page after it has been created. If I have bandwidth and if the case does not already have an owner I can work on this.
         Cheers,
         Stefan

         Reply
9. 

   Oliver Müller
   On 6. March 2026 Permalink

   After installing the February 2026 Cumulative Update in a customer environment, users are reporting an issue in the Modern Text Web Part where the Enter key stops creating new lines.

   Similar to the known Rooster.js issue in Microsoft’s JavaScript library that we encountered in 2025:
   https://github.com/microsoft/roosterjs/issues/2936

   Has anyone else observed this behavior following the February CU? Thanks for any insights or confirmation.

   As a temporary workaround, pressing Shift + Enter successfully inserts a line break.

   Reply
   1. 

      Stefan Goßner
      On 6. March 2026 Permalink

      Hi Oliver,
      the problem actually came in with October 2025 CU already.
      A hotfix for the issue is in development.
      Cheers,
      Stefan

      Reply