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


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

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

As this is a common question: Yes, June 2016 CU includes all fixes from June 2016 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 2016 CU should be available at the following locations in a couple of hours:

  • KB 3115171 – SharePoint Foundation 2013 June 2016 CU
  • KB 3115174 – SharePoint Server 2013 June 2016 CU
  • KB 3115172 – SharePoint Server 2013 with Project Server June 2016 CU
  • KB 3115170 – Office Web Apps Server 2013 June 2016 CU – This is also a security fix!

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

Important: If your farm has been on a patch level lower than July 2015 CU: July 2015 CU and later contains a breaking change compared to earlier builds which requires running the SharePoint 2013 Products Configuration Wizard on each machine in the farm right after installing the CU.
If you don’t run PSCONFIG after installing June 2016 CU (on a farm which had a lower patch level than July 2015 CU) crawl might no longer work – so ensure to schedule a maintenance window when installing this CU which includes PSCONFIG runs.
See here for detail: https://blogs.technet.microsoft.com/stefan_gossner/2015/07/15/important-psconfig-is-mandatory-for-july-2015-cu-for-sharepoint-2013/

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

Related Info:

Comments (19)

  1. Andreas says:

    Hello Stefan,

    link for SP2013 Server June CU seems to be broken. Any reason or will it be back again soon?

    1. Hi Andreas,
      I just tested and the download works fine for me.
      Please check again.
      Cheers,
      Stefan

  2. Andreas says:

    It’s working again, so I guess it was a temporary problem.

  3. Brad says:

    Hi Stefan,

    We started to notice after applying the June CU to our 2013 environment that the ability to show/hide subsites in our navigation settings under look and feel no longer works. If we select either and click ok the changes are not being applied. Any thoughts? My next step was to open a case up on this.

    1. Hi Brad,

      I would recommend to open a support case to get this analyzed.

      Cheers,
      Stefan

    2. Brad,

      I’ve seen the same issue after installing the June 2016 CU — so it definitely looks like a bug. Hopefully you’ve already opened a support incident with Microsoft to initiate the process for getting it fixed.

      1. Brad says:

        I did open a case a month or so ago and it has been logged as a bug. When it gets addressed I am not certain of.

  4. Debra Dorn says:

    The following happened to our farm after June 2016: choice columns with set your own value is now greyed out. Editing the 14 hive form.js did not work. Can no longer use the drop down with your own value. Choice works though. Permissions warnings on all sites that have limited access for any user. These are in all 2010 compatibility mode sites, lists and libraries.

    1. Hi Debra,
      did you open a support case with Microsoft to get this analyzed?

      1. Deb Dorn says:

        Stefan, I copied over the 15 Hive Form.js and replaced the 14 Hive Form.js. This has resolved the problem in our stage environment and we are doing other testing. Unable to really open a case but we do have some onsite MS consultants that I have passed this to as well.

        1. Hi Deb,
          this is an unsupported change and could cause problems with future updates. I would recommend to revert this change and to open a support case with Microsoft.
          Cheers,
          Stefan

          1. Deb Dorn says:

            I’m aware of that. I’ll replace when I run the updates, but I have a lot of users complaining. We don’t have an easy route to opening support cases with MS due to budget cuts (govt). I have pushed it up the chain.

          2. Debra Dorn says:

            Actually they have now given us a way to do this and I have submitted my ticket.

  5. Adi says:

    Hello Stefan,

    We started to notice after applying the June CU to our 2013 environment that the ability to use the “edit your profile” – button at the my site does work and show the user “Sorry, something went wrong
    An unexpected error has occurred.” after clicking the button. So I went to the ULS and find out that the web application service user of my mysite try to access the search administration database. Was there any changes at the search with this CU? I could find a similar topic related to this issue > https://support.microsoft.com/de-de/kb/2970281.

    Thank you very much in advance.
    Br, Adi

    1. Hi Adi,
      sorry – I don’t know from the back of my head.
      If you need info on this I would encourage to open a support case with Microsoft.
      Cheers,
      Stefan

      1. Vijay says:

        Hi Stefan,

        Post installing SP2013 June 2016 CU, we are facing an issue.
        When a user tries to edit his profile by clicking on “edit the profile” an error comes up saying “An unexpected error has occurred” with correlation Id.

        Same happens when the user tries to change the photo. Correlation ID in both the cases doesn’t give anything of error or warning type in ULS logs.

        Same happening on our DEV and UAT environment. Could you please advice if it is a bug in CU?

        1. Hi Vijay,
          this is not (yet) a known issue. I would recommend to open a support case with Microsoft to get this analyzed.
          Cheers,
          Stefan

        2. Adi says:

          Hi Vijay,
          did you get the same error at your ULS, as i received?
          Br, Adi

  6. Javier says:

    Hi, we have applied this patch and we are having issues with one site collection where we have the RBS setup using the Metalogix StoragePoint with these errors
    Sorry, something went wrong in the default.aspx page
    The URL ‘ is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web. When uploading files even if the file is small, but the ULS logs refers to claims authentication and we already checked the space in the database and the permissions, which were fine previous to this patch installation.
    Still working on these issues.

Skip to main content