January 2021 CU for SharePoint Server 2016 is available for download

17 Comments

1. 

   stefano2203
   On 13. January 2021 Permalink

   Hey Stefan,

   In the description you stated that in the current month only one language independent patch was released and we should use the last released patch from October. But in the text below it says that in January also a language dependent patch was released, the same is for last month?
   How can I understand this?

   Greez,

   Stefano

   Reply
   1. 

      Stefan Goßner
      On 13. January 2021 Permalink

      Hi Stefano,
      sorry – this was a copy&paste error.
      Its fixed now.
      Cheers,
      Stefan

      Reply
      1. 

         stefano2203
         On 13. January 2021 Permalink

         Cool!
         Thank you very much and a happy new year!

         Reply
2. 

   Faisal
   On 14. January 2021 Permalink

   it doesn’t like the farm version was upgraded to 16.0.5110.1000 in the Central Admin > Manage Servers in farm. Neither the below PS cmdlet is showing that #.
   (Get-SPFarm).BuildVersion

   The farm version still shows 16.0.5095.1000 that is for Dec 2020 update level.

   The Central Admin > Upgrade and Migration > Check product and patch installation status page does show the updates installed and their version as 16.0.5110.1000

   I’m assuming due to following information
   https://blog.stefan-gossner.com/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/

   If a patch changes this version number – will this version number always reflect the version in the KB of the CU it came with?
   Short answer: No

   Reply
   1. 

      Stefan Goßner
      On 14. January 2021 Permalink

      As outlined in my article only the “Check product and patch installation status page” shows correctly if the patch was installed and which components have been updated.

      You should never rely on the database schema version or (Get-SPFarm).BuildVersion.

      Cheers,
      Stefan

      Reply
      1. 

         Renton Blackstone
         On 28. January 2021 Permalink

         Hi Stefan

         I had the same issue with this patch. Even after a successful psconfig the farm version does not change. I also ran get-spfarm.buildversion and got the same results. I rebooted and then ran it all again to the same effect. We are using the CU for our install because we are installing on a brand new 2016 build. I also have other 2016 (non production) farms where I have run the same patch on all servers, and the result is the same (patch shows as installed and psconfig runs succesfully but no build number update.)

         Reply
         1. 

            Stefan Goßner
            On 29. January 2021 Permalink

            Hi Renton,
            yes thats expected. The farm version is not an indicator if a patch was installed.
            Jan CU does not change the farm version.
            See here for details how to correctly identify if a patch is installed:
            https://blog.stefan-gossner.com/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/
            Cheers,
            Stefan

            Reply
3. 

   MK
   On 22. January 2021 Permalink

   Hi Stefan,

   Thanks a lot for your support.
   I am planning to deploy December patches for Sharepoint 2016.
   And the new January patches released so, what i should to do.
   Deploying only January patches (it will be enough) or Deploying December first and then January patches.

   May help me please as I am confused 😕

   Reply
   1. 

      Stefan Goßner
      On 22. January 2021 Permalink

      Hi MK,
      SharePoint fixes are cumulative – means you only have to install January CU and it will include everything from all earlier CUs.
      Cheers,
      Stefan

      Reply
4. 

   Dawosch
   On 25. January 2021 Permalink

   Hey, i have an english SharePoint 2016 installation with german language pack. I installed the the language indepened cu in english and the language depended cu in german.

   But now i get the following error:

   Grant-SPObjectSecurity : Das Argument ‘Rights’ ist ungültig. Gültige Werte sind: Lesezugriff auf den
   Terminologiespeicher, Lese- und eingeschränkter Schreibzugriff auf den Terminologiespeicher, Vollzugriff auf den
   Terminologiespeicher
   In C:\AutoSPInstaller-master\SP\Automation\AutoSPInstallerModule.psm1:2618 Zeichen:21
   + … Grant-SPObjectSecurity $metadataServiceAppSecurity -Princ …
   + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   + CategoryInfo : InvalidArgument: (Microsoft.Share…tObjectSecurity:SPCmdletGrantObjectSecurity) [Grant-
   SPObjectSecurity], SPException
   + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletGrantObjectSecurity

   Reply
   1. 

      Stefan Goßner
      On 25. January 2021 Permalink

      Hi Dawosch,
      there is only one flavor of the language dependent and the language independent fixes.
      The language selection dialog on download center is by design but independent which language you pick you will always get the same fixes.

      About the issue: I haven’t seen this so far. If you need assistance to get this analyzed, I would suggest to open a support ticket with Microsoft.

      Cheers,
      Stefan

      Reply
   2. 

      Andre
      On 7. May 2021 Permalink

      We had the same problem last Week and after a lot of digging we found out, that somehow the Culture in PowerShell was messed up. It was showing en-US but it was still expecting German permissions. The solution was to overwrite the culture of the executing thread of the PowerShell that executes the AutoSPInstaller script to en-US 1033 manually.

      So we put a snippet somewhere in the beginning of AutoSPInstallerMain.ps1 – I put it right after:

      Import-Module -Name “$env:dp0\AutoSPInstallerModule.psm1” -Force
      #endregion

      Here is the snippet:

      $lcid = 1033
      $culture = new-object “System.Globalization.CultureInfo” $lcid
      [System.Threading.Thread]::CurrentThread.CurrentUICulture = $culture
      Write-Host -ForegroundColor Red ” — USING CULTURE: $culture —”

      All it does is setting the UI culture of the executing Thread to 1033 en-US.

      I hope it helps someone.

      Reply
5. 

   Henry Cheung
   On 5. February 2021 Permalink

   Hi Stefan,

   Does January 2021 CU for SharePoint Server 2016 include the fix for update file size over 100MB issue October 2020 CU?

   https://blog.stefan-gossner.com/2020/11/10/trending-issue-upload-of-files-larger-than-100-mb-fails-since-october-2020-cu/

   Thanks as always
   Henry

   Reply
   1. 

      Stefan Goßner
      On 8. February 2021 Permalink

      Hi Henry,
      the fix for this was first included in December 2020 CU and of course it is also part of January CU.
      Cheers,
      Stefan

      Reply
6. 

   Scott Swann
   On 25. February 2021 Permalink

   Stefan,

   I had some issues with a clients SharePoint 2016 RTM Build a few days ago. The problem I had was it was still the RTM build and never been updated. When I proceeded to update to the Jan 2021 CU files (Both dependent and independent ) It updated the user.aspx and then proceeded to have an error in that page. Something went wrong”. “An error occurred during the compilation of the request file, or one dependencies. ASP._LAYOUTS_15_USER_ASPX” Does not contain a definition for ‘SharingLinksGroupsDS_ObjectCreating’ and no extension method ‘SharingLinksGroupsDS _ ObjectCreating’. Well after a large investigation I discovered that the user.aspx page was updated, which contained this reference to the ShareingLinksGroupsDS_ObjectCreating”. Well the problem was that the Microsoft.SharePoint.ApplicationsPages.dll did not get updated even though the user.aspx did. Not sure why the CU did not update that dll. SO to resolve I had to copy over the old user.aspx page and then it continued to work. Not a good solution since each CU will cause this same issue.

   Reply
   1. 

      Stefan Goßner
      On 2. March 2021 Permalink

      Hi Scott,
      has PSConfig been run after installing the update?
      All dlls in the _app_bin directory of the different web applications including the Microsoft.SharePoint.ApplicationPages.dll are updated with the psconfig run and not when installing the update.
      Cheers,
      Stefan

      Reply
7. 

   Thorsten Schollmeyer
   On 16. March 2021 Permalink

   Hi after installing this CU, when User go on Show files in Explorer in the Document library, they get an User & Password request dialog. Is this this in your enviroment the same? Or any idea what has changed here?

   Best Regards
   Thorsten

   Reply