Steve Chen [MSFT] Sr. Support Escalation Engineer

...about SharePoint mysteries and related

SharePoint 2010 Build Numbers (Cube Sheet)

SharePoint 2010 Build Numbers (Cube Sheet)

  • Comments 57
  • Likes

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 Matrix for other SharePoint versions:


Ee721049.note(en-us,office.14).gif  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. Usually the Build number shown in Central admin comes from the Configuration Database, from table dbo.versions. This is mostly the same version as the [Microsoft.SharePoint.Dll] which reflects the Build version of foundation services.  I Know, it's a bit confusing but the shown version in central admin although the higher "server or Uber package" has been installed, is still the correct one ,-)  if you want to be sure that you have installed the server CU you also can check it in Central Admin -> Upgrade and Migration -> Check product and patch installation status. This will show you the versions installed.

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

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

RTM (04/2010) 14.0.4763.1000 - - - n/a Major release
SP1 - 2011 14.0.6029.1000 2510766 2460058 2460047 y SP1 and June CU
SP2 - 2013 14.0.7015.1000 2687453 2687464 2687452 no -
June CU 13 14.0.7102.5000 2817527 2817552 2817368 y Blog
August CU 13 14.0.7106.5000




y Blog
October CU 13  )1
(Build shown in CA)


2825786 2825824 2825793 y -
December CU 13 14.0.7113.5000 2849971 2849990 2849972  y -
Feb. CU 14 14.0.7116.5000 2863913 2863938 - y -
April CU 14 14.0.7121.5000 2878250 2878270 2878253 y -
June CU 14 14.0.7125.5002 2880972  2880975  2880974 y -
July CU 14 14.0.7128.5001 2883005 2883026


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 2883103 2889932 2883006 n/a see KB's
October 14 (no uber!) 14.0.7134.5000 2899490 n/a 2899485, 2880539 y see post
November 14 14.0.7137.5000 2899478 2889933 2899479 y SP2 required!
December 14 14.0.7140.5000 2899583 2899585 2899583 y SP2 required!
February 15 14.0.7143.5000 2899558 2910904 2899557 y -
MS15-012 - - - - - see here
March 15 14.0.7145.5001 2956201 2956208 2956198 y -
April 15 14.0.7147.5000 2965294 2965241 2965293 y -
- - - - - see here
May 15 14.0.7149.5000 3015569 3017815 2999496 y -
June 15 14.0.7151.5001 3054880 3054847 3054877 y -
July 15 14.0.7153.5000  3054975 3054983 3054972 y MS15-046
August 15 14.0.7155.5001 3055040 3055049 3055038 y  
September 15 14.0.7157.5001 3085521 3085530 3085517 y  
October 15 14.0.7160.5000 3085603 3085613 3085598 y  
MS15-110 n/a 3085567


- - Blog1
November 15 14.0.7162.5000 3101534


3101530 y -
- - - - - - -
- - - - - - -

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

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

If you want to be sure that you have installed the correct CU you also can check it in Central Admin -> Upgrade and Migration -> Check product and patch installation status. This will show you the versions installed.

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

<updated:  2013-07-31>    FAQ's: 

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: 
" 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  ;-)

  • A recent question to my sheet:

    Q:  On this post and several other sites I see the build numbers 14.0.4762.1000 and 14.0.5123.5000 listed but no 14.0.5123.5002 listed.

         Is there a reason 14.0.5123.5002 isnt listed in your article?

    A:  This fix (14.0.5123.5002) is a single hotfix for a specific issue ( and is included in the October CU!

        On my sheet, there is only listed the each cumulative update or so called “Uber-Packages” which are containing all fixes provided

        in-between the regular CU frequency.

    When you install the cumulative package, you’ll have included all single fixes, newly released since last prior CU.

    So in your case, if you install the Oct. CU, the mentioned fix is included.

    Hope that answers your Question ;-)

  • For clarification, you are supposed to install the June CU AFTER SP1, not before, as is shown in the list.

  • Hi Vince,

    you're right but the list should not imply the install order bat rather giving a cube of all updates since RTM, but thnx, I'll correct this right away to not confuse any others further.

    Please note my changed post above...

    cheers, Steve

  • (logged in before commenting this time)

    Hi Steve

    Thanks for putting together this post, I use it religiously

     >Best Practice

     >I personally recommend that you always install SharePoint Foundation 2010 patches before installing SharePoint Server 2010 patches.

    This best practice is no longer correct. As per this link it has changed:

     >The packaging of cumulative updates changed as of August 31, 2011

     >As a result of the new packaging, it is no longer necessary to install the SharePoint Foundation cumulative update and then install the SharePoint Server cumulative update.

    So can you please strike-through that Best Practice and add that comment and link

    Cheers, Adam Cogan

  • Hi Adam,

    many thanks for your commitment to my blog and your comments. Well yes it is not necessary anymoer to install both parts of the pacakges (foundation + server) but it still becomes important on certain scenarios and combinations and may casue unexoected issues if you dont do so.

    For short:  yes, it is sufficient just to install the Server CU or Project packages as they contain all required bits. But it is just an extra mile but not a problem when you still follow my recommendations.

    Its just for future cases and for consistency at all to be on the secure side. However, as written above, its just my personal view and also have been stated so on the sustained engineering blog whch are the folks that creates the fixes ;-)

    anyway, thnx, cheers and greetz, Steve

  • Very good content, congratulations.

  • Nice list and other useful information.  Thank you for putting it together and keeping it up to date.

    I have a question about language pack build numbers.

    After installing Dec. 2012 CU on all servers in the farm, I checked the Patch Levels Status (http://servername:port/_admin/PatchStatus.aspx) and see that while core sharepoint and the databases are 14.0.6131.5003, the various language packs are mostly 14.0.6029.1000 (SP1), but some items for each language pack range from 14.0.6029.1000  to 14.0.6131.5003.

    Shouldn't all the build numbers be the same?

    Or are their specific CUs/Patched for the language packs that need to be applied after installing a CU?

    Thank you,


  • Hi Tom,

    depending on what the fix contains, not all files/DLLs will be patched/updated. If you check the Microsoft.sharepoint.dll file version, this reflects the most recent update status. For language packs, usually also service packs will be served and needs to be installed inline with the SharePoint patch level. So if you have SharePoint SP1+ AND LP Sp1 applied as well, still not all files would show up the same version, so this wouldn't be a mistake. finally the CU in general are commonly "global" means they are not language specific and will patch the installed language files too. All related information on language packs can be found here:

    Hope that helps and answers your Q.

    Cheers, Steve

  • Is there a documentation that matches which OWA CUs are required/needed in a particular SP2010 CU?

  • Hi Cherina,

    I'm assuming you mean with "OWA" NOT the 'Outlook Web Access' but 'Office Web App', right?

    Well,  there is no direct mapping to CU's. Only at Service Pack Level, the updates should be aligned. The 'Office Web App' updates are released separate and in my post above you'll find all Web App updates published so far. if ther eis a new one, I'll add it here, else you can also simply search for updates on

    Hope that asnwers your Question ;-)

  • A recent Question about updating WAC (aka Office web app Server) reached me and here is the conversation:


    My customer is in SharePoint Server 2010, with August 2012 CU. They have Office Web Apps SP1 in place. They are thinking of updating Office Web Apps. I think that latest that we have that’s publicly available is June 2011 CU ( According to the KB article, this is a hotfix but we refer to it as a CU. Since it is a hotfix, it’s a single update. Does this mean that the customer should have installed a CU prior to June 2011 CU?


    The referenced KB is a single hotfix for a specific issue with Microsoft PowerPoint 2010 by using Web apps. So it is not a full WAC packages nor is it a CU.

    However, unfortunately there is no matrix or alignment between the WAC updates and the default SharePoint CU’s.

    So in case you want have them anyway,

    There are no “server/rollup packages” for Office Web Apps, and none of the SharePoint packages will contain Office Web App Fixes. You must download each individual Office Web App Patch and apply it.

    The only direct mapping is the Service pack level and all other “hotfixes” are single packs mostly for a certain version i.e. Excel, PowerPoint, Access etc. and they are only recommended to be installed


    Reply: is being referred as June "CU" in this blog:

    Step 1: SharePoint Server 2010 SP1:

    Step 2: Office Web Apps SP1:

    Step 3: SharePoint Server 2010 June CU:

    Step 4: Office Web Apps June CU:


    The blog you mentioned, describes the special circumstance with our SP1 and June CU geared up to each other and hence needs to be applied in that order ;-)

    For all later CU’s for SharePoint, there is no mapping to single hotfixes for office web apps.

    The WAC fixes are mostly security fixes and should come via WSUS or Windows online update anyway.

    If not, its only recommended to install these fixes if you having the described problems.

    There appear to be a couple of fixes for office web apps fix for October 2011 and they are KB 2687562, KB 2687617, 2760391, and 2687614 but these are for single product versions like one for excel, PowerPoint a.s.o.  None of them is considered as a full WAC rollup packages and hence each one considered only for a specific issue.

    Hope that helps,

  • Hi,  i have the Aug 11 CU installed on my environment 14.0.6109.5002 (not 14.0.6109.5005) as posted here.

    And I am trying to update to april 13 CU version 14.0.6137.5000, and I am receiving the message: "The expected version of the product was not found on the system".

    But the pre Prerequisites as informed on KB page are only the SPS2010 SP1 and SPF2010 SP1, and they are already installed.

    What am I missing?




  • @Marcos

    Are you sure, that your last CU was properly installed? Since you have installed the Aug 11 CU with 14.0.6109.5002, the error might come from a check against the updated Version of the aug. 11 CU with 14.0.6109.5005. This was a fixed Versions as it might had a Regression in the 5002 build and hence, the update probably check for the increment and may prevent you here from installing any higfher bits. Please try and get the fresh Aug.11 Cu on 5005 Build and install it on top, this should help to get the next higher CU's after. If this still does not work, then you maybe have another issue and this needs to be investigated within a MS Service request.

    HtH, cheers, Steve

  • @steve - Stefan ( indicated I could install June 2013 CU on top of RTM, and then Service Pack 2, but I'm getting a messaging indicating "The expected version of the product was not found on the system" the only successfully way I have been able to accomplish this is via the way you mentioned above?

    Why is this so difficult, why are there not any indication of these issues mentioned in any of the KB articles for the CU or service pack?

  • @steve - what you offered here: is the golden ticket. Moving forward I will use this combinaton in the order you listed.

    Thank you, this was driving me insane.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment