First published on TECHNET on Oct 16, 2017
Last week the Public Update (PU) for Project Server 2013 and 2016 were released for October 2017 . Client updates were released on October 3rd; server updates on October 10th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.
We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).
A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information:
. We may have a future blog with additional information about Click-to-Run update channels and methods.
Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.
We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.
The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See
too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.
Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).
Project and Project Server 2016
An overview of all the Office 2016 releases for October 2017 can be found here -
- October 2017, updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (but this month, as usual, the single patch comes in two parts... a wssloc and sts2016 part). - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though).
parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.
Description of the security update for SharePoint Server 2016: October 10, 2017-
Includes Project fixes, like the roll-up patch in Project Server 2013.
There is a database schema update this month - it changes to 16.0.4600.1001. Remember, Project Server 2016 data is in the content database. The version number 16.0.4600.1001 can be used to control the connecting client to the October 2017 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
October 3, 2017, update for Project 2016 (KB4011141)
The version of Project Professional 2016 will be updated to 16.0.4600.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)
If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at
for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.
and Project Server 2013
An overview of all the Office 2013 releases for October 2017 can be found here -
- October 2017, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server October PUs from the following articles:
Project Server 2013 Server Rollup Package
October 10, 2017, cumulative update for Project Server 2013 (KB4011175)
There is a database schema update this month - and the dbo.Versions table should show 15.0.4971.1001 *** Update 11/28/2017 - 15.0.4951.1000 apologies for any confusion – the Content DB version had been reported initially *** after applying the October 2017 PU. The version number 15.0.4951.1000 can be used to control the connecting client to the October 2017 PU level.
Project Professional Versions (Project Server 2013 settings)
The client version number will be 15.0.4971.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4971.1000 value to control connection of the October 2017 PU patched client.
If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See
for more details. As mentioned above - the version number entered no longer controls the server side scheduling engine - so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.