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:

Build Tables for other SharePoint versions:

image Important:

Bildergebnis für notice  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:

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

Title and post in reference

Build# Srv
Build# WSS

MSF2010 *
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
y Blog
October CU 13  )1
(Build shown in CA)
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
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
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


Bildergebnis für notice  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:

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

Bildergebnis für notice  Note: For SP2 2013 and June 2013 CU:
==> 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.

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

Ff182925.Important(en-us,office.14).gif 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.

Ff182925.Important(en-us,office.14).gif 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 (

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 n/a
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 from a command line, on each server in the farm:

psconfig -cmd upgrade -inplace b2b -wait

Additional or related resources:

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

69 thoughts on “SharePoint 2010 Build Numbers (Cube Sheet)

  1. Hi Steve,
    We have SharePoint farm 2 application and 2 web front end servers running SharePoint server SP1. We are going to upgrade SP2 and CU November 2016 leaving out December 2016 just to be on the safe side. We are on English language packs so I don’t think we need to upgrade any language packs. Do you see any issue in all of the above? Thanks Cliff


    1. Hi Cliff Fernandes,

      if English is your default language the farm was installed with, then you may not anticipate problems.
      If English LP was installed because your default setup language was different, then you have to update LPs first.

      hope that answers your Q,

      cheers, Steve


  2. Hi there.
    We have an “older” version of SP2010 installed – it version 14.0.7015.100. It is base installed as English , and we added the French language pack.
    I’d like to update it to the latest CU, with the least possible issues (isn’t this what we all aim for :))
    Can you tell me if this is a direct CU install? Or are there intermediate steps – other packages to be installed first.
    Should the SP Foundation CU be installed then the SP Server CU, then the Language Packs?

    Thanks for your help,


    1. Hi Zolt,

      with language packs there is always something special to be considered. First: once you install a language pack such as French, then you need to make sure you have on top of it all service packs for the according language packs installed. Second you may only install the next higher or most recent CU on top of it since CU’s are “global” and will then patch also the LP specific files if any.
      To be fully on a safe side, after installed LPs and it’s according Service Packs, you can go with CU for foundation first, patch all servers and then repeat with the CU for server packages. With this you might be good to go since LP realted files in foundation AND server path will be then updated properly.
      HtH, cheers, Steve


  3. Hi Steve,
    The Security Update for SPS 2010, MS15-110 – KB3085567, takes to Security Update for SPS2013
    Looks like this needs correction



  4. Hi Steve,

    Thanks for such useful and time saving article.

    I have a confusion. I have a got a SP Server 2010 with no patch installed.
    I installed a hotfix(December CU ’13) to fix some issues following the installation of Service Pack 1 for SP Server.

    Now, I have to update it upto the latest patch available, I think it is Dec CU’15.

    I didn’t install SPS Service Pack 2 yet. But it released before Dec CU’13 update. So i am confused if I should install Service Pack 2 or not?

    Another thing, does a most updated CU release includes all the changes of the previous CU releases?

    Or should i install each and every CU release upto Dec’ 15?

    Please help me because i am too much confused if i should install from Feb’14 to Dec’15. What I have understood that I should install Service Pack and RTM and most updated CU release. Kindly help me.

    Thanks a lot in advance.


    1. Hello David,

      On a SharePoint RTM install, you have to install service pack 1 and 2 on top. Then you can go further with the latest CU released after SP2.
      All CU’s include the previous updates as well down to the last published Service Pack.
      HtH, cheers, Steve


  5. Answer to "…wrong version after installing KB3085521":

    Hi, pls visit the link below to understand the mismatch 😉

    -> Common question: why does the version number on the "Servers in Farm" page not change after installing October CU?

    cheers, steve


  6. I have installed KB3085521, according to the table, I am expecting to see 14.0.7157.5001 version, but when I run "(Get-SPFarm).buildversion" command, i notice that the version showing is 14.0.7155.5000, any clue?


  7. Hi Steve,
    We're running on SharePoint Server 2010 Service Pack 1 with August 2012 CU. It seems out of support from Microsoft. i would like to patch the servers (2 web, 2 app) to SP2. The question is that if i can just install the SP2 on top of whatever currently we have


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