Finding your Build Number
To find the build version of the SharePoint farm using Windows PowerShell:
1. Open the SharePoint Management Shell
2. Type the following command:
(Get-SPFarm).BuildVersion
Please read below for further explanation of each column:
To find the build version of the SharePoint farm using Windows PowerShell:
1. Open the SharePoint Management Shell
2. Type the following command:
(Get-SPFarm).BuildVersion
Build Number Table:
Please see the table below:
Schema Version | Build Number | Schema Change | LPs | Released Month | Compon ent | KB | Download Link | Issue Fixed |
16.0.4327.1000 | 16.0.4351.1000 | N/A | No | RTM | SP 16 | RTM | ||
16.0.4327.1000 | 16.0. 4366. 1000 | No | No | April 2016 CU | SP 16 | KB 2920721 | April 2016 CU | Link |
16.0.4378.1000 | 16.0.4378.1000 | Yes | No | May 2016 CU | SP & Proj 16 | KB 3115088 | May 2016 CU | Link |
16.0.4378.1000 | 16.0.4378.1000 | Yes | Yes | May 2016 CU | SP & Proj 16 | KB 2920690 | May 2016 Cu +LP | see above link |
16.0.4393.1000 | 16.0.4393.1000 | Yes | No | June 2016 CU | SP & Proj 16 | KB 3115181 | June 2016 CU | Link |
16.0.4393.1000 | 16.0.4393.1000 | Yes | Yes | June 2016 CU | SP & Proj 16 | KB 3115184 | June 2016 CU+LP | Link |
16.0.4405.1000 | 16.0.4405.1000 | Yes | No | July 2016 Cu | SP & Proj 16 | Kb 3115299 | July 2016 CU | |
16.0.4405.1000 | 16.0.4405.1000 | Yes | Yes | July 2016 Cu | SP & Proj 16 | Kb 3115304 | July 2016 CU +LP | |
16.0.4417.1000 | 16.0.4417.1000 | Yes | No | Aug 2016 CU | SP & Proj 16 | KB 3115437 | Aug 2016 CU | Link |
16.0.4417.1000 | 16.0.4417.1000 | Yes | Yes | Aug 2016 CU | Sp & Proj 16 | KB 3115441 | Aug 2016 CU & Lp | Link |
16.0.4432.1003 | Yes | Yes | Sep 2016 CU | SP & Proj 16 | Kb 3118295 | Sep 2016 CU +LP | ||
16.0.4432.1003 | Yes | No | Sep 2016 CU | SP & Proj 16 | Kb 3118289 | Sep 2016 CU | ||
16.0.4444.1004 | 16.0.4444.1000 | Yes | No | Oct 2016 CU | SP & Proj 16 | Kb 3118372 | Oct 2016 CU | |
16.0.4444.1000 | 16.0.4444.1000 | Yes | Yes | Oct 2016 CU | SP & Proj 16 | Kb 3118376 | Oct 2016 CU +LP | |
16.0.4456.1002 | 16.0.4456.1000 | Yes | No | Nov 2016 CU | SP & Proj 16 | Kb 3127940 | Nov 2016 CU | |
16.0.4456.1002 | 16.0.4456.1000 | Yes | Yes | Nov 2016 CU | SP & Proj 16 | Kb 3127942 | Nov 2016 CU +LP | |
16.0.4471.1000 | 16.0.4471.1000 | Yes | No | Dec 2016 CU | SP & Proj 16 | Kb 3128014 | Dec 2016 CU | |
16.0.4471.1000 | 16.0.4471.1000 | Yes | Yes | Dec 2016 CU | Sp & Proj 16 | Kb 3128017 | Dec 2016 CU + LP | |
16.0.4483.1001 | 16.0.4483.1001 | Yes | No | Jan 2017 CU | SP & Proj 16 | Kb 3141486 | Jan 2017 CU | |
16.0.4483.1001 | 16.0.4483.1001 | Yes | Yes | Jan 2017 CU | SP & Proj 16 | Kb 3141487 | Jan 2017 CU + LP | |
16.0.4498.1002 | 16.0.4498.1002 | Yes | No | Feb 2017 CU | SP & Proj 16 | Kb 3141515 | Feb 2017 CU | |
16.0.4498.1002 | 16.0.4498.1002 | Yes | Yes | Feb 2017 CU | SP & Proj 16 | Kb 3141517 | Feb 2017 CU + LP | |
16.0.4510.1001 | 16.0.4510.1001 | Yes | No | March 2017 CU | SP & Proj 16 | Kb 3178672 | March 2017 CU | |
16.0.4510.1001 | 16.0.4510.1001 | Yes | Yes | March 2017 CU | SP & Proj 16 | Kb 3178675 | March 2017 CU + LP | |
16.0.4522.1000 | 16.0.4522.1000 | Yes | No | April 2017 CU | SP & Proj 16 | Kb 3178718 | April 2017 CU | |
16.0.4522.1000 | 16.0.4522.1000 | Yes | Yes | April 2017 CU | SP & Proj 16 | Kb 3178721 | April 2017 CU + LP | |
16.0.4534.1000 | 16.0.4534.1000 | Yes | No | May 2017 CU | SP & Proj 16 | Kb 3191880 | May 2017 CU | |
16.0.4534.1000 | 16.0.4534.1000 | Yes | Yes | May 2017 CU | SP & Proj 16 | Kb 3191884 | May 2017 CU + LP | |
16.0.4549.1001 | 16.0.4549.1001 | Yes | No | June CU 2017 | SP & Proj 16 | KB 3203432 | June 2017 CU | |
16.0.4549.1000 | 16.0.4549.1000 | Yes | Yes | June CU 2017 | SP & Proj 16 | Kb 3203433 | June 2017 CU +LP | |
16.0.4561.1000 | 16.0.4561.1000 | Yes | No | July CU 2017 | SP & Proj 16 | Kb 3213544 | July 2017 CU | |
16.0.4561.1000 | 16.0.4561.1000 | Yes | Yes | July CU 2017 | SP & Proj 16 | Kb 3213543 | July 2017 CU & LP |
Please read below for further explanation of each column:
- Schema Version: This version number you will see from central admin (home page or going to Central admin > System Settings > Manager Server in Farm) or you can get the same from PowerShell as well: (Get-SPFarm).BuildVersion
- Build Number: Now onwards, MSFT is not changing the schema version with every CU as they change the practice so this number represents the patch level you are. You can get by going Central Admin > Upgrade and Migration > Check Product and patch Installation Status.
- Schema Change: This column will tell if Schema was changed or not for a specific CU
- LPs: This column will tell if they included the Language Pack fix or not.
- Release: This Column will tell the release month of the CU
- Component: What SharePoint or Project component this CU is for. Most probably it will be SharePoint 2016.
- KB: Link to MSFT KB Articles
- Download Link: Download link for the CU
- Issue Fixed: This will list all the issues fixed in this CU.