Project 2016 Public Updates (January 2017 to date)

This post has been republished via RSS; it originally appeared at: Project Support Blog articles.

This page lists all of the released Public Updates (PU) and Service Packs (SP) for Microsoft Project  2016, both Standard and Professional, and Project for Office 365.

From April 2016 the Office client updates are shipped 1st Tuesday.

Each of these packages is cumulative, including all the previous fixes back to the last baseline (either the initial release or a Service Pack).   I have noticed that in 2016 we don’t do a good job of displaying the version and 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 are running a click to run installation - such as Project Pro for Office 365 see http://support2.microsoft.com/gp/office-2013-365-update for details of the update schedules - but the version numbers and fixes should be roughly in line with the CU releases below.

 

March 2019

https://support.microsoft.com/en-us/help/4462198/march-5-2019-update-for-project-2016-kb4462198

Winproj Version 16.0.4822.1000

This update contains the following improvements and fixes:

  • Adds support for the new Venezuelan currency symbol in Project 2016.
  • When you synchronize projects from Project 2016 to a SharePoint site, Project crashes. The crash occurs when a given task predecessor or successor field has 255 characters.
  • If you try to change the actual work value on a summary task when protected actual work is enabled, Project 2016 may freeze or crash.
  • If you enter a timephased actual work value for a material resource that is assigned to a fixed duration task, the Work and Assignment Units on the assignment don't display correct values. For example, assume that resource units (work) equals 100 and you enter the timephased actual work value as 23.27. The Work and Assignment Units display 99.94 instead of staying at the expected value of 100.
  • When you open projects in Project 2016, you receive the following message:
    The operation cannot be completed because the source file contains invalid project data or the total number of rows would exceed the limit of 1,048,000 rows in a project. Validate the data in the source file, insert fewer rows, delete some rows, or consider dividing your project into subprojects to provide more space for tasks and resources.

February 2019

https://support.microsoft.com/en-us/help/4462134/february-5-2019-update-for-project-2016-kb4462134

Winproj Version - 16.0.4810.1000

This update fixes the following issues:

  • Assume that you open a project from a Project Server, that and you insert a project, and that during the insertion process, you deselect the Link to project option. Also assume that the project that you insert has custom fields. After you save, close and check in the master project, custom fields values that were previously associated with the inserted project may be missing.
  • Consider the following scenario:
    • You have a manually scheduled task where the duration is greater than zero.
    • The task is partially complete.
    • The Mark task as milestone property of the task is set.
    • You save the project in the XML format.
    • You open the XML version of the project.

In this case, the task displays a zero day duration and the task finish date equals the start date.

 

January 2019

https://support.microsoft.com/en-us/help/4461587/january-2-2019-update-for-project-2016-kb4461587

Winproj.exe version 16.0.4795.1000

Improvements and fixes

  • This update contains the following improvements and fixes:
    • After you edit and save a project, the values for some Enterprise Resource Custom fields on the project are lost.
    • Consider the following scenario:
      • You assign a resource to a task.
      • In the Task Usage view, you display the Actual Work and Actual Overtime Work fields.
      • On the assignment, you type 2.33h in the Actual Work field and type 3.33h in the Actual Overtime Work field.

When you compare the actual work on the task with the actual work on the assignment, the values are inconsistent. For example, the task shows 5.66h and the resource assignment shows 5.67h.

    • In some situations where your project is saved to Project Server and where user updates are protected, you may not be able to indent or outdent a task. Instead, you receive the following error message:

Change would modify work entered by a team member.  We can’t make that change because Project Web App is set to only allow actual work to be entered by team members through Timesheets or My Work.

    • When you edit resource properties on local resources while editing from a master project, changes are not saved successfully.
    • You can't create recurring daily exceptions whose periods are more than 1 day and the intervals overlap. As an example, you create a recurring exception that begins on the first day of the month, is scheduled every 28 days and ends after three months. If you try to create another recurring exception that begins the second day of the month, is scheduled every 28 days and ends after three months, the action is blocked.
    • In the Czech language, a corrected translation for Committed Work is made.

December 2018

https://support.microsoft.com/en-us/help/4461540/december42018updateforproject2016kb4461540

Winproj.exe version 16.0.4783.1000

Improvements and fixes

  • This update fixes the following issue:Consider the following scenario:
    • You make changes to a project.
    • You save the project.
    • You look at the progress indicator in the lower-right part of the screen to determine the progress.

In this situation, the indicator starts by saying that it is "Saving" the project. Then, it says that it is "Synchronizing data to server...". After this, however, the expected progress and final "Save completed successfully" details are not displayed

November 2018

https://support.microsoft.com/en-us/help/4461478/description-of-the-security-update-for-project-2016-november-13-2018

Winproj.exe version 16.0.4771.1000

Improvements and fixes

  • This security update contains improvements and fixes for the following nonsecurity issues:
    • When you save a project as an XML file, Project 2016 may crash. This issue can occur after you install the April 3, 2018, update for Project 2016 (KB 4018320).
    • When you make changes in a project and then save it, the custom field lookup table values are also saved even though they have not been changed. Therefore, it takes longer to publish the project. And while the publishing processes, other actions such as viewing the tasks view in Project Web App may be slow.
    • Assume that you update cost or work data for a subtask in Project 2016. When you save a baseline on the task and choose the option to roll up the baseline data to all summary tasks, the baseline data for task summary tasks within the sub project is rolled up but not to the inserted project summary tasks and summary tasks in the master project.

Consider the following scenario:

    • You have a SharePoint document library.
    • The document library list experience is set to the new "modern" experience.
    • The document library versioning settings require checkout.
    • You have a Project file stored in the library. You open the file from the library by  using Project 2016.

In this situation, you find that the expected "check out required" prompt isn't displayed, and therefore you can't respond. This means that if you make changes to the project and save, Project tells you that the changes can't be saved because checkout is required.

October 2018

https://support.microsoft.com/en-us/help/4461443/october-2-2018-update-for-project-2016-kb4461443

Winproj.exe version 16.0.4756.1000

Improvements and fixes

  • This update makes sure that the Japanese era name in Project 2016 is displayed correctly when a new era begins.

September 2018

No package

August 2018

https://support.microsoft.com/en-us/help/4032238/august-7-2018-update-for-project-2016-kb4032238

Winproj.exe version 16.0.4732.1000

Improvements and fixes

  • Assume that you open a project from Project Server. You change a local custom field's lookup table, then you save, close and reopen the project. In this case, values from the lookup table that were previously entered for various tasks may be lost even though the values aren't deleted from the lookup table. Additionally, some parts of the lookup table definition may be missing.

July 2018

https://support.microsoft.com/en-us/help/4022217/july-3-2018-update-for-project-2016-kb4022217

Winproj.exe version 16.0.4717.1000

Improvements and fixes

  • Assume that you apply a different view (such as the Gantt Chart view) to a project that has the Network Diagram view applied. When you apply the Network Diagram view again to the project, the nodes are lost and the dependency lines are drawn to random places. In some cases, Project may crash.
  • The actual work values of a task and the assigned resource are inconsistent. For example, the task shows actual work as 5.66 hours and the assignments shows actual work as 5.67 hours.
  • Task EAC value is not calculated as expected for a project in Project 2016. For example, when you compare the EAC field in a project that's opened in Project 2010, there is a value difference of anywhere from a few cents to several thousand dollars (assuming the dollar currency).
  • When you select the Open button from the Project Web App resource center without any resource selected, you see the message "To perform this action, you need to have Project Professional 2016 installed." In this case, if you dismiss the message, you cannot edit enterprise resources.
  • If you use a 32-bit version of Project and you use the Update Project function to reschedule uncompleted work, you may not see an expected Planning Wizard page that tells you that Project did not reschedule certain unscheduled tasks because of a constraint that's applied to them.
  • The actual finish date that you enter is ignored for a task if the task has a Finish No Earlier Than (FNET) constraint and the actual finish date is earlier than the FNET constraint.

June 2018

https://support.microsoft.com/en-us/help/4022164/june-5-2018-update-for-project-2016-kb4022164

Winproj.exe version 16.0.4705.1000

Improvements and fixes

  • Consider the following scenario:
    • You create a project template that has a task and resource assigned to it where the Assignment Units value is set to 0%.
    • You create a project in Project Web App in which the template is associated with the selected enterprise project type.

In this situation, the assignment on the task shows the Assignment Units value as 100% instead of 0%.

  • When you insert a project into a master project and clear the link to project check box, you may receive the following error message:

These tasks can't be linked because they're already linked through another task chain.

After the insertion process is complete, for a given task, it displays the same predecessor or successor for two times.

  • If you save a project that's created by Project 2002 or Project 2003 to a project server, the MSP_TASK_CUSTOM_FIELD_VALUES_SHADOW database table grows large.
  • Assume that you have a task that has a cost resource assigned and there is no work or material resource. When you split the task, the remaining cost is lost.
  • When a Project based COM add-in executes the FileSave method, Project 2016 may crash.
  • When you try to open an enterprise calendar while it is connected to a Project Web App instance by using Google Chrome, you receive the following error message:

Sorry, we were unable to open your project. Please try again. If this happens again, contact your administrator.

  • Assume that you add a resource to your project where the default booking type for the enterprise resource is set to Proposed. When you change the booking type of the resource in the project to Committed, and then save, close and reopen the plan again, the booking type is reverted to Proposed.
  • When you delete a Gantt chart type view that has a drawing in Project 2016, Project 2016 may crash. Related to this, when you delete a drawing in a Gantt view, you may see the drawing is deleted from another view.

May 2018

https://support.microsoft.com/en-us/help/4018373/may-1-2018-update-for-project-2016-kb4018373

Winproj.exe version 16.0.4690.1000

Improvements and fixes

  • When you try to perform an action, for example, applying a font or a background format to a cell, Project may crash.
  • Consider the following scenario:
    • You create a fixed duration task that is 100% complete.
    • You create a custom calendar and add a one-day exception in the range of task duration.
    • You change the task calendar to the custom calendar, and then you see that the duration reduces by one day.
    • You save and then close the project.
    • You reopen and recalculate the project, and then check the finish date.

In this situation, the actual finish date is shifted to one day later.

  • When projects are opened from a server, resources names aren't always seen. In addition, when you use the Build Team dialog box, you see the same thing where some resources don't have names. After you apply this update, the Resource Names are visible to the user.
  • Consider the following scenario:
    • You create a local project with some tasks and save it as a file.
    • You create a second project, you have the first project share resources from it and you save it as a local file.
    • You assign the resource to the tasks.
    • You save the projects.
    • You upload the project file and shared resource file to a SharePoint Online document library.
    • You open the project file from the document library, and you receive the message:

This file shares resources from a resource pool

    • After you select OK, the shared resource file is also opened.
    • You add a new task to the project file and assign it to a resource.
    • You save the project file and close both files.

In this situation, when you reopen the project file, the link to the shared resource file is lost.

  • Consider the following scenario:
    • As a team member, you open your timesheet and enter work for two adjacent days.
    • On the first day, you set the actual work value back to zero.
    • On the first day, you set 8 hours of non-working time on an administrator task (for example, vacation).
    • You send a status update for approval.
    • You open the previous week timesheet.
    • You enter actual work values.
    • You send the timesheet for approval and the status manager approves it.

In this case, the actual work that's entered on the second day of the two days moves to the first day. The actual work should not move when the status update is applied to the project.

April 2018

https://support.microsoft.com/en-us/help/4018320/april-3-2018-update-for-project-2016-kb4018320

Winproj.exe version 16.0.4678.1000

Improvements and fixes

  • When a task custom field formula is applied, and it also uses the formula for summary and grouping rows, the summary row displays "#ERROR". In addition, the grouping row displays incorrect values.
  • The Change Working Time dialog box enables you to select a date and to see the working shifts for that day listed in the Working times section. For example, a date shows working shifts of 8:00 AM to 12:00 PM and 1:00 PM to 5:00 PM. In some cases, you may be unable to see all the defined shifts for the given date because it's hidden behind the text that tells you the date's base calendar.
  • You open a project from the Project Center while using the Google Chrome browser. Then you see the following error message:

Sorry, we were unable to open your project. Please try again. If this happens again, contact your administrator.

  • Consider the following scenario:
    • You have a project plan that has many tasks with long durations.
    • You may have some baselines established.
    • You save the project plan to an XML file.
    • You open the XML file.

In this case, if you use the 32-bit version of Project, it may crash. If you use the 64-bit version of Project, you notice that it takes a long time to open the file and Project uses many gigabytes of memory. When you look at the size of the XML file, you'll also notice that it is hundreds of megabytes in size.

Note To fix this issue, you also have to set the value of the registry key XmlDisableTimephasedSplitByDay to 1. See Registry information for more information.

  • This update also contains the following improvement:
    • When you save a project to the XML format, the following pieces of new information are exported:
      • The build number of Project that created the XML file.
      • Project, task, resource and assignment GUIDs.
      • Names of views.
      • Names of tables.
      • Names of filters.
      • Names of groups.
      • Names of data import and export maps.
      • Names of reports.
      • Names of drawings.

Project exports these pieces of information but does not read them when you open or merge an XML file. Therefore, you can't, for example, add or change view names within an XML file, and have Project read and understood the information.

Note If you do not want your XML files to have this new information, you can set the following registry key:

      • Location: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\MS Project\Options\Save\
      • Type: DWORD
      • Name: SimpleXmlexport
      • Value: 1

March 2018

https://support.microsoft.com/en-us/help/4011734/march-6-2018-update-for-project-2016-kb4011734

Winproj.exe version 16.0.4666.1000

Improvements and fixes

  • If your project has manually scheduled tasks, and server notifications and reminders are turned on, you may receive unnecessary modified task notifications.
  • After actual work from a status update is applied to a task, the work values may not appear in Project as expected. For example, you report 4 hours on a day, but when you open the project, you don't see the time-phased actual work value. This issue may occur when you assign a new resource to a task that is completed.
  • When the Status field is referenced in a task custom field formula, other calculations may go slowly. For example, when you enter time-phased work data, it takes several seconds before you take back control.
  • When you add a resource to a project, the Booking Type field of the resource is ignored. For example, if the default booking type for the resource is set to "Proposed", when you add the resource to your project, the booking type is displayed as "Committed".
  • When you manipulate Views and other elements within the ProjectBeforeSaveBaseline event code in Project VBA, Project may crash after you save a baseline.
  • When you open and edit a project, then save back to Project Server 2016, you may see an error message that has some of the following elements in it:

ActiveCacheQueuedMessageExecutionError

error="System.InvalidCastException: Specified cast is not valid”

  • When you open an XML file that has time-phased baseline data in Project 2016, the time-phased data on assignments may be incorrect. For example, the time-phased work hours that you entered are 2, 2, 2, 2. However, they are displayed as 2, 0, 0.58, 1.42, 0. The totals stay the same.
  • When a task custom field formula is applied and it also uses the formula for summary and group rows, the summary row displays “#ERROR”.  In addition, the grouping row displays incorrect values.
  • Consider the following scenario:
    • You save a baseline in your project, and then you save the project.
    • You save another baseline and you save the project, close it, and check it in.
    • You query the database and view the MOD_DATE property for the given baselines.
    • Another user opens the project and saves a different baseline.
    • You query the database and check the MOD_DATE property for the three baselines.

In this situation, you find that the values of the MOD_DATE property for the baselines are the same. They should be different and reflect the date and time when you saved the baselines.

February 2018

https://support.microsoft.com/en-us/help/4011672/february-6-2018-update-for-project-2016-kb4011672

Winproj.exe version 16.0.4654.1000

Improvements and fixes

  • You cannot assign a cost value to a cost resource through the Assign Resource dialog box if the Windows regional setting is set to Norwegian. Instead, you see the following error message:

This field only supports numbers.

If you’ve only typed numbers, try entering a smaller number with up to two decimal places.

Consider the following scenario:

    • You are using the German version of Project 2016.
    • You set the date format to use Weeks. For example, “3/W05".
    • You create an automatically scheduled task.
    • You modify either the Start or Finish field to change the date.

In this scenario, you receive the following error message:

The date you entered isn't supported for this field. Dates must be between January 1, 1984, through December 31, 2149.

Enter the date in the correct format, eg., 15/06/00 or 15 June 2000

Consider the following scenario:

    • You have a Project Web App site and Project Professional 2016 in your organization.
    • You create some custom project fields and add them to your project detail pages (PDPs).
    • In Project Web App, you create a new project and add values to these custom fields.
    • You open the project in Project Professional 2016, make a change and then save the project.
    • You open the project in Project Web App and view the custom field values on the PDPs.

In this situation, the values for these custom fields may be lost.

Consider the following scenario:

    • You have a task that has a resource assigned.
    • The task has a split in it. For example, there's a week of work, a week where no work exists and then a final week that has work.
    • In the timesheet for this task, you enter hours on the task so that the work is completed up to the date where the split begins.
    • The timesheet is submitted and then the status update is approved.
    • After that, the project is opened in Project Web App and the task finish date is adjusted to a date that's after where the actual work is completed. For example, the actual finish date is set to the middle of the week where there's no work.

In this situation, the actual work is spread over the whole duration.

January 2018

https://support.microsoft.com/en-us/help/4011633/january-2-2018-update-for-project-2016-kb4011633

Winproj.exe version 16.0.4639.1000

Improvements and fixes

  • The grouping rows that are applied to Gantt views in projects may not display values for given fields that have formula calculations.
  • Consider the following scenario:
    • You have two projects.
    • You assign two tasks from the two projects to a same resource.
    • You use the Capacity Planning tool to check the two projects, and you see that a red over allocation icon shows in the indication column.
    • You change the duration to a longer period.

In this scenario, the over allocation icon in the indication column stops working.

  • When you operate on a project in Project 2016, you receive the following error message:

This operation cannot be completed because the source file contains invalid project data or the total number of rows would exceed the limit of 1,048,000 rows in a project. Validate the data in the source file, insert fewer rows, delete some rows, or consider dividing your project into subprojects to provide more space for tasks and resources.

This issue occurs if the assignment maximum unique ID of 1048576 is exceeded.

  • The progress point shape (the point on the progress bar) for some tasks may not be drawn at an expected position in Project 2016.

December 2017

https://support.microsoft.com/en-us/help/4011573/december-5-2017-update-for-project-2016-kb4011573

Winproj.exe version 16.0.4627.1000

Improvements and fixes

  • In the Chinese version, Project 2016 crashes when you open the Change Work Time dialog and scroll the calendar to date between 1995 and 2011.
  • When system events such as Group Policy updates are applied, Project 2016 may flicker.
  • When visual reports are generated from the context of a master project, the results are inconsistent and may fail completely in certain cases. For example, if you select the Earned Value Over Time Report chart, you may find that not all the costs from the sub projects are included in the pivot chart, and you may receive the following error message when you create a visual report:An unknown error has occurred. An error occurred and the requested action could not be completed at this time.
  • Consider the following scenario:
    • You open a project from Project Server.
    • You save the project by using the Save for Sharing functionality.
    • You delete data from the project. For example, you delete an assignment on a task.
    • You save the project back to the server.

In this situation, you may find that there is still data for the deleted element in reporting database. For instance, you still see actual work in the project.

November 2017

https://support.microsoft.com/en-us/help/4011227/november-7-2017-update-for-project-2016-kb4011227

Winproj.exe version 16.0.4615.1000

Improvements and fixes

  • When you save changes to a master project that's stored in a SharePoint document library, subprojects switch to read-only mode and aren't saved accordingly.
  • If you have Task Path feature enabled, Project 2016 may freeze when you select a task within your project.
  • After you set a timescale label to None in a timescaled view such as the Gantt chart, all labels for other timescale tiers disappear, and the label for the tier that you have selected to hide does not disappear.
  • Consider the following scenario:
    • You have a task in Project 2016 that is set to fixed duration and is effort-driven.
    • You have a resource assigned to the task.
    • Within a Task Form type view, you assign an additional resource to the task and specify the units for the resource to any value other than 100 percent.

In this scenario, the unit setting for the additional resource is 100 percent, and the name disappears.

  • Consider the following scenario:
    • You save a baseline in your project.
    • You query the database and check the MOD_DATE property for the given baseline.
    • You open the project and save a different baseline.
    • You query the database and check the MOD_DATE property for the two baselines.

In this scenario, you find that the values of the MOD_DATE property for the two baselines are the same. They should be different and reflect the dates on which you save the baselines.

October 2017

https://support.microsoft.com/en-us/help/4011141/october-3-2017-update-for-project-2016-kb4011141

Winproj.exe version 16.0.4600.1000

Improvements and fixes

  • Consider the following scenario:
    • You decide to edit a project in Project Web App or Project 2016.
    • You enter time-phased Actual or Actual Overtime work on an assignment and notice that it's no longer scheduled the way that you expect it should be.
    • You adjust the assignment start dates and finish dates to reflect the schedule that you have expected.

In this situation, additional actual work that you don't enter may be applied to the assignment unexpectedly.

  • Assume that you have a Project Server 2016 and Project Professional 2016, when you save a project that's connected to the Project Server, you may receive the following error message:

Change would modify work entered by a team member

We can't make that change because Project Web App is set to only allow actual work to be entered by team members through Timesheets or My Work.

This issue occurs after the July 5, 2017, update for Project 2016 (KB3203476) is installed.

September 2017

https://support.microsoft.com/en-us/help/4011101/september-5-2017-update-for-project-2016-kb4011101

Winproj.exe version 16.0.4588.1000

Improvements and fixes

  • When you open certain XML files, Project 2016 may crash. Additionally, in some cases, the durations of tasks may differ from those in the earlier versions of Microsoft Project.

August 2017

https://support.microsoft.com/en-us/help/4011034/august-1-2017-update-for-project-2016-kb4011034

Winproj.exe version 16.0.4573.1000

Improvements and fixes

  • Changes the word Level to the word Equalize in resource leveling scenarios for the Danish version of Project 2016.
  • This update fixes the following issues:
    • When you use the Save Baseline feature to copy a baseline from one to another (for example, from baseline 1 to baseline 5), the time phased cost and work values for budget resources are not copied.
    • The Status value may be incorrect at the summary task level. For example, a summary task's status is displayed as Late even though all of its subtasks are calculated as Complete, Future Task, or On Schedule.

 

July 2017

https://support.microsoft.com/en-us/help/3203476/july-5-2017-update-for-project-2016-kb3203476

Winproj.exe version 16.0.4561.1000

Improvements and fixes

Assume that you create a SharePoint Tasks List in Project Online. After you change the indent of the tasks in Project 2016 and synchronize the tasks with SharePoint, the indent setting isn't synchronized correctly.

  • If the task finish date is changed in the schedule web part, the actual work is spread unexpectedly.
  • After you replace a local resource with an enterprise resource, the actual work is transferred to the enterprise resource even though it's a protected work.
  • When you select a task in the Task Name column in Project 2016, Project 2016 crashes if the first column that's locked of the table is Task Name, and one or more tasks are indented.
  • After you import task, resource, and assignment information from an Excel worksheet in Project 2016, the work value is ignored.
  • When you open an XML file that has comma decimal characters for numeric values in Project 2016, the numeric values is lost because the numeric values are read incorrectly if Project 2016 uses dot decimal characters.
  • Cost precision is lost after you copy and paste a task in a project. For example, if the cost on the source task is $76.85, it will become $76.65 on the pasted task.

 

June 2017

https://support.microsoft.com/en-us/help/3191934/june-6-2017-update-for-project-2016-kb3191934

Winproj.exe version 16.0.4549.1000

Improvements and fixes

  • Improves the translation of Project 2016 in multiple languages.
  • Pasting into the Resource Namesfield within the Task Usage view allows you to paste the same resource name more than once. This creates a duplicate and causes problems when you apply status updates from Project Server.
  • Improves translation for the French version of Project 2016.
  • This update fixes the following issues:
    • Consider the following:
      • A project manager publishes a task to a team member.
      • The team member in either a timesheet or in tasks within Project Web App reports work that's earlier than what was scheduled. For example, 8h of work was scheduled on Wednesday but 8h of actual work was reported and submitted for Monday.
      • The status manager approves the update.
      • The team member zeros out the actual work and moves it to a later date.
      • The status manager approves the update.
      • The project is opened in Project Server.

In this situation, the task's actual start date still reflects the set with the earlier update instead of the new update where the actual start date is later.

  • When you open a project from Project Server, you incorrectly see the following error message:

This project cannot be opened in read-write mode because a previous project checkin for this project is not complete.

  • Assume that you open a project in Project Professional 2016, and you are prompted to apply status updates. If you select to apply status updates, the process never finishes, and the project remains in a temporarily unusable state.
  • When you open an XML file that has timephased baseline data in Project 2016, the timephased data appears incorrectly. For example, on Saturday, the timephased baseline work should appear as 0.9h, but it instead appears as 0.88h.

May 2017

https://support.microsoft.com/en-us/help/3191870/may-2-2017-update-for-project-2016-kb3191870

Winproj.exe version 16.0.4534.1000

This update fixes the following issues:

  • After you change the Physical % Complete value on a subtask, the value is not calculated as expected on the related summary task.
  • When you open a project from a SharePoint list, Project 2016 may crash as the synchronization process begins.
  • When you print review project data, you may find the text that is wrapping in a cell appears differently than it does in the view. For example, text may be missing or the location where the text breaks from one line to the next is different.
  • If a cost and a work resource are assigned to the same task, you may not be able to change the task's status manager.

April 2017

https://support.microsoft.com/help/3178708

WinProj.exe version 16.0.4522.1000

This update includes the following improvements and fixes:

  •  
    • In some circumstances, leveling on a week-by-week basis pushes tasks to the end of time (12/31/2149). Meanwhile, the leveling operation takes a long time to complete, and Project 2016 is unresponsive during that time.
    • After you upgrade from Project 2013 to Project 2016, manually scheduled tasks are not updated correctly. For example, you create a project that has a manually scheduled task by using Project 2013 and open it from your server by using Project 2016. Then you update the task's duration and save the project. However, the change does not appear in PWA or when it's opened again in Project 2013.
    • The Links Between Project dialog box incorrectly displays "File Not Found" in the Differences column for projects that exist and are available on your Project Server.
    • Consider the following scenario:

In this situation, the given feature pane isn't displayed as expected.

  • When you use the Copy Timeline function in Project 2016, the timescale doesn't align correctly with where the bars are scheduled and shown. For example, you have a task that begins January 23, 2017. However, the timescale marker that shows January 21, 2017 appears later than the start of the task.
  • Removing the start date from a resource assignment may cause the start date of the task to reschedule to "as soon as possible", and this may cause huge leading splits on the assignment.
  • When you open the Build Team dialog box in Project 2016 and enable the Online status next to name display option, Project may crash.
  • When you assign a task to a resource with a max units 0, the assignment units is unexpectedly assigned as 100%.
  • When you edit an assignment finish date from a Task From type view, Project 2016 may crash.
  • When you open a project file from a SharePoint site through the Recent menu in Project 2016, the file is opened with read/write permission, and you are not prompted to check out the project even though the Require documents to be checked out before they can be edited? SharePoint option is enabled.

March 2017

https://support.microsoft.com/help/3178669

WinProj.exe version 16.0.4510.1000

This update fixes the following issues:

  • The Visual Basic Applications ScreenUpdating property does not work as expected in Project 2016. Instead of freezing the screen content when the code runs, the screen continues to update. This produces screen flicker and causes the code to run slower.
  • Assume that a project manager opens a project in Project 2016 that has been successfully used with Project 2013. In this situation, when actual work values are observed in the Task Usage view, it is found that, for some resources, the actual work has been moved from the dates on which it was entered.
  • In the Progress Lines dialog box, you select to display progress lines in relation to the baseline plan instead of the default actual plan. In this situation, the progress line does not draw as expected.
  • When you open an .xml file within the Import Wizard and select the As a new project option, Project 2016 may crash.
  • Assume that you open a project plan, and transfer local resource custom field lookup table values to an enterprise resource enterprise field. Then you save the project plan to a Project server. In this situation, some custom enterprise resource lookup table values may be lost.
  • In some cases, enterprise custom field data may be lost from a project after a status update has been applied, and the project is then opened in Project Professional 2016.

February 2017

https://support.microsoft.com/help/3141514

Winproj.exe version 16.0.4498.1002

This update fixes the following issues:

  •  
    • When you open a project that has a milestone task, an actual start date may be added unexpectedly even though it did not have a date the last time it was saved.
    • A task's % Complete value is also updated unexpectedly after you update the % Work Complete value.
    • The Cost Performance Index (CPI) value on a summary task may incorrectly display a value that's similar to -99999999999999.
    • When you print a project view such as the Gantt chart one by one page in Project 2016, you may find that the row heights are taller than expected, that column widths are narrower than expected, and that font sizes are smaller than expected.
    • When you open a project and save it, the project ownership may unexpectedly change to you.
    • Consider the following scenario:
      • You are a user who edits projects in Project Professional or Project Web app.
      • You have been denied the Save Protected Baseline permission.
      • You open a project from Project Server.
      • You copy and paste a task to another location in the project.

In this situation, the protected baseline (baseline 0 – baseline 5) data is pasted. Because you don't have permissions to create baseline data, the paste process should not replicate this detail from the copied task and its assignments.

January 2017

https://support.microsoft.com/en-us/kb/3141459

Winproj.exe version - 16.0.4483.1000

Fixes the following issues:

  • Assume that you create and apply a grouping in a sheet type of view such as the Gantt Chart view in Project 2016. When you print the project, the horizontal bands appear. However, the vertical parts that tie together the top and bottom of the band don't appear.
  • In Project Professional, you can now add the Locked field to a task view to facilitate closing tasks to update.In Microsoft Project Server, team members have project tasks assigned to them and they report their status (the work that they have performed) on these tasks. In some cases, a project manager may want to close these tasks to update so that team members are prevented from submitting status but still have visibility to the tasks.To achieve this, previously the project manager had to edit the project in Project Web App and set the Locked field on the given tasks in the project. Now, in order to lock or close tasks to update, the project manager can open their project in Project Professional and insert the Locked field into a task view where they can set the value to Yes or No as appropriate.
  • The Last Modified date in the Project Professional Open dialog box does not reflect the current time zone. For example, your time zone is Pacific Time (UTC-08:00) and the Last Modified date shows 09:15 instead of the expected 01:15.
  • Assume that you save a project that has timephased baseline data to the XML format. When you open the XML file, the timephased baseline data is incorrect.
  • When you save a baseline for a selected task, the task or assignment baseline values may be incorrectly rolled-up to and displayed on the related resources.
  • When you apply status updates in PWA, actual work is added to some assignments unexpectedly. For example, suppose that you have an assignment that has 35 hours total work and the status update is to apply 9 hours. When you view the results in Project Professional, you find that the assignment is unexpectedly completed. Meanwhile, the total work and the actual work have increased to 400 hours.
  • When you open a project from a SharePoint document library through a direct URL, the project is opened as checked-out even though the Require documents to be checked out before they can be edited? setting is enabled.

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.