I’m presenting a summarized “Build Numbers Cube Sheet” as I did so before, so please find the most recent info about SharePoint Updates here:
Jump List:
- Current table with all Build Numbers!
- Office Web Apps Server Updates
- Project Server Updates
- SharePoint 2013 Language Packs
- Workflow Manager Versions
In reference to other/older SharePoint Versions, please find here some similar posts:
- Builds and Updates for MOSS/WSS – (applies to: Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0)
- SharePoint 2010 Build Numbers (Cube Sheet) – (applies to: SharePoint 2010 Server and SharePoint Foundation ; aka WSSv4)
- SharePoint 2013 Build Numbers and CU’s – This Post!
Common Questions:
- What is the difference between a PU, a CU and a COD?
- “The expected version of the product was not found on the system”
- Whitepaper explaining the update process of SharePoint
- SharePoint patching demystified
- Terminology of updates (CU, patch, etc.)
- Description of the standard terminology that is used to describe Microsoft software updates
Supportability:
- SQL Server 2014 and SharePoint Server 2013
- Microsoft Product Lifecycle Page (a quick check on product Versions and Support lifetime)
Other related Links to Updates:
- How to: install update packages on a SharePoint 2013 farm where search component and high availability search topologies are enabled
- Software updates overview for SharePoint 2013
- Install a software update (SharePoint 2013)
- Updates for SharePoint 2013
- Update center for Office, Office servers, and related products
Build Matrix: [ last updated: 2016-12-30 ]
All releases prior to SP1 have been offloaded to this Archive-Page here! If you need to check for previous versions and/or information, you will find it there.
Note:
Service Pack 1 will be mandatory requirement for installing any subsequent SharePoint 2013 cumulative updates as the new baseline!
The SharePoint Server 2013 Packs are containing the Foundation Packs and may need only the Server package to be installed!
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). This does not necessarily match the Number outlined in the KB-articles.
Please see here for more information about the SharePoint Build versions and numbers:
- 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
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.
For SP1:
In order to determine if SP1 is installed for Office 2013 or a related product, look for the program version in the list of installed programs in the Programs and Features control panel. If SP1 is installed, the final (fixed) version will be 15.0.4571.1502 or higher. Additionally, if you’ve installed the SP1 update for an MSI product, SP1 will be listed in Installed Updates in that same control panel.
You can also use this PowerShell script to display version info for installed SharePoint product and language packs
=> Service Pack 1 for SharePoint and Office 2013
Important!
- If your farm has been on a patch level lower than July 2015 CU: Unlike other CUs – after installing the August 2015 CU you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.
If you don’t run PSCONFIG after installing August 2015 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 here for detail: http://blogs.technet.com/b/stefan_gossner/archive/2015/07/15/important-psconfig-is-mandatory-for-July-2015-cu-for-sharepoint-2013.aspx - When you install the cumulative update on a single-server SharePoint farm or on SharePoint servers that include Search Service Application topology roles, you should follow the steps that are mentioned on the following Microsoft website: http://go.microsoft.com/fwlink/?LinkId=279911
NOTE!
As of November, 24th, 2014 the Office Web Apps Server will be removed from the Microsoft Download Center.
At that time it will only be available for download under Volume Licensing agreements.
For more information please visit the site Volume Licensing Service Center.
To see which version of the OWA (also called the “Web Access Components” or “WAC”) use the following PowerShell:
PS > (Invoke-WebRequest http://owa.contoso.com/m/met/participant.svc/jsonAnonymous/BroadcastPing).Headers[“X-OfficeVersion”]
see also here for some more insights:
http://blogs.technet.com/b/sammykailini/archive/2013/09/20/how-to-find-the-version-or-build-number-for-an-office-web-apps-2013-farm.aspx
- More Info: Office Sustained Engineering and Release Team
- Language Packs for Microsoft Office Web Apps Server
- Service Pack 1 for Microsoft Office Web Apps Server (KB2880558)
- See all Builds for Office Web apps here!
SharePoint 2013 Language Packs
- Language Packs for SharePoint Server 2013 (RTM)
- Language Packs for SharePoint Foundation 2013 (RTM)
- SharePoint Server 2013 Language Pack Service Pack 1 (SP1)
- SharePoint Foundation 2013 Language Pack Service Pack 1 (SP1)
- Project 2013 and Project Server 2013: Language Packs
- Project Server Updates
- Project Server Service Pack 1
What’s New in SharePoint 2013?
- SharePoint 2013 Top 10 New Features (SharePoint Joel)
- Localization and internationalization improvements in SharePoint 2013
- Following in SharePoint 2013
- SharePoint 2013 RTM Setup and Install
Other related posts:
- Common Question: What is the difference between a PU, a CU and a COD?
- SharePoint Patching demystified
- Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- CHANGE: SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging
- How to: install update packages on a SharePoint 2013 farm where search component and high availability search topologies are enabled
- Update Center for Microsoft Office, Office Servers, and Related Products
- SQL Server 2014 and SharePoint Server 2013
- SharePoint 2013 and .NET framework 4.6
We installed SharePoint Server 2013 last April. Our version is at 15.0.4569.1506. I want to get patched and up to date on everything. Can I start with the September CU or do I need to go back further than that?
LikeLike
We are planning to update SharePoint 2013 server and Office Web Apps 2013 server to SP 1.
SP 2013 RTM ( Build Version – 15.0.4420.1017)
OWA 2013 15.0.4481.1508 (April 2013 Update, KB2810007)
Can I install
http://www.microsoft.com/en-us/download/details.aspx?id=42544 for SharePoint 2013 directly on RTM?
For OWA SP1 can i install http://support2.microsoft.com/kb/2880558 on top April CU update?
LikeLike
Hello Sir ,.. I need your Help .I am getting error while installing sharepoint 2010 in my PC. it shows error while installing sharepoint foundation :-
"setup is unable to proceed due to the folloing error:-
This Poduct requires Windows Server 2008 Service Pack 2 or above.
Correct the issues listed above and re-run the setup"
but Problem is that for windows 7 there is no SP2 or above what i can do..
please Help me to resolve this error.
Thanks.
LikeLike
1)We have SP1 with Version No 15.0.4569.1000 . Do we need to first install Update Re-release or we can directly install September CU2014 … 2) We want to Install Chinese Language Pack . Do we need to install now after SP1 or updated SP1 ?
Answer:you should first install the language pack SP1 and then re-apply the re-released SP1 for SharePoint. If it has some changes, it will install/update the previous pack, If it is the same or nothing to change it will tell you, that no updated needed.
HtH, Steve
LikeLike
Hi Steve,
what about 9 september 2014 update of SharePoint 2013 KB2889864 this is corresponging to Build 15.0.4649.1000
Thank you in advance.
LikeLike
In my SharePoint 2013 farm, it is showing the version as 15.0.4641.1000. I show installed KB2880552 (SP1) and KB2880994 (Security Update). I know July 2014 needs to be installed before I go to August but it looks like my version is past that. Any advice
for which one I should install next?
LikeLike
Hi Steve,
I have installed the sp1 release 15.0.4569.1000 and I need to update the version to the 15.0.4623.1001 (2881061 server package) June 2014 version but the package its failed to install on the server …. you can let me know how to fix this…. any idea!!!
regards,
LikeLike
We have farm version 15.0.4569.1000.
in April 2014 there were two released of CU…..SP1 Pre Mark and SP1 Post Mark….how we will came to know which is our version.
Also is April 2014 CU are applicable on us or not since we used budled installation.
If its applicable will it cover all past CUs and Security Updates?
LikeLike
2817439 URL when I click on "Download the Microsoft SharePoint Foundation 2013 Service Pack 1 package now" – We are sorry, the page you requested cannot be found.
LikeLike
Thanks mate! All clear now. BTW your blog helped me since early MOSS 2007! Thanks a lot!
LikeLike
The link for 15.0.4569.1509 "Fix!" has "support" and "Microsoft" backwards for the hostname.
LikeLike
Hi Steve, I've deployed SP2013 with SP1 (downloaded that from my VLSC) before it was announced that SP1 contains a "feature" that may disable further updating. Would you suggest to re-install RTM version and CU/PU or rather wait for server package to fix my SP1?
LikeLike
Well, we were familiar from SharePoint 2010 and MOSS 2007 the bi-monthly "cumulative updates"
LikeLike
Hi, already a announcement for SharePoint 2013 SP1 and it's build 15.0. or even 15.1. ?
it was announced "early this year"….
http://blogs.office.com/2013/11/20/office-2013-service-pack-1-coming-early-next-year/
LikeLike
Thank you! I'm using this page a lot.
LikeLike
I've installed Patch 2825647 in a SPS2013 Enterprise environment after that Configuration database version is 15.0.4551.1001 , and not 15.0.4551.1005 as shown in the matrix above.
Or is the buildnumber not euqal to the 15.0.4551.1005 ?
LikeLike
No problem Steve! We still have our Revision number not the same as the one annouced by MS. :s
LikeLike
@Gary; Anthony Ennen:
Hey Guys, sorry for the typo, you were right, I made a mistake. Its corrected now.
LikeLike
Hello Steve,
We are in the same situation.
support.microsoft.com tells 15.0.4551.1001 for the foundation package and 15.0.4551.1005 for the Server package which doesn't correspond to your build matrix.
Then, after having installed the kb2825647 CUs, we have our build version set to 15.0.4551.1001. Do you have any idea?
Is it possible than MS just mixed both 2825647 & 2825674…? can't be right?
Many thanks in advance. Regards, Anthony
LikeLike
Hi Steve,
I have the same issue with SP2013 Server version. It's 15.0.4551.1001 .
support.microsoft.com/…/KBHotfix.aspx
LikeLike
@ R_Popescu:
the build 15.0.4554.1005 is the Server package. If your Central admin page Shows the 15.0.4551.1001 then ist the fondation uold only and you may have mistakenly mixed the kb's???
Did you run the PSConfig wizard after each install?The Build number and Version shown in central admin site, under Servers in farm is retrieved from the DLL file version from the [Microsoft.SharePoint.dll], found in C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions15ISAPI
Please double check again and repost if still having a mismatch in build numbers.
Thnx, Cheers, Steve
LikeLike
Ok, so I have a standard version of Sharepoint 2013 and web apps on another server. When applying the October update, what update should I be applying on the web app server?
Also, will the web app update be an issue with Exchange 2013 CU2?
LikeLike
I have discovered a bug in the June CU (possibly even earlier) that is not present in SharePoint RTM: "Unable to post comments in SharePoint 2013 blogs". I've written down this in a blog post: chuvash.eu/…/debugging-oob-sharepoint-unable-to-post-comments-on-sharepoint-blogs-sp2013-june-cu
LikeLike
HI Steve,
I successfully installed KB2825647 (the Server version), with KB2825674 (the Foundation version) installed right before, but the version reported by the farm in the end is 15.0.4551.1001 rather than 15.0.4554.1005. What am I missing? Could it be possible that 4551.1001 is the latest or the KBs should be installed in the reverse order – Server and then Foundation?
Thanks, Radu
LikeLike
@SpBo:
Hi, for Project server, you need to install the march updates first, run PSConfig wiz, install then the august CU and rerun PSConfig wiz.
For SharePoint, ontop of April CU just install the august CU.
If you have office web apps, please install also the according updates there too.
cheers, Steve
LikeLike
Hi Steve, my SharePoint 13 farm is on the Apr'13 CU and I've just installed Project Server 13 RTM and successfully executed psconfig. I'd like to update SharePoint and Project Server to Aug'13 level. What CUs and in what order should I install them? PS March CU first, then PS+SP Aug CU? Thanks
LikeLike
thanks for the info , April update version is different its not 15.0.4505.1002 but
15.0.4505.1005
LikeLike
Hi Jesper, I’m sorry – sure I will Keep it updated as good as possible but since we have monthky release cycles its a bit hard to maintain the Posts aside of my daily work.
pls appologize, I’ll update it asap to most current.
LikeLike
Thanks Steve, really appreciate it. This type of lists are required in order to work with SharePoint, so Microsoft should prioritize time to this 🙂
LikeLike
Hiya,
page is no longer updated?
LikeLike
@Erin:
Hello Erin,
you can apply any CU that has been released after the most recent Service Pack which is currently SP1.
You have SP1 installed, hence you can go ahead and install one of the most recent CU’s being published yet to be all up to latest.
Hth, Cheers, Steve
LikeLike
Hi Dean Morgan, yes 15.0..4701.1000 is March CU – I just havent had tiem yet to update the list. Sorry….
LikeLike
Hello Raj,
no, nothing wrong 🙂
You might have installed the re-released SP1 which has that higher build number on the foundation part (see alos here:
http://blogs.technet.com/b/steve_chen/archive/2014/02/26/3623749.aspx).
Depending on where you looked up the dll it can vary but as long as you have executed the PSConfig wizard after SP1 installed, you should be fine.
The final proof of the correct build version is to check the config DB on table versions, this is the patchlevel of sharepoint that matters and what is displayed in central admin on Servers in Farm.
More info on build numbers and why they may differe can be found on my post above as well.
Hth; cheers, Steve
LikeLike
Thanks alot.
LikeLike
Thanks for the info!
LikeLike
Hello shyam kanungo,
sorry for late reply, Since SharePoint wasnt designed to be isntalled on a PC system, soem tweaks for developers were posted across the web to get it working on a PC as well. So SharePoint expects the Server OS Service Pack version which is the equivalent Service
Pack on PC OS as described below:
– The service packs for Server Operating systems are in correlation to the respective PC OS,
– that means, SP2 for Server 2008 is linked to SP2 for Vista,
– Server 2008 R2 SP1 is linked to Windows 7 and so on.
Please check your PC OS and update it according to its latest SP level, then retry the SharePoint SP2 again – this should work then.
HtH, Kr, Steve
LikeLike
@srinath:Yepp, the previous Link is invalid due to an issue with the SP and was recalled. The new Link is now updated in table, please use the re-released KB and start over.cheers, Steve
LikeLike
thanks
LikeLike
Hi Khalil,
thanks for your notice but it is the "foundation" packages (aka WSSv5) that are actually on 15.0.4505.1002.
The 15.0.4505.1005 is the server package. You can verify the correct file version from the [Microsoft.SharePoint.dll], found in C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions15ISAPI
If you go to your central admin page, servers-in-farm, here you'll see also the build version and finally you can verify it with a SQL query like this:
use [sharepoint_configDB]
select * FROM [sharepoint_configDB].[dbo].[Versions]
The highest Number in column [Id] shows the actual version.
HtH,
Cheers, Steve
LikeLike
@Lukasz: please see here fro more: http://blogs.technet.com/b/stefan_gossner/archive/2014/04/10/sharepoint-2013-sp1-and-april-cu-status.aspx😉
LikeLike
Hello Mani,
to both of your questions: yes, you can install SP1 in either case directly on top of RTM version.
cheers,. Steve
LikeLike
Thanks for the info, it was very useful for me. Just FYI: the "April 2014 15.0.4605.1004 CU 2878240" is now listed As May 7 CU and the download site have 3 revision files to download: ubersrv_2, ubersrv_1 and ubersrv2013kb2878240fullfilex64glb
greetz,
Marcelo.
LikeLike
@Tariq:
I’m not sure what you mean with "two released CU … SP1 Pre Mark and SP1 Post Mark…." ???
AFAIK, there is only one April CU package each (SharePoint server and SharePoint Foundation) as found in the respective KB articles from the table above.
The mentioned Build version is the current SP1 and hence you are fine with it. There was an issue with SP! and maybe that confused you as SP1 hence were re-released, so just download the new and current bits from here: SP Server: KB 2880552; SP foundation:
KB 2880551 and you’re good to go.
For April 14 CU, you should wait or skip it unless you have a specified issue as outlined in the KB.
If you mean with "bundled installation" a slipstreamed install source that includes SP1, then use only these media here:
http://blogs.technet.com/b/stefan_gossner/archive/2014/02/28/sharepoint-2013-with-sp1-quot-slipstream-quot-is-now-available-for-download.aspx
SP1 covers all past CU’s up to but not including the April 14 CU. So its ok to have just SP1 for now. All later CU’s will containing any of the CU’s released after SP1, so no worries if you jump on a later one 😉
Does that answers all your questions?
Cheers, Steve
LikeLike
Great post, thanks Steve.
LikeLike
@Peter Sun:
SP1 is still in Beta testing and earlier announced schedule may slip due to some late submitted bugs, so please stay patient, I’ll post about once it’ll be ready 😉
LikeLike
@Sascha: The given Build number is the one that is stated in the respective KB article. The build Version shown in Central admin page is the the one that comes the config DB. Also the Version of the Microsoft.SharePoint.dll or the Microsoft.SharePoint.portal.dll was recently mostly the same. Now the DLLS can be any other inside the ISAPI Folder and it counts the highest Version of the files changed by the CU which is then presented in KB. So no worry, it is correct, that you have the 15.0.4551.1001 as it is not always the dll as mentioend above and can be differnt than what is seen on the KB. HtH, cheers, Steve
LikeLike
@ArbutusJoe:Thanks for the hint, link is correct now and should work 😉
LikeLike
@HASS:
maybe you have an older package as it was republished due to a regression.
– Please download and install the new, re-released Service pack 1 and retry!
– See more details here:
http://blogs.technet.com/b/stefan_gossner/archive/2014/04/22/sp1-for-sharepoint-2013-has-been-rereleased.aspx
– The KB articles for the re-released Service Packs are different from the recalled Service Pack.
– See also the FAQ all about SP1 etc. here:
http://blogs.technet.com/b/stefan_gossner/archive/2014/02/27/sp2013-sp1-faq.aspx
HtH, cheers, Steve
LikeLike
Steve, Can you continue the chart to include February and March when it comes out?
LikeLike
Hi Dave, sorry I was very busy but its done now,
Enjoy patching 😉
LikeLike
Hi Velizar,
you can try to install the update on top of September CU. if it si already there you will get a popup saying its not required. If it is not part of the sept. CU already, it will install. The Build in the KB is not necessarily the one you see in central admin,
this is outlined above and may happen due to the file version overview listed in the KB as well.
The purpose of this blog is to maintain the usual CU cycle and in some exceptions special patches, PU’s etc. that have direct dependencies to pre-/post- released CU’s – so it doesn’t claims to be fully accurate in ALL existing updates/hotfixes entirely.
While each CU contains all previous fixes published, the most recent CU should be sufficient. A specific patch is only important and to be installed if the particular described issue of it is really affecting your farm.
HtH, cheers, Steve
LikeLike
Hi Neal,
if you are already past the august CU build shown in your central admin, and you have installed the August fixes all as listed above, then all you can do further is waiting for the next following CU which would be the Sept. 2014 Cu yet and install that one
on top. That should append the patch chain to the most recent bits.
Cheers, Steve
LikeLike