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
I could install SharePoint 2013 using SQL 2016 SP1 without any hassle but don’t see any support documentation from Microsoft. Request to share the compatibility document of SharePoint 2013 and SQL 2016.
LikeLike
Hello Sushil Paudel,
The answer to this question is no, SharePoint 2013 will never be supported on SQL 2016. (with the exception of SSRS integration, see here for more: https://docs.microsoft.com/en-us/sql/reporting-services/install-windows/supported-combinations-of-sharepoint-and-reporting-services-server)
<underline<In general there is a rule of thumb:
A SharePoint release will support the latest SQL Server version (n) at the time of release as well as the one previous released version (n-1) and one addition/new release of SQL (n+1).
For the case of SharePoint 2013, the following SQL versions are supported:
SQL 2014 = n+1
SQL 2012 = n or aligned with release of SP2013
SQL 2008 R2 = n-1
Hth, cheers, Steve
LikeLike
Please update the information to latest. There is no information of 2017’s.
LikeLike
@kuniyasu: Yes you are right. I am struggeling with time and haven’t updated my list since a while. Will do it soon,
sorry for that 😦
LikeLike
Dears,
As iam exploring the my eBiz SharePoint farm, i found that all license installed are “SharePoint and Project Server 2013 – 15.0.4420.1017 (RTM)”.
I need your advise and experience about the best paractice for patching this farm.
LikeLike
Hello Yuosof Radi,
you can install the SP1 on each server in farm, but if you have Language Packs installed as well, you have to install the respective Service Packs for them too.
Once done, you have to upgrade to SP1 on all your server in farm, regardless if it is a SharePoint or Project server.
After that, you should consider to install one of the most recent CU’s as well to stay in-line with the current update/upgrade levels.
Don’t forget to run psconfig Wizard after each update stage and on each server in farm 😉
cheers, Steve
LikeLike
Hi Steve
currently our prod server is sharepoint 2013 SP1 First release + project server 2013 SP1.
we want to update it all to the recent ones.
so please correct our strategies if its wrong:
1. update Sharepoint SP1 rereleased on all servers
2. update Project server SP1 with the same build number as Sharepoint Rereleased on all servers
3. update December 2016 CU sharepoint + project server on all servers
4. Run psconfig one by one on every server
is that correct?
or after step 2.. i need to run psconfig first?
thanks
mardi
LikeLike
Hello mardi septianto,
after installed SP1 you should run the PSConfig first before upgrading further to Dec. CU.
The PSConfig Wizard has to be exec. on each server in farm as well to fully apply the SP1 and schema updates all over the places.
kr, Steve
LikeLike
Hello,
Does SharePoint Online have a version nubmer?
Thank you.
LikeLike
Hello Larry,
SPO of course has a build number but you may never use it. Its just internally to track the update/upgrade level and to file bugs against the respective build.
Why would you need it?
kr, Steve
LikeLike
Hi Steve,
I would like to update SP1 to November 2016 KB3127933 from the below baseline version.
DisplayName : Microsoft SharePoint Server 2013
DisplayVersion : 15.0.4571.1502
DisplayName : Language Pack for SharePoint and Project Server 2013 -Arabic ???????
DisplayVersion : 15.0.4420.1017
DisplayName : Language Pack for SharePoint and Project Server 2013 – French/Français
DisplayVersion : 15.0.4420.1017
DisplayName : Microsoft SharePoint Designer 2013
DisplayVersion : 15.0.4569.1506
When i was trying to run the CU thru “The expected version of the product was not found on the system.” Could you please help me out here?
FYR, find the patch status from CA: http://sathiya.io/wp-content/uploads/2016/12/Screen-Shot-2016-12-08-at-12.46.28-PM.png
Thanks in advanced.
Regards,
Sathiya
LikeLike
Hello Sathiya_M,
your screenshot shows current patch level 15.0.4875.1506 which is equal to “November 2016 CU” so it should be installed already.
But aside of this, your language packs are not on a proper patch status. They are both (French and arabic) still on RTM version so you need to update the Language packs as well up to SP1 according to the server patch level.
The SharePoint designer seems on SP1 so only most recent updates here are missing if any. Please find the download for the LP SP1 here: https://www.microsoft.com/en-US/download/details.aspx?id=42543 – you need to change the language first, then wati a few seconds until the text shows in the chosen language and now click “Download”.
HtH, cheers Steve
LikeLike
Thank you for your valuable time. I have download and fixed completely.
LikeLike
Hi,
Are there any plans of getting Service Pack 2 of SharePoint 2013 Enterprise server in the near future ?
Thanks!
LikeLike
Hi Bob,
afaik no. Service Packs are usually not only includes all fixes released since RTM. They also may carry some feature upgrades/adds that could enrich the product.
by now, I’m not able to tell you if this is happening in near future.
Cheers, Steve
LikeLike
Hi, i was wondering what happen with the update , there is no July and august patch but they are available.
Thank you
LikeLike
Hi Yannick, sorry I was loaded with other tasks so I missed the updates to be posted. pls. appologize, I’ll work off all missing posts and updates quickly.
LikeLike
Thank you Steve. You an Stefan have been the beacon of everything Microsoft releases for SharePoint updates. Look forward to seeing all updates from you on the build versions for SharePoint.
Cheers,
Ashok
LikeLike
Thanks for this amazing post!
LikeLike
Hi,
There is no Uber Pack since September’15 ?
My SP farm is on last September’15 update and I wait for new Uber to update it.
Thx for your job !
LikeLike
Hello Chris,
pretty much anyone except two since September 2015 are UBER Packages, so feel free to download any one of the most recent ones.
cheers, Steve
LikeLike
Hello Steve,
Thanks for your response.
Today when I searched for OWA CU, I looked that : https://blogs.technet.microsoft.com/stefan_gossner/2016/05/11/may-2016-cu-for-sharepoint-2013-product-family-is-available-for-download/
According to Stefan Goßner, it seems that May 2016 CU is an Uber Pack.
LikeLike
Oups, sorry I read too fast your reply. “anyone except two […] are UBER Packages” Thanks ! 🙂
LikeLike
Hi,
Our SP 2013 environment is only at SP1 (15.0.4569.1509). To get it fully updated would you recommend do it incrementally or would it be ok to go straight to one of the more recent CU’s?
LikeLike
Hi Chris,
you can go straight ahead to one of the most recent CU’s on top of SP1 – no need to do it incrementally.
There are some special cases but very rare where a certain order must be considered not to break the update chain but not since SP1, so you#re good to go.
greetz, Steve
LikeLike
Dear friend,Thanks for the article!!!
iransaffrons.com
LikeLike
For every Patch I tried to download “We are sorry, the page you requested cannot be found.”
Does anybody know what is wrong at Microsoft? Pretty annoying when it is not possible to download a patch, when it is needed…
LikeLike
Hello Martype,
thanks for the heads up, it seems indeed we have an issue here and I’ll send this to our teams for investigation.
cheers, Steve
LikeLike
Thanks, it seems to be working again 🙂
LikeLike
Did not see an update for the Feb’15 updates. I just applied to my environment and see that the updates increment the version number to 15.0.4797.1000.
LikeLike
Hello “AG”,
I assume you mean the February 16 (not 15) – yes, this updates to build number 15.0.4797.1000.
LikeLike
Just wanted to point out that updates for SharePoint Designer are included in the Office 2013 monthly updates. You can’t go off of the KB article number for the SPD update as it won’t match what is in the Installed Updates info.
LikeLike
thanks for the heads-up but I wonder where you saw any SPD references in this post?
LikeLike
My server db version is 15.0.4569.1509 after installing the sp1 2880552.How can i proceed after that there are more than 20 CUs released,i have to install all the CUs upto December2015 or only some CU are enough.
One more question is i did not found August2014 and october2014 CU links in the msdn https://technet.microsoft.com/library/dn789211(v=office.14).I have to install the individual fixes like 2883085 or i can skip the both august2014 and october2014.
LikeLike
Hello,
you can go with the most recent publsihed CU on top of SP1. Each CU contains all previous updates based on last Service Pack. For August and October 2014, there was indeed no CU but soem single fixes as shown in my above table view. But if you go with the latest CU, then these are anyway included.
HtH, cheers – Steve
LikeLike
SharePoint 2013 was originally installed with SP1 slipstreamed. All CUs including October 2015 CU were applied to the farm. Then in December, suddenly, SP1 showed in Windows updates. It was downloaded and installed.
Questions: 1. Why was SP1 installed if SharePoint was originally installed with slipstreamed version of SP1
2. Did the SP1 overwrite all the CUs that were installed up to date ?
Thanks
LikeLike
Hi Yuri,
to be honest, I have no idea. you can check in central admin page unde rservers in farm the version and verify it with the above table. If you find a version lower than the october 2015 CU, the Service Pack might have overwritten the CU but thats unepxtected. I t should at least on installign check teh current version and should not install again if its already on teh according Build version.
To be sure, just install the october CU or a later one on top.
kr, Steve
LikeLike
How can i See the DB Build Number in Client and Server System????
LikeLike
Hello Parag,
The DB Build is found in the SharePoint Config DB, in table “Versions”. the same can be found in the central admin pages under “Servers in Farm”
example: Configuration database version: 15.0.4737.1000
For the “Client System” I’m not sure what you mean with this?
if you are meaning the Office 2013/2016 Client like Word, Outlook etc., then this Build version is found under the Menu “File -> Office Account -> About …Link.
Hope that helps a bit.
LikeLike
Hi Darel,
the first SP1 release has had a regression and that’s why a 2nd release came out. So if your Prod-Box is currently only deployed with the first SP1 but no other CU’s afterwards, then just go ahead and reinstall the 2nd SP1 release on top to get the same build
version. If any CU’s are already installed on it as well, then the latest CU you have had installed from all might be reinstalled after the 2nd SP1 release the same way to assure a not broken update chain.
But in any case, please make a full backup of your servers and databases so that you can roll back in case of a critical error.
HtH, cheers, Steve
LikeLike
Hi Mark,
I’m sorry but I fear that I didn’t understand your problem. Can you be more specific?
When one user goes to his own MySite and uploads/updates his Profile Picture, then this goes by default to the mysite host location under "…//User Photos/Profile Pictures/…"
Once uploaded, then this should appear there with its respective "{userTest1Name}_MThumb.jpg" a.s.o.
You should see the tiles when browsing the above given URL.
I don’t know what you mean with {CurrentUserName}… this should be according to your settings under the user profile and mysite settings or how you have defined the URL to be constructed at MySite creation time (Manage Profile Service – My Site Settings –
Setup My Sites Site Naming Format… ).
if you cannot fix it by these settings, then please open a support case with MS to investigate this deeper.
Thanks and cheers, Steve
LikeLike
I ran into the schema version problem of moving a backup of a site collection from one server to another because my development server did not have service pack 1 installed, but my production server did. No problem, I just downloaded the SP1, installed,
configured my development server to be SP1 with expectation all would be well. Microsoft had published a new SP1 with bug fixes that took my development server to 15.0.4701.1000 which is greater than my production site of 15.0.4569.1000. Although both of my
sites report they're at SP1, restore-spsite won't work with the error of "Schema version of backup 15.0.4701.1000 does not match current schema version 15.0.4569.1000". I think this is rather silly to occur if I'm trying to keep two sites up to date together.
I guess I have to try and make them the same always, which I am now becoming worried installation of KBs won't guarantee as Microsoft changed the SP1 kit between my installs. This really should not occur, but oh well. Any thoughts on how to get these two in
line since I have a development site collection that I realty need to put in production. Is there a good, recommended KP to apply to both? I really didn't want to take my production farm down to just move a site collection. 😦
Thanks,
Darel
LikeLike
Hi!
I have a sharepoint server 2013 with October 2015 (15.0.4763) KB. When I go to user profiles and try to upload a photo for testUser1, always set picture for the current user (my photo). Instead of "http://{mySiteHostUrl}/User Photos/Profile Pictures/{userTest1Name}_MThumb.jpg"
olways set "http://{mySiteHostUrl}/User Photos/Profile Pictures/{CurrentUserName}_MThumb.jpg". This error is not until October update. But after 15.0.4763 kb there is an error!! Help me, please
LikeLike
hello Lon Feuerhelm,
I’m sorry but I’m not sure If I got your problem correctly (typo?) So if you have a higher build now as the patch is you installed, then this si indee very strange. can it be, that meanwhile automated updates have been applied right at the same time and hence
a potential security fix on SharePoint might have now a higher build version? can you verify in config database, table versions, what the build numbers are shown in sequence?
if in doubt, just go with the next higher build,install it and see whether the patchlevel is now eual on each server in farm.
And of course, don’t forget to run the config wizard!
cheers, Steve
LikeLike
I just finished applying the May 2015 CU to two of our dev farms when the install was complete I ran (get-farm).buildversion and it returned build 4753 (Sep CU) instead of 4719 I used the same files last month and got version 4917 installed as it should,
any idea what would cause this behavior.
LikeLike
Hello Colin Campbell,
many thanks for the heads up, I’ve fixed the link and it should work now 😉
Thanks a lot.
LikeLike
@Anuj :same answer as for ans, use this link
http://support.microsoft.com/kb/2880552 and install SP1, the rereleased package that should come up with Build 15.0.4571.1502.
kr, Steve
LikeLike
Hi steve,
Thanks for your reply.
After installing sp1 my configuration data base number is 15.0.4420.1017
but my client has 15.0.4569.1000 version.
So if i create site back up then will it work on clients server ?
Thanks.
LikeLike
Hi Anuj;
Version 15.0.4420.1017 is RTM Build so it cant be if you have installed SP1. With SP1 you must have version 15.0.4569.1000 or even 15.0.4571.1502 (see re-released SP1 Post)
So for any reasons this doesn’t looks good at all and you should ensure you have installed the correct updates and have run the PSConfig wizard after it!
The client version 15.0.4569.1000 is SP1 from first release and should be updated to 15.0.4571.1502 anyway.
However, a site backup/restore might not work on different versions.
Please check again, if you are really have installed the service pack correctly and config wiz executed.
LikeLike
@ans :
your version:15.0.4420.1017 = the RTM Version of the product. The next service pack is SP but please install the re-released version of it (Should be then Build 15.0.4571.1502). The Download Link is:
http://support.microsoft.com/kb/2880552
HtH, cheers, Steve
LikeLike
G’day, and thanks for an awesomely useful blog.
The link for ‘Notes’ in the July 2015 CU is broken, I expect it should be:
http://blogs.technet.com/b/stefan_gossner/archive/2015/07/15/important-psconfig-is-mandatory-for-july-2015-cu-for-sharepoint-2013.aspx
LikeLike
Hi,
my share point version from central administration is "Configuration database version:15.0.4420.1017".
i want to update my version to "15.0.4569.1000".
so what i need to do for it please.
if i need to download updates so please give me links.
please help me.
LikeLike
Hi,
my share point version from central administration is "Configuration database version:15.0.4420.1017".
i want to update my version to "15.0.4569.1000".
so what i need to do for it please.
if i need to download updates so please give me links.
please help me.
LikeLike
Hello "Tech ",
I guess its likely related to a known problem with the first release of SP1. You might have installed this one before the rereleased SP1 and added the December CU which is not a problem but may cause your error now. Please check in config DB on table "version"
what buld you have installed for SP1 and verify it with the build number form the 2nd released SP1 (see the table above).
Pls. See also this post here for more info:
http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx
cya, cheers, Steve
LikeLike
We have currently on our SharePoint 2013 farm the SP1 and December 2014 CU (kb2910938),
Now, we want to update again by installing the July 2015 CU (kb3054937), but when running "ubersrv2013-kb3054937-fullfile-x64-glb" we encounter a problem with the error message :
"The expected version of the product was not found on your system"
Do you know why this error ? And what happen ?
LikeLike
It is in point of fact a great and helpful piece of info. I am happy that you shared this useful info with us. Please stay us up to date like this. Thanks for sharing.
http://staygreenacademy.com/
LikeLike
Hi, Thanks for all of this. Could you please add another column to the grid that indicates if it is an Uber-update? This is my second full installation, and it hasn't got much easier (- SP1). Takes 2-3 days to research what to install on a fresh install.
Currently, to be sure I haven't missed anything, I have to install all CU's (selectively cumulative updates) since SP1 (the second one). Also, I think the volume license image is bad. It still displays 15.0.4569.1000 as the build number..
This was very helpful in determining that I need to install all patches:
http://blogs.technet.com/b/stefan_gossner/archive/2014/08/19/sharepoint-patching-demystified.aspx
LikeLike
I am seeing 15.0..4701.1000 but that is not yet listed would that be the March CU?
LikeLike
my sharepoint configuration version show 15.0.4569.1000 after install service pack 1 service install version changed 15.0.4571.1502 then i checked microsoft.sharepoint.dll it shows 15.0.4569.1000 is any wrong
LikeLike