Trending issue: Incorrect user information is displayed in SharePoint Server 2019 after installing December 2022 CU – Resolved!

A problem in SharePoint Server 2019 December 2022 CU has been identified which can cause incorrect user information to be displayed in people fields.
Webapplications which host only one site collection should not be affected.
Other SharePoint versions are not affected.

Resolved!

A hotfix has been released which resolves the issue. See below for details.
This is a fix for the language independent part of December CU. The language dependent fix was not affected.

  • KB 4461512 – This update fixes an issue in which the Person field shows the wrong user in the different lists between different site collections.

The downloads for December 2022 CU are available through the following links:

Important: You can either install the above listed fix on top of December 2022 CU for SharePoint Server 2019 or you can install the above listed fix and skip the language independent fix from December 2022 CU. In any case ensure that the language dependent fix from KB 5002310 is installed as well.

16 Comments


  1. Hi Stefan,

    Any updates on the ETA for the Hotfix? This is affecting critical applications in our prod 2019 SP farm.

    Thanks!

    Marc Dinger
    mdinger@libertydentalplan.com

    Reply

    1. Hi Marc,
      an ETA is not yet available.
      Cheers,
      Stefan

      Reply

      1. Thanks for the update; hopefully sooner than later!

        Reply

        1. The fix has been released.

          Reply

          1. Great news! Thanks for the update Stefan!

            Cheers,
            Marc



  2. Is this a problem that affects modern sites or is this problem reported in classic sites as well?

    Reply

    1. Hi Taavi,
      the issue affects as well modern site and classic sites.
      It can show up in Powershell and custom applications.
      Infopath Forms with People columns can also be affected.
      Cheers,
      Stefan

      Reply


  3. The fix is now available.

    Reply

  4. Hey Stefan,

    Just to be clear if we were to patch an environment that had not yet had the December 2022 update, I would install the above fix first and then the language dependent from the previous post. Correct?
    Also our test domain has the December 2022 patch with the error, so I would install the fix there on our servers, then re-run the config wizard as usual?

    Thanks in advance!

    Reply

    1. Yes, first kb4461512 (version 16.0.10394) and kb5002310 (languages.)

      Reply

    2. Correct in all points.

      Reply

  5. Do you know if the fix will be part of the Jan updates?

    Reply

Leave a Reply

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