January 2023 CU for SharePoint Server Subscription Edition is available for download

The product group released the January 2023 Cumulative Update for SharePoint Server Subscription Edition. Similar to SharePoint Server 2016 and 2019 SharePoint Server Subscription Edition is patched with a language dependent and a language independent fix.

The KB articles for January 2023 CU will be available at the following locations in a couple of hours:

  • KB 5002331 – January 2023 Update for SharePoint Server Subscription Edition (language independent)
    This is also a security update!
  • KB 5002326 – January 2023 Update for SharePoint Server Subscription Edition (language dependent)

The downloads for January 2023 CU are available through the following links:

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 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.

Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.

SharePoint Server Subscription Edition January 2023 CU Build Number:

Language independent fix: 16.0.15601.20418
Language dependent fix: 16.0.15601.20418

Related Links:


  1. Hi Stefan,
    On two farms now, I have received the following error when patching the first server:
    Failed updating SecurityMode and ProtectionLevel in cluster. [Exception=System.Management.Automation.CmdletInvocationException: ErrorCode:SubStatus:Error while loading the provider “SPDistributedCacheClusterProvider”. Check HKEY_LOCAL_MACHINE -> SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\Caching\Providers -> SPDistributedCacheClusterProvider. —> Microsoft.SharePoint.Internal.Caching.DataCacheException: ErrorCode:SubStatus:Error while loading the provider “SPDistributedCacheClusterProvider”. Check HKEY_LOCAL_MACHINE -> SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\Caching\Providers -> SPDistributedCacheClusterProvider. at Microsoft.SharePoint.Internal.Caching.CustomProviderFactory.GetTypeFromRegistry(String invariantName) at Microsoft.SharePoint.Internal.Caching.CustomProviderFactory.CreateInstance(String invariantName) at Microsoft.SharePoint.Internal.Caching.ClusterConfigDictionaryReader..ctor(ClusterConfigElement cs) at Microsoft.SharePoint.Internal.Caching.ClusterConfigurationFactory.GetReader(ClusterConfigElement cs) at Microsoft.SharePoint.Internal.Caching.AdminApi.CacheAdmin.GetCacheAdmin(ClusterConfigElement clusterConfigSettings, String clusterEndpoint, IClusterInformation clusterInfo, Boolean needFileLogging) at Microsoft.SharePoint.Internal.Caching.Commands.ConnectAFCacheClusterConfigurationCommand.InitializeCacheAdmin(ClusterConfigElement clusterConfigSettings) at Microsoft.SharePoint.Internal.Caching.Commands.ConnectAFCacheClusterConfigurationCommand.BeginProcessing() — End of inner exception stack trace — at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input) at Microsoft.SharePoint.DistributedCaching.Utilities.SPVelocityPowerShellWrapper.ExportCacheClusterConfig(String provider, String connectionString, String path) at Microsoft.SharePoint.Upgrade.UpdateClusterConfigurationInSPDistributedCache.Upgrade()]

    Google wasn’t any help here, but the error seems to relate to the Distributed Cache service.

    We routinely disable the Distributed Cache service on a web front end server during the Upgrade phase (and restart it when PSConfigUI wizard is complete). I run the command Remove-SPDistributedCacheServiceInstance; this is supposed to preserve the user experience with Newsfeed and Microblogs while patching is underway. This is suggested by Microsoft here: https://learn.microsoft.com/en-us/SharePoint/upgrade-and-update/video-demo-of-zero-downtime-patching-in-sharepoint-server-2016?redirectedfrom=MSDN

    Both times I encountered the error, I re-enabled the DC by running Add-SPDistributedCacheServiceInstance. Re-attempting the PSConfigUI is successful (it does this as a Repair action).

    Have you encountered this before? Is it a bug? Or am I doing something wrong? Should I be disabling DC to begin with?


    1. More info:
      1. This occurred on a SP 2016 Enterprise farm, and a SPSE farm.
      2. The wizard completes with a failed status, but the upgrade seems to have been successful anyway, because the next run on PSConfigUI does not perform an upgrade, just a repair.
      3. The server in each case has a MinRole of WFE+DC.


      1. I am unable to resolve this issue. All good December 2022 patches and PSCONFIG. Second run does work on psconfig, but 2 timer jobs continue to fail and USE-CACHECLUSTER fails to find cache host. I have 2 single-server farms and my prod farm is WFE+DC. Funny thing, all 3 have failures on finding cachehost, but nothing in logs points to this until the patch and psconfig in January. I am getting some remote registry errors on the connection string and I’ve verified the permissions are good and RR is running. I use a SQL alias and that connects for my farm and nothing else fails. Two timer jobs for feed cache continually fail after psconfig. I’m frustrated. I’m in a “mil” environment, so hard to say if something has changed policy/server/AV/FW, but so far nothing I can find.


    2. Hi All,
      I opened a ticket with Microsoft and they said that in my case, the error arises because the patch is upgrading the Cache Cluster. Since I had halted the service as a patching step (which I had thought was a best practice), it couldn’t export the config file, so it failed the upgrade with a hard error:

      “After January 2023 CU update, while executing Psconfig we are trying to change the SecurityMode and ProtectionLevel paramters in cluster (as the error message says: Failed updating SecurityMode and ProtectionLevel in cluster); in order to do this we are exporting the cachecluster config first and this will fail if DCache is unprovisioned on the machine. The key will be removed by Unprovisioning so you should not unprovision Distributed Cache before the January update.

      Post January patch, you can continue with the standard procedure of unprovisioning DC and performing patching.”

      I will attempt to patch my production farm this weekend, fingers crossed.


  2. I resolved my issue. It was Remote Registry was locked down and I added the WSS_WPG group. Resolved!


    1. Hi Deb, we’re in a “mil” environment as well, and the WSS_WPG group is already there as read-only. What did you see in the logs? I even added the service account that runs the appFabric service, but no luck

      We’re seeing A parameter cannot be found that matches the parameter name ‘Path’. But what path is it? I haven’t found any remote registry error yet.


  3. I added the WSS_WPG group to the WINREG key with Read permissions and now USE-CACHECLUSTER works and get-cachehost comes back with the correct information.
    It has to be added to the WINREG key. This was something that was locked down/changed after the December patching in our environment.


  4. With the last Updates i had the Issue that the STS update took ages to install. When I canceled the STS and tried to Install it it told me the Update was already installed. Furthermore my EventLog had a Log of Issuses from the Restart Manager
    „Application ‚C:\Windows\System32\inetsrv\w3wp.exe‘ (pid 13268) cannot be restarted – Application SID does not match Conductor SID..“ can you please tell me what is the issue here?


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.