June 2022 CU for SharePoint Server 2016 is available for download

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

  • KB 5002222 – June 2022 Update for SharePoint Server 2016 (language independent)
    This is also a security update!
  • There was no language dependent fix released this month.
    The most recent language dependent fix is KB 5002118 from January 2022 CU.

The downloads for June 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 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 June 2022 CU Build Numbers:

Language independent fix: 16.0.5332.1001

 
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:

7 Comments


  1. Hi Stefan.
    It was your habit to mention that corresponding KB is also a security update. Did you forget to mention it or there are new “rules”? Since 4/2022 all updates (KB5002183, KB5002195, KB5002222) are also security updates as I see.

    Reply

    1. Thanks for the hint! There was a problem in my script to generate the patch list.
      I fixed it.

      Cheers,
      Stefan

      Reply

  2. Hi Stefan, Language depentend fix KB 5002118 I’ve already installed in january 2022. (together with KB 5002113). After installing now KB5002222 the cmdlet “(Get-SPFarm).BuildVersion” shows me 16.0.5329.1000. Is that right? In CA under “Check product and patch installation status” I found the version 16.0.5332.1001 for “Microsoft SharePoint Foundation 2016 Core”.

    Reply

      1. Thank you, Stefan. I’m aware of the confusion about build number, build versions, patch level, … but for some time now the build version and the build number have always matched so well that I was a bit unsure after this update 😉

        Reply

  3. Hello Stefan Goßner, how are you?

    After installing the update KB5002222 Infopath Web Forms are showing the error below:

    Can you help us?

    DeserializeVersion1 failed with unhandled exception Microsoft.Office.Server.Security.SafeSerialization+BlockedTypeException: SafeSerialization[Context=EnhancedBinaryReader Deserialization]: type System.Guid not allowed.
    at Microsoft.Office.Server.Security.SafeSerialization.ValidatingSerializationBinder.ResolveAndValidateType(TypeName typeName, Type type)
    at Microsoft.Office.Server.Security.SafeSerialization.ValidatingSerializationBinder.BindToType(String assemblyName, String typeName)
    at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Bind(String assemblyString, String typeString)
    at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name)
    at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)
    at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryObjectWithMapTyped record)
    at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
    at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
    at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
    at Microsoft.Office.InfoPath.Server.Serialization.EnhancedBinaryReader.ReadSerializable()
    at Microsoft.Office.InfoPath.Server.DocumentLifetime.DocumentSessionState.<>c__DisplayClassc.b__8()
    at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock) StackTrace:
    at Microsoft.Office.Server.Native.dll: (sig=5fa0e72f-c37c-49be-8b42-b95544077530|2|microsoft.office.server.native.pdb, offset=28719)
    at Microsoft.Office.Server.Native.dll: (offset=2EAF6)

    Reply

    1. Hi Henan,

      I haven’t seen this and would suggest to open a ticket with Microsoft Support to get this analyzed in more detail.

      Cheers,
      Stefan

      Reply

Leave a Reply

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