SharePoint 2013 Build Numbers and CU’s

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:

In reference to other/older SharePoint Versions, please find here some similar posts:

Common Questions:


Other related Links to Updates:

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.

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!

Version Build # Type Foundation Package (KB) Server Package (KB) Project Server Updates Office Web apps Language specific Notes
SP1-released Apr.2014
fixed Build:
SP 2817439
yes Known Issue
Re-released SP
April 2014 15.0.4605.1004 CU 2863892 2878240 2863899 global Known Issue1
Known Issue2
MS14-022 15.0.4615.1001 PU 2952166 2952166 2952166 n/a Security fix
June 2014 15.0.4623.1001 CU 2881063 2881061 2881051 global Different Build Nr.
July 2014 15.0.4631.1001 CU 2882999 2882989 2883003 global -
August 2014 15.0.4641.1001 Indiv.Fixes,no "Uber" Pack! 2883081 2883085
2883093 global See Post
September 2014 15.0.4649.1001 CU 2883087 2883068 n/a global -
October 2014 15.0.4659.1001 no "Uber" Pack! 2889946 2899469
2889898 global See Post!
November 2014 15.0.4667.1000 CU 2899468 2889944 n/a global See Post
December 2014 15.0.4675.1000 CU 2910945 2910938 2899574 global See Post
February 2015 15.0.4693.1001 CU 2920801 2920804 2956101 global -
March 2015 15.0.4701.1001 CU 2956159 2956166 2956158 global Known Issue
April 2015
15.0.4711.1000 CU 2965261 2965266 2965306 global Known Issue1
Known Issue2
May 2015 15.0.4719.1002 CU 3039747 3039780 3039748 global -
June 2015 15.0.4727.1001 CU 3054864 3054866 3054865 3054863 global -
July 2015 15.0.4737.1000 CU 3054931 3054937 3054933 3054930 global Known Issue    MS15-070
August 2015 15.0.4745.1000 CU 3055004 3055009 3055005 3055003 global Known Issue
MS15-081 n/a PU 3054858 3055003
September 2015 (single patches) n/a no "Uber" Pack! 3085501 3085481 3085501 3085481 3054998 3085483 3054870 3054813 3085501
3085481 3054998 3085483 3054870 3054813
3085487 n/a
September 2015 15.0.4753.1003 CU / Uber!(delayed) 2975894 2986213 2986195 3085487 global Aug.CU required!
MS15-099 n/a - 3085501 3054861 - 3085487 -
MS15-110 n/a PU - - - - - Blog
October 2015 15.0.4763.1002 CU 3085488 3085492 3085489 3085571 global Blog
November 2015 15.0.4771.1000 CU 3101368 3101373 3101369 3101367 global Blog
MS15-116 n/a PU - - - - - Blog
December 2015 15.0.4779.1000 CU 3114339 3114345 3114341 - global Blog
MS16-004 15.0.4787.1000 Sec.Bulletin - 3114503
- - - Known Issue
Januar 2016 15.0.4787.1000 CU 3114492 3114497 3114493 n/a global MS16-004
February 2016 15.0.4797.1001 CU 3114722 3114726 3114723 3114338 global MS16-015
Known Issue
March 2016 15.0.4805.1000 CU 3114822 3114827 3114823 3114821 global MS16-029
April 2016 15.0.4815.1000 CU 3114935 3114938 3114936 3114934 global Known Issue
May 2016 15.0.4823.1003 CU 3115023 3115029 3115024 3115022 global MS16-054
June 2016 15.0.4833.1000 CU 3115171 3115174 3115172 3115170 global MS16-070
Known Issue
July 2016 15.0.4841.1000 CU 3115290 3115293 3115291 3115289 global MS16-088
August 2016 15.0.4849.1000 CU 3115447 3115450 3115448 3115446 global includes Aug.PU
September 2016 15.0.4859.1000 CU 3118271 3118279 3118274 3118270 global MS16-107
October 2016 15.0.4867.1002 CU 3118361 3118366 3118365 3118360 global MS16-121
November 2016 15.0.4875.1000 CU 3127930 3127933 3127931 3127929 global MS16-133
December 2016 15.0.4885.1000 CU 3128001 3128005 3128003 n/a global MS16-148
- - - - - - - - -

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:

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


  • 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:
  • 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:

Office Web Apps Server 2013:

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[“X-OfficeVersion”]

see also here for some more insights:

SharePoint 2013 Language Packs

 Project Server 2013 Updates:

What's New in SharePoint 2013?

Other related posts:

Comments (111)

  1. Saffron says:

    Dear friend,Thanks for the article!!!

  2. Martype says:

    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…

    1. 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

      1. Martype says:

        Thanks, it seems to be working again 🙂

  3. 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.

    1. Hello “AG”,
      I assume you mean the February 16 (not 15) – yes, this updates to build number 15.0.4797.1000.

  4. ktaber says:

    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.

    1. thanks for the heads-up but I wonder where you saw any SPD references in this post?

  5. Firdouz Hussain says:

    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 have to install the individual fixes like 2883085 or i can skip the both august2014 and october2014.

    1. 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

  6. yuri says:

    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 ?

    1. 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

  7. Parag Shah says:

    How can i See the DB Build Number in Client and Server System????

    1. 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.

  8. 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

  9. 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

  10. Darel says:

    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. 🙁



  11. Mark says:

    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

  12. 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

  13. Lon Feuerhelm says:

    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.

  14. Hello Colin Campbell,

    many thanks for the heads up, I’ve fixed the link and it should work now 😉
    Thanks a lot.

  15. @Anuj :same answer as for ans, use this link and install SP1, the rereleased package that should come up with Build 15.0.4571.1502.

    kr, Steve

    1. anuj says:

      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 ?


      1. 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.

  16. @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:

    HtH, cheers, Steve

  17. 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:

  18. Anuj says:


    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.

  19. ans says:

    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.

  20. 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:

    cya, cheers, Steve

  21. tech4 says:

    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 ?

  22. SharePoint 2013 Online Training says:

    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.

  23. Chris says:

    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:

  24. Dean Morgan says:

    I am seeing 15.0..4701.1000 but that is not yet listed would that be the March CU?

  25. Raj says:

    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

  26. Erin says:

    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?

  27. Mani says:

    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 for SharePoint 2013 directly on RTM?

    For OWA SP1 can i install on top April CU update?

  28. shyam kanungo says:

    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.


  29. Neeraj says:

    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 ?

    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

  30. Velizar says:

    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.

  31. Neal says:

    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?

  32. HASS says:

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

  33. Tariq Younas says:

    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?

  34. srinath says:

    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.

  35. LukaSz says:

    Thanks mate! All clear now. BTW your blog helped me since early MOSS 2007! Thanks a lot!

  36. ArbutusJoe says:

    The link for 15.0.4569.1509 "Fix!" has "support" and "Microsoft" backwards for the hostname.

  37. LukaSz says:

    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?

  38. Anonymous says:

    Well, we were familiar from SharePoint 2010 and MOSS 2007 the bi-monthly "cumulative updates"

  39. Peter says:

    Hi, already a announcement for SharePoint 2013 SP1 and it's build 15.0. or even 15.1. ?
    it was announced "early this year"….

  40. SP_Bert says:

    Thank you! I'm using this page a lot.

  41. 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 ?

  42. Anthony Ennen says:

    No problem Steve! We still have our Revision number not the same as the one annouced by MS. :s

  43. @Gary; Anthony Ennen:

    Hey Guys, sorry for the typo, you were right, I made a mistake. Its corrected now.

  44. Anthony Ennen says:

    Hello Steve,

    We are in the same situation. 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

  45. Garry says:

    Hi Steve,

    I have the same issue with SP2013 Server version. It's 15.0.4551.1001 .…/KBHotfix.aspx

  46. @ 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

  47. hayden says:

    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?

  48. Anatoly Mironov says:

    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:…/debugging-oob-sharepoint-unable-to-post-comments-on-sharepoint-blogs-sp2013-june-cu

  49. R_Popescu says:

    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

  50. @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

  51. SpBo says:

    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

  52. Khalil Khan says:

    thanks for the info , April update version is different its not 15.0.4505.1002 but


  53. 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.

  54. Thanks Steve, really appreciate it. This type of lists are required in order to work with SharePoint, so Microsoft should prioritize time to this 🙂

  55. Hiya,
    page is no longer updated?

  56. @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

  57. Hi Dean Morgan, yes 15.0..4701.1000 is March CU – I just havent had tiem yet to update the list. Sorry….

  58. 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:

    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

  59. 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

  60. @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

  61. 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.


    Cheers, Steve

  62. Hello Mani,

    to both of your questions: yes, you can install SP1 in either case directly on top of RTM version.
    cheers,. Steve

  63. 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


  64. @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:

    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

  65. Ed (DareDevil57) says:

    Great post, thanks Steve.

  66. @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 😉

  67. @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

  68. @ArbutusJoe:
    Thanks for the hint, link is correct now and should work 😉

  69. @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:
    – 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:

    HtH, cheers, Steve

    1. Dave says:

      Steve, Can you continue the chart to include February and March when it comes out?

      1. Hi Dave, sorry I was very busy but its done now,
        Enjoy patching 😉

  70. 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

  71. 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

Skip to main content