SharePoint 2010 Build Numbers (Cube Sheet)

SharePoint 2010 Build Numbers Cube Sheet

As many times used in our daily business, we’re used to ask for “Build number” rather than “Service Pack or Patch level”.
Because of some confusion of the customers and for transparency I’ll provide here a list of the most relevant Build numbers and its related KB Numbers.

Quick Jump list:

• Most recent CU’s and SP’s (Table view)
• SharePoint CUs and Windows Update – Important Update as per February 2015!
• Important Notes!
• Common Question on Hotfixes, Security Updates and Non-Security related Public Updates for SharePoint
• Notes for SP1
  • List of all SP1 downloads
  • SP1 and June 2011 CU
• Notes for SP2
  • List of available SharePoint 2010 and Office Server 2010 SP2 packages
  • SharePoint 2010 with Service Pack 2 ISO available
• Update sequence of SharePoint 2010 packages
• Links and Resources
• Language Packs
• Background Info on CU’s
• Filter Packs
• Project Server
• The mystery behind SharePoint 2010 Patching
• Slipstream Installations with updates included
• Support Life Cycle for SharePoint Products
  • SharePoint Foundation 2010
  • SharePoint Server 2010
• Office Web Apps for SharePoint 2010
• Understanding Updates for SharePoint Products and Technologies white paper
• SharePoint patching demystified
• Description of the standard terminology that is used to describe Microsoft software updates

Build Tables for other SharePoint versions:

• SharePoint 2007 (MOSS) Builds
• SharePoint 2010 Builds (This List)
• SharePoint 2013 builds
• SharePoint 2016 builds

---

 Important:

• SharePoint 2010 Service Pack 1
• August 2012 CU for SharePoint 2010 and any later will only install on a server/farm which has SP1 installed.
• SharePoint 2010 Service Pack 2
• SharePoint Foundation 2010 with Service Pack 2 ISO available!
  – For SharePoint Server with SP2 slipstreamed please check your MSDN/VLSC subscriptions to download it!
• If you also have Project Server 2010 in your farm, you’ll find the full server package for project server here: http://technet.microsoft.com/en-us/projectserver/gg176680
• Effective with SP2 all subsequent CU’s released after SP2 requires now the service pack 2 as new baseline for installation!
  

---

  Note:
The bits of RTM version are shown in central admin page with Build number “14.0.4762.1000” but it’s actually “14.0.4763.1000” – So no worry about 😉
In case of early publishing, some KB article might not be available right away while the download links already working. Please consider, that delay’s in publishing the according KB articles will be expected!

)1 = in the KB articles for the October 2013 CU there is the Build Number 14.0.7110.5000 mentioned but after installing the Oct. 2013 CU, you’ll find the Build Version 14.0.7108.5000 shown in the central admin.
If you want to be sure that you have installed the right CU/Version, see here for more info about it:

• Common question: why does the version number on the “Servers in Farm” page not change after installing October CU?
• SharePoint does not have a build version. Full Stop.
• SharePoint Patching and Get-SPProduct -local

---

Table View:  [ Last Updated: 2016-12-30 ]  (find the archived Builds prior SP2 here)

Title and post in reference	Build# Srv Build# WSS	MSF2010 * Foundation KB articles	SPS 2010 Server KB articles	Project Server 2010 KB articles	Global language	Notes, Remarks, Known Issues
RTM (04/2010)	14.0.4763.1000	–	–	–	n/a	Major release
SP1 – 2011	14.0.6029.1000	2460058	2510766	2460047	y	SP1 and June CU
SP2 – 2013	14.0.7015.1000	2687464	2687453	2687452	no	–
June CU 13	14.0.7102.5000	2817552	2817527	2817368	y	Blog
August CU 13	14.0.7106.5000 14.0.7106.5002	2817594 2825990	2817570 2825949	2817573 2825959	y	Blog
October CU 13  )1 (Build shown in CA)	14.0.7110.5000 (14.0.7108.5000)	2825824	2825786	2825793	y	–
December CU 13	14.0.7113.5000	2849990	2849971	2849972	y	–
Feb. CU 14	14.0.7116.5000	2863938	2863913	–	y	–
April CU 14	14.0.7121.5000	2878270	2878250	2878253	y	–
June CU 14	14.0.7125.5002	2880975	2880972	2880974	y	–
July CU 14	14.0.7128.5001	2883026	2883005	n/a	y	–
August CU 14	14.0.7129.5000		2889831	n/a	y	see post
August CU 14	14.0.7130.5000	2889825		n/a	y	see post
September CU 14	14.0.7132.5000	2889932	2883103	2883006	n/a	see KB’s
October 14 (no uber!)	14.0.7134.5000	n/a	2899490	2899485, 2880539	y	see post
November 14	14.0.7137.5000	2889933	2899478	2899479	y	SP2 required!
December 14	14.0.7140.5000	2899585	2899583	2899583	y	SP2 required!
February 15	14.0.7143.5000	2910904	2899558	2899557	y	–
MS15-012	–	–	–	–	–	see here
March 15	14.0.7145.5001	2956208	2956201	2956198	y	–
April 15	14.0.7147.5000	2965241	2965294	2965293	y	–
MS15-033 MS15-036	–	–	–	–	–	see here
May 15	14.0.7149.5000	3017815	3015569	2999496	y	–
June 15	14.0.7151.5001	3054847	3054880	3054877	y	–
July 15	14.0.7153.5000	3054983	3054975	3054972	y	MS15-046
August 15	14.0.7155.5001	3055049	3055040	3055038	y
September 15	14.0.7157.5001	3085530	3085521	3085517	y
October 15	14.0.7160.5000	3085613	3085603	3085598	y
MS15-110	n/a	3085613	3085596	–	–	Blog1 Blog2
November 15	14.0.7162.5000	3101547	3101534	3101530	y	–
December 15	14.0.7164.5000	3114418	3114408	3114405	y	–
January 16	no CU released.	n/a	n/a	3114556	y	Blog
February 16	14.0.7166.5000	3114567	3114558	3114754	y	Blog
March 16	14.0.7167.5000	3114886	3114882	3114876	y	–
April 16	14.0.7168.5000	n/a	3114995	3114992	y	–
May 16	14.0.7169.5000	n/a	3115126	3115122	y	–
June 16	14.0.7170.5000	n/a	3115245	3115242	y	MS16-70
July 16	14.0.7171.5002	3114890	3115319	3115316	y	MS16-088
August 16 -not released-	n/a	n/a	n/a	n/a	n/a	n/a
September 16	14.0.7173.5000	3115477	3115473	3115470	y	MS16-107
October 16	14.0.7174.5001	n/a	3118387	3118383	y	MS16-121
November 16	14.0.7176.5000	n/a	3127957	3127952	y	MS16-133
December 16	14.0.7177.5000	3118391	3128036	3128033	y	MS16-148
–	–	–	–	–	–	–
–	–	–	–	–	–	–
–	–	–	–	–	–	–
–	–	–	–	–	–	–

 

  Note:
Due to early posting, sometimes the KB-articles and Descriptions for the updates are not directly working!
So please expect some delay in final publishing of the KB’s!  But the Download Links should work almost immediately!

As usual, the SharePoint 2010 Products Configuration Wizard or “psconfig –cmd upgrade –inplace b2b -wait” should be executed on every server in the farm following the update installation.

Regarding more detailed Info about the Build number shown in your central admin -> servers in farm’s site copmared to what you see on the KB-articles,
Please see here for more:

• Common question: why does the version number on the “Servers in Farm” page not change after installing October CU?
• SharePoint does not have a build version. Full Stop.
• SharePoint Patching and Get-SPProduct -local

New! PowerShell script to display version info for installed SharePoint product and language packs

---

  Note: For SP2 2013 and June 2013 CU:  https://blogs.technet.microsoft.com/steve_chen/p/build2010presp2/#SP1
==> List of all SharePoint 2010 and Office Server 2010 SP1 packages

---

Background Information of Cumulative Update (CU)

Cumulative update packages for Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010 containing hotfixes for the issues that were fixed since the release of SharePoint foundation and SharePoint Server 2010. ´
They are sometimes also called “Uber Package”.

After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or “psconfig –cmd upgrade –inplace b2b -wait” in command line.
This needs to be done on all servers in the farm with SharePoint 2010 installed.
As usually, you should start with the server, hosting the central admin and finishing it there, after all other servers has been updated as well!
The other servers now can run the psconfig wizard in parallel (on MOSS we had to run them sequentially, one by one).

Please see also here for more general info: Common Question: What is the difference between a PU, a CU and a COD?
See also “SharePoint patching demystified”

---

Recommended Update sequence of packages:

As commented by the escalation folks at Microsoft, it should be sufficient to apply only the SharePoint Server2010 “Uber” packages (aka MOSS14; SPS2010) as these contains the SharePoint Foundation packages (aka WSSv4; MSF2010) as well. But still there is a recommendation to stick on the “old common” approach…

Resource: SharePoint Server 2010, SharePoint Foundation 2010 – Updates | TechNet

Extract:
Best practice (this is my opinion and is the result of daily support challenges and issues, that are related to this process!)

For any given build you may find that it is not necessary to install a SharePoint Foundation 2010 update before you install a SharePoint Server 2010 update. This flexibility in the installation sequence is part of the software update system design. However, there might be times where it is necessary to remove this flexibility in order to properly fix a specific issue.

As per this Link now: http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx
“…it is no longer necessary to install the SharePoint Foundation cumulative update and then install the SharePoint Server cumulative update.”

Well yes, its true and you can do so if it is more applicable for your Environment. but I still may recommend to follow as above to keep the best consistency for any updates as well for future.
But yeah, if you don’t want to go the extra step, for common CU updates, the server package (SharePoint) or the full Project Server package suffices all your needs, 😉

---

Slipstreamed installation and updates:
How to create a slipstreamed installation source:
http://technet.microsoft.com/en-us/library/cc261890(office.12).aspx

Be careful when you use SharePoint slipstreamed installations!   – by Jie Li
http://blogs.msdn.com/b/opal/archive/2011/07/06/be-careful-when-you-use-slipstreamed-sharepoint-installation-files.aspx

---

Project Server 2010:
Updates for Project Server 2010
Blog of Brian Smith
Project Server Admin blog
Microsoft Project Support Blog
Service Pack 1 for Microsoft Project Server 2010 (KB2460047)
Service Pack 2 for Microsoft Project Server 2010 (KB2687452)
Most Recent Project Server updates:  http://technet.microsoft.com/en-US/projectserver/gg176680.aspx

Remember!  -> SP1 is a pre-requisite for the Office 2010 February 2013 CUs.

---

Language Packs:
Deploy language packs (SharePoint Server 2010)
Deploy language packs (SharePoint Foundation 2010)
Install Language Packs for SharePoint Server 2010
Install available language template packs (SharePoint Foundation 2010)
Install available language template packs (SharePoint Server 2010)
Install SharePoint 2010 Language Pack on Windows 7   (PDF)
2010 Server Language Packs for SharePoint Server 2010, Project Server 2010, Search Server 2010, and Office Web Apps 2010

Language Pack SP1

• Download the Microsoft Office Servers 2010 Language Pack Service Pack 1 package now
• Service Pack 1 for Microsoft SharePoint Foundation 2010 Language Pack (KB2460059)
• List of all SharePoint 2010 and Office Server 2010 SP1 packages

Language Pack SP2

• Service Pack 2 for Microsoft SharePoint Foundation 2010 Language Pack (KB2687466)
• Service Pack 2 for Office Servers 2010 Language Pack

 Note:
Installing language packs on the Web servers
After you install the necessary language files on the Web servers, you can install the language packs. Language packs are available as individual downloads (one download for each supported language). If you have a server farm environment and you are installing language packs to support multiple languages, you must install the language packs on each of the Web servers.

 Important:
The language pack is installed in its native language. For example, the Russian language pack executable file is in Russian…

SharePoint Foundation 2010 language packs are not required for SharePoint Server 2010 (http://technet.microsoft.com/en-us/library/cc262108.aspx)

---

Filter Packs:
Microsoft Office 2010 Filter Packs

---

Office Web Apps for SharePoint 2010:

Note!
The office Web apps are not like the SharePoint Server updates. They are mostly released either as a single hotfix/update, a security fix or sometimes even as a bulk pack.
So please consider to check via the Windows update services, the Office Team Blogs as listed below and/or via the links from the below table

The Updates for Office Web apps are not maintained in detail like the SharePoint CU updates in this post! I’m only lisitng the most important or Service Packs,
so please apologize if not all updates or not the most recent news are published just-in-time.
If in doubt, run the windows Update service on your Server, hosting the Office Web Apps and check if there is any office web app offered.   😉

See also these blogs and posts for more info:

Office Web Apps for SharePoint 2010 Update overview:	Links:	Notes:
Service Pack 1 for Office Web Apps	Description of Office Web Apps SP1 Patching correctly SP1 and June 11 CU for SharePoint 2010 AND Office Web Apps Service Pack 1 for Microsoft Office Web Apps 2010 (KB2460073) Update Office Web Apps (Installed on SharePoint 2010 Products) with SP1 Description of the SharePoint Foundation 2010 cumulative update refresh package (SharePoint Foundation server-package): June 30, 2011 Office Web Apps on SharePoint 2010 products: What are the updates since the July 2011 updates?	n/a
Service Pack 2 for Office Web Apps	Description of Office Web Apps SP2 Service Pack 2 for Microsoft Office Web Apps (KB2687470)	Known issues
—	—	—

As usual, after you finish applying the updates, run the SharePoint 2010 Products Configuration Wizard,
or from a command line, on each server in the farm:

psconfig -cmd upgrade -inplace b2b -wait

---

Additional or related resources:

• The Office Sustained Engineering and Release team
• Updates for SharePoint 2010 Products
• Updates for Project Server 2010
• Updates for Enterprise Search Products
• Update Center for Microsoft Office, Office Servers, and Related Products
• Software updates overview (SharePoint Server 2010)
• Service Pack 1 for Microsoft FAST Search Server 2010 (KB2460039)
• List of all SharePoint 2010 and Office Server 2010 SP1 packages
• Please see also my post All about updating MOSS or more information on the Install order and what to be considered when installing updates for MOSS 2007/WSSv3

Please send me a comment, if you find a mistake or dead link here,
Thx, Steve  😉