February 2023 CU for SharePoint Server 2016 is available for download

The product group released the February 2023 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 2023 CU should be available at the following locations in a couple of hours:

  • KB 5002350 – February 2023 Update for SharePoint Server 2016 (language independent)
    This is also a security update!
  • KB 5002325 – February 2023 Update for SharePoint Server 2016 (language dependent)
    This is also a security update!

The downloads for February 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 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 2023 CU Build Numbers:

Language independent fix: 16.0.5383.1000
Language dependent fix: 16.0.5383.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:

4 Comments


  1. Hello Stefan,
    in this CU there is a fix for the problem relative on Distributed Cache, about your post relative on Januart 2023 patch ?

    Thank you

    Reply

    1. Hi Roberto,

      a permanent solution for the issue is still being investigated.
      Currently the only solution is to apply the steps from my article.

      Cheers,
      Stefan

      Reply

      1. Where is the article located, you mentioned in your response?

        Reply

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.