I have SharePoint server 2013 installed inside windows server 2008 r2. and i have updated the SharePoint server 2013 using windows update to use the latest CU.

so the final CU which i have installed is September 2014 CU and SP1.

now i run the following command:-

PS C:\Windows\system32> (get-spfarm).buildversion

Major  Minor  Build  Revision

-----  -----  -----  --------

15     0      4641   1000

but i can not find this version number inside the CU version on this link

so can anyone advice what does my current version relates to ? Thanks

2 Answers 2


thats from a blog, refer to microsoft technet for more uptodate version info:

September 9, 2014 update for SharePoint Server 2013 (KB2889864)

This article describes update KB2889864 for Microsoft SharePoint Server 2013 that was released on September 9, 2014.

This update includes stability and performance improvements.


this build version is updating on the 12-Aug-2014 update that contains those files and carried on from 27-Jul-2014 update.


so that being said you can refer to this:

it shows you the latest builds for each area


latest build is:

This is build 15.0.4649.1001 of the cumulative update package

check manual way for verification on updates applied onto server:

central admin -> upgrade and migration -> check product and patch installation status


ok i understand your frustration but if your updating correctly and that sharepoint is uptodate than there is no reason to be conserne. as i noted it could be several issues that could cause you to get the different build number:

to understand what is going on look into the powershell code your using:


looking on msdn it states the following for the function SPFarm.BuildVersion:

Gets the Microsoft SharePoint Foundation build version of the server farm.

now read this as noted earlier:

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

also like to note:

the powershell is looking up on build version not patch build version!

if you were to look into the kb for october you would see some items on old build and some on new builds. But the overall build from powershell is correct.


Yes its important that you run wizard every time you do a CU,

I would:

1) install CU

2) reset server

3) run SharePoint Products Configuration Wizard

4) reset server

5) check to make sure by running powershell code!

the SharePoint Products Configuration Wizard will update the content database and configuration database with the update and apply any patches.

its very important to apply cu on all front end servers before you run SharePoint Products Configuration Wizard!!!!

Run the SharePoint Products Configuration Wizard on the Central Administration server (APP-1) to upgrade the configuration database and upgrade each content database serially.

also note:

Run the configuration wizard to ensure that if an update fails for a specific server, the error is not propagated to the other web servers. For example, a failed update for one server could make the update fail for one or more site collections.

for a full setp guid from msdn on adding CU and updating with SharePoint Products Configuration Wizard then refer to this:


  • 1
    yup that is fine! yes you do have september 2014 CU installed and all uptodate! within ca you should see what cu is installed and when with its version
    – Ali Jafer
    Oct 15, 2014 at 14:38
  • 1
    did you run sharepoint Products Configuration Wizard after update? that is important to run
    – Ali Jafer
    Oct 16, 2014 at 10:21
  • 1
    i would update again! there is a new update for October and it should put you at 15.0.4659.1001 CU and then run Products Configuration Wizard after update
    – Ali Jafer
    Oct 16, 2014 at 10:25
  • 1
    just updated my answer
    – Ali Jafer
    Oct 16, 2014 at 11:07
  • 1
    no problem happy to help! its confusing untill you dig into the method in how its getting that value and what type of cu you have installed. Dont worry you have the latest CU installed!
    – Ali Jafer
    Oct 16, 2014 at 13:03

The Build version you mentioned in your question is for August 2014 CU.

But as you said you installed the Spetember 2014 CU then your version should be 15.0.4649.1000.

As you mentioned in the post, two things make sure( both are mandatory.

  • Install the September 2014 CU on all servers in the farm.
  • Run the Config wizard on all server in the farm. If you did not run the config wizard then SharePoint will show last build number.
  • Lastly run the Get-SPproduct -Local to update the config db.
  • but when i check the "Manage Patch Status" inside the system administrator,it mentioned that the 15.0.4649.1000 is already installed , , and i successfully run the Config wizard... but (get-spfarm).buildversion will shown 4641 instead of 4649.. can u advice please?
    – John John
    Oct 15, 2014 at 22:19
  • and i only have one SharePoint server. i do not want to be doing unnecessary steps. i am sure that September 2014 CU was part of the WU i did one month ago, also today i Run a windows update and it mentioned that i have SharePoint October 2014 CU (but i did not installed till now). and also inside the "Patch status" on my CA it mentioned that 4649 is installed ....
    – John John
    Oct 15, 2014 at 22:28
  • Did you try to download the spet 2014 current directly from site n try to install it?also make sure you download the server patch not foundation
    – Waqas Sarwar MVP
    Oct 15, 2014 at 22:42
  • but inside the "Central administration>>upgrade and migration>>check product and patch status" section, it mentioned that i have 15.0.4649.1000 installed,, so why i need to download it again? also the recommended approach to install SharePoint 2013 CU is using windows update tool, this is Microsoft instruction not mine...
    – John John
    Oct 15, 2014 at 23:04
  • I m not arguing on msft recommendation but as of now you have issue then why not try to to direct install...as per my little experience we never apply cu as part of WU....we always patch server separately n SharePoint separately in order to easy troubleshooting if any issue.
    – Waqas Sarwar MVP
    Oct 16, 2014 at 0:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.