April CU 2016 for SharePoint 2013 released


This Month CU has been released with a full server packages, a.k.a. "Uber Packages"
This CU contains all previous CU's (and security fixes) since last published Service Pack but does not contain the Service Pack itself!

NOTE!
All Updates for SharePoint 2013 requires
SharePoint Server 2013 SP1 first as mandatory baseline for all following CU’s!

If you are on a lower build 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 April 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 this Blog for detail.

For servers that include search components, please follow specific steps to ensure that you install the Updates correctly.
Please find here important advise on how to do that:
How to install update packages on a SharePoint farm where search component and high availability search topologies are enabled


Please note the following change for new releases. Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Based on the file size, the SharePoint Server 2013 package has been now divided into several separate downloads. One contains the executable file (identified as i.e. ubersrv2013kbxxxxxfullfilex64glb), while the other contains the .CAB file (identified as i.e. ubersrv1,…2  etc.). All of them are necessary and must be extracted to the same folder to successfully install the update. All of them are available by clicking the Download link in the KB article for the release.

Example:
image

Further Information:
As usual, you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm after installing the packages.

  • The SharePoint Server pack (Uber) contains the Foundation packs, so you basically only need to install one Package.
  • The Project Server Packs containing both, so if you install this one, no need for the other two to install additional  

SharePoint 2013 Updates

 

Build Number:  15.0.4815.1000 (may vary due to individual components)

KB 3114935 - SharePoint Foundation 2013 CU (Uber)

KB 3114938 - SharePoint Server 2013 CU (Uber) - adds Cloud hybrid search capability in SharePoint Server 2013

KB 3114936 - SharePoint Server 2013 with Project Server CU

KB 3114934 – Office Web Apps Server 2013 (Note: Office Web Apps Server 2013 fixes can be released in a different cadence to SharePoint)

 

SharePoint related security fixes:

Security Bulletin MS16-042


KNOWN ISSUE:
n/a

Workaround:
n/a


Related Links:

Common Questions:

Other SharePoint Builds and version tables:

Tags Build cumulative Downloads KB Article Patch SharePoint 2013 SPS2013 Update

Comments (2)

  1. PP says:

    Hi Steve
    I see you write this on the patching posts. Does it means let say I'm running on CU November 2015 (higher build than July 2015 CU) and I'm updating the farm to CU April 2016. I don't need to run PSconfig?

    If you are on a lower build 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 April 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 run

    1. Steve [MSFT] says:

      Hello PP,

      "...running the SharePoint 2013 Products Configuration Wizard on each machine in the farm right after installing the CU" was required before that specific CU.
      if you wouldnt run it simply search would stop working. Same can happen on security updates that changes SharePoint bits and once beign deployed automated, the wizard might not be called.
      In general the config Wizard needs to be executed always. It just applies the final state to finish the entire update. If you don't run it, sharepoint would work maybe partly some time but sooner or later you must run the psconfig wizard anyway.
      Does that answers your Q?

      Cheers, Steve

Skip to main content