SharePoint 2010 Build Numbers Archive up to SP2

SharePoint 2010 Build Numbers Archive up to SP2

This is the archived part of my current Post “SharePoint 2010 Build Numbers (Cube Sheet)” to keep the main view short and focused on the most recent information and important updates ūüėČ

Here you’ll find a table with all released Builds since SharePoint 2010 went RTM up to latest Service Pack!

  Important Notes!

Table View of all Updates Since RTM up to Service Pack 2

Title and post in reference

Build# Srv
Build# WSS

SPS 2010 Server KB articles

MSF2010 *
KB articles

Project Server 2010 KB articles

Global Language

 Notes, Remarks, Known Issues

public Beta (rel. 11/2009) 14.0.4536.1000 n/a Preview
RTM (04/2010) 14.0.4763.1000 n/a Major release
June 2010 CU1
Non-CU! Single Fix!
14.0.5114.5000 983319 y Blog
June 2010 CU1
Non-CU! Single Fix!
14.0.5114.5003 983497 y Blog
June 2010 CU1
Non-CU! Single Fix!
14.0.5114.5000 2124512 y Blog
June 2010 CU1
Non-CU! Single Fix!
(osrchmui-ja-jp.msp, osrchmui-ko-kr.msp, osrchmui-zh-cn.msp, osrchmui-zh-tw.msp)
14.0.5114.5003 2182938 ja-jp
June 2010 CU1
Non-CU! Single Fix!
14.0.5114.5003 2204024 y Blog
June 2010 CU1
Non-CU! Single Fix!
14.0.5114.5003 2281364 y Blog
Aug. CU 10 14.0.5123.5000 2352342 2352346 y
Oct. CU 10 fixed packages 14.0.5128.5003 2394320 2394323 y Blog
Dec. CU 10 14.0.5130.5002 2459257 2459125 y 2490381
Feb. CU 11 14.0.5136.5002 2475878 2475880
April CU 11 14.0.5138.5001 2512800 2512804 y
SP1 – 2011 14.0.6029.1000 2510766 2460058 2460047 y SP1 and June CU
June CU 11 (fixed Srv build)  )x
June CU 11 (WSS)
2536599 2536601 y SP1 and June CU
Aug. CU 11  (Server)
Aug. CU 11  (WSS)
2553048 2553050 y Blog
Oct. CU 11  )** 14.0.6112.5000 2596505 2596508 y
Dec. CU 11  )** 14.0.6114.5000 2597014 2597058 y
Febr. CU 12 )** 14.0.6117.5002 2597150 2598321 y
April CU 12 )** 14.0.6120.5006 2598151 2598321 y
June CU 12 )** 14.0.6123.5002 2598354 2598373 y
Aug. CU 12 )**
Aug. CU 12 )**    (WSS)
2687353 2687355 y Blog
Oct. CU 12 )**
Oct. CU 12 )**     (WSS)
2687564 2687566 y
Dec. CU 12 )**
Dec. CU 12 )**    (WSS)
2596955 2596957 y
Feb. CU 13 )** 14.0.6134.5000 2767793 2760791 y
April CU 13 )** 14.0.6137.5000 2775353 2794728 y
SP2 – 2013 14.0.7015.1000 2687453 2687464 2687452 no

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.

The Build number shown in your central admin -> servers in farm’s site is the version that comes from the configuration database (table dbo.versions).
Please see here for more:
Common question: why does the version number on the “Servers in Farm” page not change after installing October CU?

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

 Dependency between SP1 and June 11 CU!!
It is not a recommendation or advice, it is a must, as it is clearly specified on the SP1 KB:

Known  issue:
After you install SharePoint Foundation 2010 SP1 or SharePoint Server 2010 SP1, you must also install the corresponding June 2011 Cumulative Update refresh
. For more information about these updates, click the following article numbers to view the articles in the Microsoft Knowledge Base:

2536601  (
Description of the SharePoint Foundation 2010 cumulative update package (SharePoint Foundation server-package): June 30, 2011

2536599  (
Description  of the SharePoint Server 2010 cumulative update package (SharePoint server-package): June 30, 2011

 June 11 CU –¬† New FIM bits implemented!
With the June 2011 CU package, there is also a new FIM release (ForeFront Identitiy Manager aka “missclient.exe”) published.
Where before, the FIM showed up with version 4.0.2450.11, you’ll after installing June 2011 CU notice, that it will come up now in version 4.0.2450.34 yet.

Posts by CAPES:
SharePoint 2010 SP1 and the June Cumulative Update for SharePoint 2010
Office 2010 Service Pack 1:   Five Common questions regarding the Service Pack

Ee721049.note(en-us,office.14).gif  Note for SP1: 
Microsoft SharePoint Server 2010 Service Pack 1 (SP1) provides the latest updates for SharePoint Server 2010.
This service pack includes two main categories of fixes:

  • Previously unreleased fixes that were made specifically for this service pack. In addition to general product fixes, these fixes include improvements in stability, performance, and in security.
  • All the public updates that were released through June 2011, and all the cumulative updates that were released through April 2011.

See also:

For clarification: 

If you are currently on any Build prior or equal  April 2011 CU, please perform the update as follows:

  • Install the SP1 packages for SharePoint Foundationon all Servers in Farm
  • Install the according Language packs (if applicable) on all Servers in Farm
  • Install the SP1 packages for SharePoint Serveron all Servers in Farm
  • Install the according Language packs (if applicable) on all Servers in Farm for each language installed!
  • Install the Office Web Apps SP1(if applicable)
  • Install the SharePoint Foundation June 2011 CUon top on on all Servers in Farm
  • Install the according Language packs (if applicable) on all Servers in Farm for each language installed!
  • Install the SharePoint Server June 2011 CUon top on on all Servers in Farm
  • Install the according Language packs (if applicable) on all Servers in Farm for each language installed!
  • The SharePoint 2010 Products Configuration Wizard or “psconfig ‚Äďcmd upgrade ‚Äďinplace b2b -wait‚ÄĚ should be run once on every server in the farm following the final update installed.

Q:   Is it true that installing only the server packages would be sufficient as they contain the foundation packages anyway?
A:   We recommend installing the SharePoint Foundation 2010 packages followed by the SharePoint Server 2010 packages to ensure all binaries are properly updated as a best practice; however, Server packages will include the Foundation package so they could be installed independently. The June CU does not include all of the files included in Service Pack 1 so should be installed following Service Pack 1.  In order to ensure everything is up to date, you will need to install both packages.

Ee721049.note(en-us,office.14).gifNote for SP2 2013 and June 2013 CU:
The recently published June 2013 CU for SharePoint and Foundation is NOT INCLUDED into the SP2!
if you have already installed the June 2013 CU (on top of SP1) on your SharePoint servers, SP2 should be installed on top to stay aligned with the patch level chain. You must install SP1 Prior to SP2 to apply the June 2013 CU as it will not install on top of SP2! Else, you can wait for the Agust 2013 CU to be installed on top of SP2 which then have June 203 CU included.

Best recommended Install order:

1. If not yet done, Install SP1 + June 2011 CU
2. Then install June 2013 CU
3. Now you can install SP2 + any later released CU.

Note: Due to required changes to the Prerequisite Installer, Service Pack 2 cannot be slipstreamed into installation media for use with installation on Windows Server 2012 systems. Installation of SharePoint Server 2010 with Service Pack 2 on Windows Server 2012 systems requires an integrated Service Pack 2 installation media due following the patch release.

FAQ’s:¬† <updated:¬† 2013-07-31>

Q:¬† with the SharePoint 2010 June 2013 CU (KB2817527), and now the August 2013 CU (KB2817570), the server package includes a CAB file (ubersrv_1.CAB) in addition to the executable. Curious about the logic behind this change …
A:  Its because we are reaching a physical file size limit of 2GB. So it had to be split.

Q:¬† Is this a “Post-SP2 hotfix”?¬† – What’s the relationship between SP2 and August 2013 CU?
A:  June and August CU are both Post SP1/SP2 CUs. You can install August CU in SP1 or SP2. But we highly recommend to stay inline with the chronological patch history to stay consistent.

==> 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

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.

I personally recommend that you always install SharePoint Foundation 2010 patches before installing SharePoint Server 2010 patches. This best practice ensures that you will always be successful when installing updates and keeps you on the save side.

 Install Order:
– start with the Foundation update,
– then run the Psconfig wizard
– reboot if prompted
– install now the server packages
– then run the Psconfig wizard again
– reboot once more if prompted
– check for errors on logs!
– check on Central admin page -> Upgrade and Migration -> Upgrade status / product and patch installation status

repeat this for each server in farm.

As per this Link now:
“…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:

Be careful when you use SharePoint slipstreamed installations!   Рby Jie Li

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:

Ee721049.note(en-us,office.14).gifRemember!  -> 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

Language Pack SP2

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.

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 (

Filter Packs:
Microsoft Office 2010 Filter Packs

 Office Web Apps for SharePoint 2010:

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
Service Pack 2 for Office Web Apps Known issues

As usual, after you finish applying the updates, run the SharePoint 2010 Products Configuration Wizard. Or, at a command line, on every server in the farm, run:  psconfig -cmd upgrade -inplace b2b -wait

Uninstall or Disable Office Web Apps? Use this guide to chose whether Office web apps might be required or should be uninstalled:

Additional or related resources:

Please send me a comment, if you find a mistake or dead link here,
Thx, Steve¬† ūüėČ

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s