December 2022 CU for SharePoint Server 2019 is available for download

A new version of the language independent fix has been released to resolve a problem with the first update. If you already installed the first version of December CU you can install the new fix on top of the old one. If not, just install the new version of the fix. See here for more details:
Trending issue: Incorrect user information is displayed in SharePoint Server 2019 after installing December 2022 CU. The KB articles listed below already point to the corrected version.

The product group released the December 2022 Cumulative Update for SharePoint Server 2019 product family. SharePoint Server 2019 is patched with a language dependent and a language independent fix.

The KB article for December 2022 CU will be available at the following Location in a couple of hours:

  • KB 5002311 – December 2022 Update for SharePoint Server 2019 (language independent)
    This is also a security update!
  • KB 4461512 – Updated version of December 2022 Update for SharePoint Server 2019 (language independent)
    This is also a security update!
  • KB 5002310 – December 2022 Update for SharePoint Server 2019 (language dependent)

The downloads for December 2022 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 2019 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 2019 December 2022 CU Build Number:

Language independent fix: 16.0.10393.20000
Language independent fix: 16.0.10394.20016
Language dependent fix: 16.0.10393.20000

 
Related Links:

12 Comments


  1. Another great year, thanks for this blog Stefan!

    Reply

  2. We are investigating an issues together with MS Premier Support which surfaced after this update. The display name of people columns in edit forms are not correctly resolved anymore.

    Reply

    1. Hi Bart,
      this is a problem we identified in December 2022 CU for SharePoint.
      The Product Group is investigating the issue.
      Cheers,
      Stefan

      Reply

      1. We have put all our site collections in read-only mode to prevent further data corruption. We hope for a fix soon!

        Reply

    2. I can confirm that we also encounter this quite massive problem.

      Reply

  3. Dear Stefan, I admire your work since I started working with SharePoint, ~2015. We have a strange situation where I currently work. They have started migrating from SP13 years ago and never patched the SP19 farm. We are at the SP19 2019 January CU level. Now a major project is to get the newly migrated farm up to the latest CU. Since I never encountered such a big cap between patches, does this mean we need to start and patch every CU since 2019 or can we just apply one of the latest CU Updates, e.g. SP 19 November 2022? Could you please let us know? We found some comments similar to my question, but it was not for a SP19 Farm and I wanted to double check with you. Cheers and happy holidays!

    Reply

    1. Hi Stefan,
      you can just apply the most recent CU and run the config wizard. SharePoint fixes are cumulative – so all older fixes are included in the newer ones.
      Just ensure to install as well the language independent and the language dependent fix.
      Cheers,
      Stefan

      Reply

  4. Hi Stefan, I see the above issues when trying to edit forms the display name is is not being correctly resolved, for us can’t even edit or open the forms (infopath) yeah I know I should move away. I’d assume the fix will also address this?

    Reply

    1. Hi Dag,
      I would assume yes – but I would recommend to open a support case to ensure that your issue is tracked.
      Cheers,
      Stefan

      Reply


    1. Yes – indeed. The blog post has been updated meanwhile.

      Reply

Leave a Reply

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