June 2021 CU for SharePoint 2013 product family is available for download

Stefan Goßner - June 9, 2021 - 25 Comments

The product group released the June 2021 Cumulative Update for the SharePoint 2013 product family.

For June 2021 CU we have full server packages (also known as Uber packages) for all products. No other CU is required to fully patch SharePoint.

As this is a common question: Yes, June 2021 CU includes all fixes from June 2021 PU.

ATTENTION:

Be aware that all Updates for SharePoint 2013 require SharePoint Server 2013 SP1 to be installed first.

Please also have a look at the article that discusses how to properly patch a SharePoint 2013 farm which has Search enabled (see below).

Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hotfix Download Available link in the KB article for the release.

This CU includes all SharePoint 2013 fixes (including all SharePoint 2013 security fixes) released since SP1. The CU does not include SP1. You need to install SP1 before installing this CU.

The KB articles for June 2021 CU should be available at the following locations in a couple of hours:

KB 5001957 – SharePoint Foundation 2013 June 2021 CU
KB 5001961 – SharePoint Server 2013 June 2021 CU
KB 5001959 – Project Server 2013 June 2021 CU
KB 5001956 – Office Web Apps Server 2013 June 2021 CU

The Full Server Packages for June 2021 CU are available through the following links:

After installing the fixes you need to run the SharePoint 2013 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.

Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation 2013 CU. And the Project Server 2013 CU also contains the SharePoint Server 2013 CU and SharePoint Foundation 2013 CU.

Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.

Related Info:

25 Comments

Sarah Robb
On 9. June 2021 Permalink

Hi Stefan,

Any idea if the InfoPath issue (reported by Nitin) introduced in the March 2021 patch has been resolved in this patch?

Thank you
Sarah Robb

Reply
1. Stefan Goßner
  On 10. June 2021 Permalink
  
  Hi Sarah,
  sorry – I cannot find a comment from Nitin in the March 2021 CU blog post for SharePoint 2013.
  Can you send me a link?
  Thanks,
  Stefan
  
  Reply
  1. Sarah Robb
    On 10. June 2021 Permalink
    
    Hi Stefan,
    
    It was actually posted on the April 2021 post. https://blog.stefan-gossner.com/2021/04/13/april-2021-cu-for-sharepoint-2013-product-family-is-available-for-download/#comment-9114
    
    Reply
    1. Stefan Goßner
      On 11. June 2021 Permalink
      
      Yes, the fix is in June CU.
      
      Reply
      1. Sarah Robb
        On 11. June 2021 Permalink
        
        That is great news. Thank you Stefan!
Dwayne Alan Potter
On 17. June 2021 Permalink

Do you know if the InfoPath issue existed in the May CU as well?

Reply
1. Stefan Goßner
  On 17. June 2021 Permalink
  
  Yes. It was fixed with June CU.
  
  Reply
  1. Dwayne Alan Potter
    On 17. June 2021 Permalink
    
    Hi Stefan,
    
    Thank you for the confirmation.
    
    Reply
  2. Randall
    On 17. June 2021 Permalink
    
    Hi Stefan,
    
    We applied the June 2021 CU but we’re still getting the same InfoPath errors.
    
    Thanks,
    Randall
    
    Reply
    1. Stefan Goßner
      On 18. June 2021 Permalink
      
      Hi Randall,
      I double checked and the fix is in the Microsoft.Office.InfoPath.Server.dll with version 15.0.5351.1000.
      Please double check the version of the dll on your machine.
      Thanks,
      Stefan
      
      Reply
      1. Randall
        On 18. June 2021 Permalink
        
        Hi Stefan,
        
        I checked our Microsoft.Office.InfoPath.Server.dll version and it is 15.0.5351.1000.
        
        Thanks,
        Randall
      2. Stefan Goßner
        On 18. June 2021 Permalink
        
        Hi Randall,
        then it seems your scenario is different from the one we have seen and fixed in this CU.
        I would recommend to open a support case to get your specific issue analyzed in more detail.
        Cheers,
        Stefan
Manikanth
On 6. July 2021 Permalink

Known issue reported in June 2021 CU.

https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-sharepoint-enterprise-server-2013-june-8-2021-kb4011698-93187954-fe43-eadf-6788-defd8c8b039c

Reply
Yoann
On 6. July 2021 Permalink

For your information a know issue has been added about KB4011698 :

When third-party assemblies try to access some sensitive properties, user code might be blocked. When this issue occurs, “8gaol” event entries are logged in SharePoint Unified Logging System (ULS) logs. For example, you may find the following entry in ULS logs:

8gaol Unable to access this sensitive property : from outer assembly.

So before to install it in prod, test in your recette environment

Reply
1. Stefan Goßner
  On 6. July 2021 Permalink
  
  A fix for this issue is currently in the works.
  Customers running into this issue after installing June CU should open a support case with Microsoft to get unblocked till the final fix is available.
  
  Cheers,
  Stefan
  
  Reply
  1. Yoann
    On 6. July 2021 Permalink
    
    Thanks Stefan your answer.
    Do you know when fix will be available (July, august, …) ?
    
    Regards,
    Yoann
    
    Reply
    1. Stefan Goßner
      On 6. July 2021 Permalink
      
      Hi Yoann,
      the fix is currently planned to be included in August CU (as always it might change) and it will require changes to the web.config to enable the relevant 3rd party components which should not be blocked.
      A KB article will be made available when the fix is available outlining the necessary steps.
      Cheers,
      Stefan
      
      Reply
      1. Yoann
        On 6. July 2021 Permalink
        
        Okay, thanks for your quick answer !
      2. Ron Veldhoen
        On 13. September 2021 Permalink
        
        Hello, does anyone know if this issue was fixed already in the CU August 2021?
        
        Regards,
        Ron
      3. Stefan Goßner
        On 13. September 2021 Permalink
        
        Hi Ron,
        yes it was fixed.
        You need to install August CU and follow this article to enable relevant 3rd party assemblies:
        https://blog.stefan-gossner.com/2021/08/10/common-error-unable-to-access-this-sensitive-property-8gaol-logged-in-uls-after-installing-june-2021-cu-or-later/
        Cheers,
        Stefan
Wasi ur Rehman Khan
On 11. July 2021 Permalink

Hello Stefan,

I wanted to clear my confusion about this point, “Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation 2013 CU. And the Project Server 2013 CU also contains the SharePoint Server 2013 CU and SharePoint Foundation 2013 CU.”.

I have SharePoint 2013 with SP1, if i install Project Server 2013 CU so that means i don’t need to install SharePoint Server 2013 June CU ?

Regards

Reply
1. Stefan Goßner
  On 11. July 2021 Permalink
  
  Hi Wasi,
  thats correct – but why would you install the Project Server 2013 CU on a SharePoint Server 2013 machine?
  It is bigger and will take longer to install.
  Cheers,
  Stefan
  
  Reply
  1. Wasi ur Rehman Khan
    On 14. July 2021 Permalink
    
    Thanks! Stefan. because we have Project Server2013 installed with SharePoint 2013, that is why we need to update both.
    
    Reply
Pietro Gottardi
On 20. July 2021 Permalink

does someone know if this cu is supported on windows 2008 R2?

Reply
1. Stefan Goßner
  On 21. July 2021 Permalink
  
  Hi Pietro,
  Windows Server 2008 R2 by itself is no longer supported.
  SharePoint fixes are not tested against unsupported operating systems.
  Cheers,
  Stefan
  
  Reply

Share this:

25 Comments

Leave a Reply Cancel reply