Project 2016 Updates (RTM to December 2016)

[Brian-Smith]

December 2016

December 6, 2016, update for Project 2016 (KB3127994)

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

WinProj.exe version: 16.0.4471.1000

Fixes the following issues:

• Updates the translation of the check in confirm dialog box in Ukrainian when you close a changed project.
• Fixes the following issues:
• When you view a custom field lookup table within the Project Information dialog box, you may find that some expected values don't appear.
• When you open and save a Project 2003 project to a server, resource enterprise custom field values may be lost.
• Consider the following scenario:
• In a project, you go to the Resource Sheet view where you have resources defined.
• You insert one of the local Outline Code fields.
• From the outline code field on a resource or on resources, you select a value from the values that you have defined.
• You save the project to Project Server.
• Later, you set the outline code values to something else.
• You save, close and reopen the project.

In this situation, the new values that you set into the outline code field on the resources are lost.

• After you save a baseline, timephased work and cost values aren't displayed as expected. For example, you may see work and cost during periods where no work or cost exists.
• When you open certain XML files in Project, assignment delay is ignored. Therefore, the start and finish of some assignments on a task may be different. This can also cause the given task to schedule differently.
• In a master project, when you view the finish date of an inserted project summary task (this is the task that represents a subproject), you may find that it doesn't reflect the latest finish date of the tasks in the subproject.

To fix the following issue, install December 6, 2016, update for Office 2016 (KB3115278).

Consider the following scenario:

• You create a new report. For example, you create a new report that's based on the default Project Overview report.
• In a field list, you add more than one level of sorting.
• You save your project.
• You open your project.

In this situation, all the elements on the report are lost and all that you see is a blank screen.

November 2016

November 1, 2016, update for Project 2016 (KB3127960)

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

WinProj.exe version: 16.0.4456.1003

Fixes the following issues:

• In some cases, you can't open a saved project that you worked with previously. Instead, you may see the file open progress indicator appears as if the project is opening, but the project doesn't open.
• Assume that you start Project Professional and connect to a server, and that you have selected to load summary resource assignments. In this situation, when you go to a resource usage view, a given resource that should be shown as overallocated appears to be underallocated during a certain period, for example, daily.
• When you open certain XML files, the start date of some assignments may be ignored, which means tasks are scheduled incorrectly. You may also notice that the assignment on a task has an actual start date yet the task doesn't.
• When you level a project on a week-by-week basis, Project may freeze. After the leveling is complete, you may find that the tasks are scheduled out to the end of time, which is December 31, 2149.
• When you use the JavaScript Office API against Project 2016, querying task start dates and finish dates always returns the automatically scheduled start dates and finish dates instead of the manually scheduled start dates and finish dates.
• When you open a project from a SharePoint site and then click the Edit Project button from the banner, you may see an error message that resembles the following:

You have made changes to '<project name>'.
Another user has also made changes. What would you like to do?
Click Discard to discard your changes and edit the latest version.
Click Save as to save your changes to a different file and open the latest version.

This issue occurs with projects that were stored in Project Server.

• After you save and publish a project plan, upon close and check it in, you receive the following error message:

The following job failed to complete.
Job Type: Checking
Error ID: 9000(0x2328)
Could not checkin project. Please contact your system administrator to force checkin this project.

• When you open an XML file, resource assignments may have trailing zero work values in a usage view. For example, the work contour may resemble the following:

8h, 8h, 2h, 4h, 0h, 0h, 0h

It should appear as the following:

8h, 8h, 2h, 4h

• Consider the following scenario:
• You have a master project.
• You have several sub projects in the master project.
• The sub projects are set to read-only.
• You open the master project.
• You select the Edit Project button from the banner.

In this situation, the sub projects are opened with the read/write permission even though they are set to read-only.

• Assume that you change the name of an enterprise calendar. When you open projects that use that calendar, Project 2016 may crash.
• Assume that have a task that has a duration of four elapsed months or longer. When you save the task to the XML file format, Project 2016 freezes.
• When you open certain XML files, you receive the following error message:

The actual finish date is before some of the previously entered timephased actual work values. If you continue with this operation, Project will truncate some of the previously entered timephased actual work values.

Additionally, when you open some XML files, you may find that the Gantt bars for fixed or elapsed duration tasks show an unexpected trailing split.

• If an inserted subproject has a task that is 100% complete and has an ALAP constraint, the summary tasks within the subproject may have an incorrectly calculated start, finish, and duration.
• Assume that a project contains a local resource whose name is the same as an enterprise resource, and the local resource is assigned to an incomplete task and a task that is 100% complete. When you save the project on a server, the local resource is assigned to the completed task, and the enterprise resource is assigned to the incomplete task.

October 2016

October 11, 2016, update for Project 2016 (KB3118342)

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

16.0.4432.1003

Fixes the following issues:

• When you open projects from an XML file and some tasks in the file are defined as manually scheduled, the duration of these tasks may change to the default of 1d instead of the value that's defined in the file.
• If a task is updated to be 100% complete and the cost resource for the task is more than $83.33, the duration is reset unexpectedly.
• Consider the following scenario:
• You have an enterprise calendar.
• You set the enterprise calendar as the base calendar for some projects in the project server.
• In preparation to delete the enterprise calendar, you go to the projects that are using the calendar and select a different calendar for them.
• In Project Web App settings, you go to the Enterprise Calendars page and try to delete the calendar.

In this situation, you can't delete the calendar because you are told that it is in use. After you install this update, you can now go to the projects in which the calendar is used, and use the organizer to delete it. After the calendar is deleted from the individual project that uses it, you will then be able to go to PWA and delete the calendar.

• Consider the following scenario:
• You have a master project in which you have at least one sub project.
• The master and sub projects have been saved to Project Server.
• You unlink the sub project from the master project.
• You save the sub project back to Project Server.

In this situation, the assignments in the sub project are lost.

• Consider the following scenario:
• You have a task in a project that has a resource assigned.
• The resource assignment has 80h of work.
• The resource assignment has split work wherein it works the first week, and it has a zero work split for the second week and finally has work on the last week.
• The assignment is 50% complete and the first week is completed.

On the Task Usage view, the actual work details of the assignment resembles the following:

8h, 8h, 8h, 8h, 8h, 0h, 0h, 0h, 0h, 0h

You view the stop date and also notice that it's the same as the resume date. After you install the update, the trailing zero actual work values no longer appear and the stop date corresponds to where the last timephased actual work value that's more than zero is ended, and it's not the resume date which starts at the beginning of the third week.

• When you publish a project from Project 2016 to PWA, resource enterprise custom field values may be lost.
• When you publish a project to Project Server, formulas associated with a custom field that use the Current Date function will display the correct values. However, the published data for the same field may display a different value. For example, you have a custom task field with a formula that displays the current date. Then, you publish a project and you see the expected values on tasks in the custom field in PWA. Two days later, you open the same project in Project 2016, you see the correct values and publish the project. However, when you see the published values within the custom field in PWA, you see the same value from two days earlier.
• When status updates are applied, trailing time phased actual work values are created. This causes finish dates are later than expected.

September 2016

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

16.0.4432.1000 (Remember - you need to look at winproj.exe, we don't show the specific Project version under File, Account - just the MSO version).

• Assume that you create an .mpp file in a SharePoint document library and then synchronize the library to the local computer by using OneDrive, and the file path is longer than 130 characters. In this situation, the .mpp file can’t be opened in Project 2016.
• Assume that you create a project from a template in Project Web App. When you try to enter timephased cost date or actual cost date for a cost resource in Project 2016, the values that you enter can't be applied, and Project 2016 may crash.
• When you merge or append a tab-delimited text document into an existing project, merged changes can't be saved in Project 2016.

August 2016

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

16.0.4417.1000

• Translates some terms in multiple languages to make sure that the meaning is accurate.
• When you try to import and merge an XML format into an existing project, and the XML project has tasks that have dependencies among them, Project 2016 may crash.
• Consider the following scenario:
• You have at least two projects and the projects have task-level cross project dependencies.
• The projects are included in a master project.
• The master project is open and you are looking at the Gantt view.
• In this situation, you experience the following issues:
• The dependency lines between the tasks in the inserted projects aren't displayed.
• Dragging and dropping to create links between tasks that are in a sub-project or across sub-projects doesn't create a link as expected.
• The Link the selected tasks and Unlink tasks buttons in the schedule grouping of the Task ribbon don't function on cross project tasks.
• When you try to edit or create a new Network Diagram data template, you receive the following error message:

The field "<Unavailable>" does not exist. Click a field name in the list, and then press Enter.

• When you work in a usage view within the context of a master, Project 2016 may crash. This issue may occur when you level resources or delete tasks.
• Assume that you have a Project .MPP file that's stored in a SharePoint document library. When you click the file name, the project opens but you don't see a banner that offers you the ability to edit or check out the project. Instead, the project may keep in a read-only state and you can't save or check in changes.
• When you set the date of a task to a value that's greater than the year 2099 in Project 2016, the date is displayed incorrectly in the date picker control. For example, if you have tasks that are scheduled on May 12, 2110, the year is displayed as 2010 in the date picker.
• In the printout or print preview of a Gantt chart in Project 2016, the Resource Names column displays the same information as the Predecessors column. This issue occurs if you set Windows Regional Settings to a right-to-left language.

July 2016

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

16.0.4405.1000

Fixes the following issues:

• When you open and then save a project file to a Project server, the task finish date and duration are changed. This issue occurs if the assignment finish date doesn't match the task finish date. This can be the case with fixed duration tasks.
• The Last Modified and Last Published timestamps are not converted to your timezone.
• When you save a project, some baseline information may be lost if you don't have the permission to save a baseline.
• When you save a project for sharing, and then save it back to the server, the baseline data is deleted from the project if you don't have the Save Protected Baseline permission.
• When you add a resource or do a Save As operation to the MPP format on a project that's connected to Project Web App, Project 2016 may crash.
• When you go to a view such as the Gantt chart and then click the auto filter on a date field such as the Start field, dates that are later than 2099 aren't displayed. Therefore, you can't filter days that are later than 2099 by using the auto filter.
• Assume that you set the primary language to simplified Chinese and the secondary language to English. When you try to synchronize projects with a SharePoint task list, the process fails.
• If you set % Work Complete progress on a summary task in Project 2016, work and actual work may incorrectly be added to subtasks that don't have a resource assigned.
• Assume that you select to load summary resource assignments to start Project 2016. When you go to a Resource Usage view and scroll through the resource, Project 2016 may crash. This issue occurs after you install March 8, 2016, update for Project 2016 (KB3114865).

June 2016

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

16.0.4393.1000

• Updates the translation in the project check in dialog box for French to make sure that the meaning is accurate.
• When you try to unlink a subproject from a master project that has a custom field with a lookup table defined, Project 2016 crashes if the subproject doesn't have the same lookup table definition as in the master project yet the custom field has values.
• When you try to open a large 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.

• Project 2016 may freeze when you print or preview certain projects.
• Consider this scenario:
• You have an enterprise resource custom field.
• The field has a lookup table applied to it, and multiple values can be selected.
• You have a resource that has a value in the field that's longer than 255 characters.
• You open a project in Project Professional that uses this resource.

In this situation, you receive the following error message:

The value you entered does not exist in the lookup table of this code. All values must be predefined in the code lookup table. Contact your server administrator to get new values added.

You also find that the list of values in the field is truncated or has disappeared completely.

• When you try to print a specified number of pages and select to have the timescale fit to the end of the page, the timescale doesn't horizontally fill the entire page.
• Assume that you change a date by using the date picker, and the date is not in the current year. In this situation, the day and month are changed but the year isn't changed. This issue occurs when the date format is set to 4/W04.
• When you save subprojects in the context of a master project, Project 2016 may crash. This issue may occur if the subprojects have Visual Basic Applications code in them.
• When you set a finish date for a fixed duration task in which assignments on the task have actual work entered on non-working times, the finish date is changed to a different date from what you entered, and the assignment finish date is changed to the task finish date even though the assignment doesn't share the task's finish date.
• When you open a project that has many cross project links in Project 2016, Project 2016 may freeze and eventually crashes when the computer runs out of memory.
• Assume that you open a master project that has many subprojects in Project 2016. When you press ESC to cancel the loading, Project 2016 may crash.
• Consider the following scenario:
• You have a task in your project.
• You have two resources that are assigned to the task.
• On one of the assignments, delay has been added.
• You publish the project to a server where protected actual work is enabled.
• The resource who owns the assignment where delay doesn't exist reports work and the status update is applied to the task. The other assignment still has no actual work.
• As the project manager, you set the work value to zero on the assignment that has no actual work.

In this situation, the actual start and actual finish dates are set on the assignment even though these dates weren't reported by the team member. Later, when the project manager adds work back to the assignment and tries to reschedule it, the operation fails because Project tells that the change would change work entered by a team member.

• Project 2016 may freeze when you create a recurring task.
• If you try to reset the work breakdown structure (WBS) for a selection of tasks, the entire project is updated instead.
• When you scale a printout to fit to one page in Project 2016, the printed output is unreadable.
• When you submit a Physical % Complete value for a task that is synchronized to a SharePoint task list in Project 2016, an incorrect value is displayed. For example, the value of 100% appears as 1000%.
• When you open projects, Project 2016 may crash. This issue occurs for some projects in which certain calendars in that project were duplicated.
• Consider this scenario:
• A task has an eight-hour assignment and it has been published to a team member.
• The team member opens their timesheet and enters multiple time-phased actual work values. For example, 8h on one day and 3h on a second day.
• The team member changes their mind and zeros out the last time-phased value. In this case, the 3h turns to 0h.
• The team member submits their timesheet and the status manager approves the update which is then applied to the project.

When the task and assignment are viewed in Project Professional, the task ends on the second day and the assignment ends on the first day. The expectation is that the task ends at the same time as the assignment.

• The Office.ProjectProjectFields.ProjectServerUrl property that is used in Office Application solutions returns an integer instead of a URL string.
• When you use the Project Import Wizard, you receive an incorrect merge result if the merge key is set to a custom field.
• When you set the % Work Complete value for summary tasks in Project 2016, Project 2016 may crash. This issue occurs if Project is connected to a Project server where the Only allow task updates via Tasks and Timesheets setting is enabled.
• When you synchronize a project in Microsoft Project 2016 to a SharePoint task list, some assignment data is lost if there are more than 50 rows.Note To fix this issue, you need to install June 7, 2016, update for Office 2016 (KB3114709).

May 2016

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

16.0.4378.1000

• A better translation of the following messages is now available for the Japanese language. These messages appear when a user tries to edit the name of an enterprise resource within their project:
• Changes to enterprise resources will be lost.
• You can modify an enterprise resource in a project for modeling purposes and publishing the project will include any changes. Your changes will be overwritten when the project is next opened.

A user with security permission can modify the attributes of this resource by checking out the resource with the Open Enterprise Resource Pool command.

• Fixes the following issues:
• Assume that you use a task template that has cost resources assigned to create a project in Project Web App. When you open the project in Project 2016, Project 2016 crashes.
• In some cases, a task's % Complete displays 99% even though the % Work Complete  on all the assignments on the task shows  100%.
• When you apply a group to a checked-out enterprise view in Project 2016, Project 2016 may crash.
• Consider the following scenario:
• You have an enterprise resource that's assigned to a project.
• You change the booking type for the resource.
• You save and then open the project again.

In this situation, the booking type property isn't saved.

• The ZoomTimescale Visual Basic Applications method ignores the duration parameter for the Timeline view in Project 2016. Therefore, you can't force the timeline view to zoom to a specific range.
• Consider the following scenario:
• A team member is assigned to a task that begins on Monday.
• The task is published to the team member.
• The team member opens their timesheet and enters actual work on Wednesday.
• The team member submits their timesheet.
• The project manager approves the status update from the team member.

In this situation, the task still shows that it begins on Monday instead of Wednesday.

• When a summary task is viewed in the task inspector, the subtasks aren't listed.
• Consider the following scenario:
• A user enters time phased actual work on an assignment and submits the work for approval.
• The status manager approves the update.
• The user changes the assignment start date and then submits the change.
• The status manager approves the update.

In this scenario, the time phased actual work may move to another date.

• If you use the Assign Resources dialog box to replace one resource with another resource, the total work value displayed in the Resource Usage view isn't always updated correctly.
• Setting actual cost for cost assignments on tasks doesn't always calculate the correct progress as expected. This issue occurs when the assignment is the only resource on the task.
• When you delete a resource from a split task, the split task is deleted unexpectedly.
• When you import a project from an XML file, timephased baseline work isn't imported correctly. For example, on an assignment, the baseline cost values over a 10-day period are as follows:

2h, 3h, 4h, 5h, 6h, 8h, 8h, 8h, 8h, 8h.

When it's imported, the values change to 2h, 6h, 6h, 6h, 6h, 6h, 6h, 6h, 6h.

April 2016

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

16.0.4366.1000

• After you apply status updates to project schedules, the actual work contours on some assignments unexpectedly display zero for actual work values in various time periods.
• When you try to update budget costs on resources in Project 2016, Project 2016 may crash.
• When you use an auto filter on a text type field, such as the task name, and the field contains many varied values, Project 2016 may crash.
• Assume that you add the compliant field to a view and find something isn't compliant. When you make the item compliant, the field isn't updated until you leave the view and then come back again.
• If you have the option to clear leveling values before leveling or you click the Clear Leveling button within the Resource Leveling dialog box, it doesn't always work correctly. Instead, tasks may be leveled to unexpected dates or values may still be found in the Leveling Delay field.
• You can't create a project from a SharePoint task list if the list has data validation rules set.
• When a resource is overallocated by a combination of actual work and remaining work, the work doesn't appear in red (overallocated) in that period when it's leveled on a day-by-day basis.
• Microsoft Project doesn't always calculate the finish dates of some tasks that causes them to finish later than expected. This can occur in a scheduled from finish project where implied dependencies from a summary task to the sub tasks aren't always respected.
• Assume that you have a summary task that contains one or more subtasks. Then, you make the summary task become a non-summary task either by outdenting all subtasks or by deleting all subtasks. In this scenario, the internal property on the task that specifies the duration format (minutes, hours, days, weeks, and months) may not be set correctly. Therefore, when you publish the project, the reporting data is inaccurate, and the duration of the given task isn't correct.
• When you open a master project that has cross project links, Project 2016 may crash.
• When you try to connect to a Project Web App instance in Project 2016 on a computer in which you have not recently connected to the PWA instance, the connection may fail.
• When you select multiple tasks and try to replace a resource, the replace action doesn't work if the initial resource that you are replacing isn't assigned to all the selected tasks.

March 2016

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

16.0.4351.1000

• When you merge an Excel workbook into an existing project where there's more than one assignment on a given task, only the actual work on the first assignment is updated.
• When you use Microsoft Visual Basic for Applications (VBA) macros to edit project data within the  Project.BeforeSave event handler, the edits to the project may not be saved if the project is saved to Project Server.
• After status updates are accepted and applied to tasks in a project, the total actual work on the assignments may become larger, and the new actual work appears in time periods where the user didn't report it. For example, you report 8h on Monday and 3h on Tuesday. When you view the assignment in the project after the update is applied, besides the 8h on Monday and 3h on Tuesday, you may also see 8h on Thursday and Friday.
• You can't remove remaining work from a manually scheduled task in Project 2016 when the task is published to Project Server. This issue occurs when the Only allow task updates via Tasks and Timesheets  task settings and display options are enabled.
• After you level resources by using the week-by-week or month-by-month basis in Project 2016, the resources remain overallocated.
• When you use Project 2016 with certain Windows region date and time formats (for example, Spanish (Mexico)), baseline bars aren't displayed in the Gantt chart.
• When you apply a grouping to a task type view, baseline finish type fields may not show the expected value on the grouping summary row tasks. Instead of showing the latest finish date as expected, the field shows Not Available if at least one of the grouped tasks doesn't have a baseline finish date.
• Consider the following scenario:
• A user enters time phased actual work on an assignment and submits the work for approval.
• The status manager approves the update.
• The user changes the assignment start date and then submits the change.
• The status manager approves the update.

In this scenario, the time phased actual work may move to another date.

• When you open a project from a server, it may take a long time if the project doesn't exist in the user's local active cache.
• Consider the following scenario:
• You add some Visual Basic Applications (VBA) code to a project in Project Professional 2016.
• You save and publish the project to Project Server, and then you check in the project.
• You edit the project on the schedule project detail page in Project Server.
• You change and save the project.
• You open the project again in Project Professional 2016.

In this situation, the VBA code is missing.

• Assume that you have a series of related tasks (they have dependencies between them) and you now make one of the tasks inactive. In this situation, the successor tasks to the inactive task may be scheduled later than expected.
• Macros that exist in the local global template don't work if they are invoked from the ribbon. This issue occurs when Project 2016 is connected to Project Server.
• When a plan is opened for edit in Project 2016 or in Project Web App, in some cases, additional actual work may appear on an assignment.
• If you save an incremental baseline that rolls up baseline values from a task to summary tasks, the timephased baseline values of the summary tasks are deleted from the dbo.MSP_EpmTaskBaselineByDay table in the reporting database.
• If you update a sheet view to show the notes field, you may see redraw issues.
• If you have a project that's saved to Project Server, you can't access project level properties.
• When Project 2016 connects to Project Server, Project 2016 may crash if there are enterprise templates but you don't have the permission to access them.
• It may take a long time to open multiple projects from Project Server in Project 2016.
• You can't publish a project in Project Web App and receive an error message that looks something like the following:

Cannot insert duplicate key in object 'pub.MSP_PROJECT_RESOURCES'

• It takes a long time to close and check-in a master project if Summary Resource Assignments (SRA) are loaded.
• When you print a timeline in Project 2016, the last letter can sometimes be wrapped to the next line.
• If you delete data by using the delete or backspace key in Project 2016, the BeforeTaskChange, BeforeResourceChange, and BeforeAssignmentChange events are not triggered.
• When you open a Project file from a SharePoint document library, the file is sometimes opened as read-only when it should be read and write. In other cases, the project is sometimes opened as read and write but you can't save changes.Note To fix this issue, you also need to install March 8, 2016, update for Office 2016 (KB3114857).
• After you set the Default Assignment Owner field for an enterprise resource and then create a project that uses the resource, the Default Assignment Owner field is blank.
• If you enable the Only allow task updates via Tasks and Timesheets option, you can't set tasks to 100% complete if the task has an assignment with zero work.
• When you level resources for projects in Project 2016, Project 2016 may crash.
• When you select to merge data from Excel and use the task name as the key in Project 2016, you receive an error message.

February 2016

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

16.0.4339.1000

• Enables add-in developer to receive a list of API requirement sets.
• Fixes the following issues:
• When you try to import an Excel workbook into a project in Project 2016, some assignment information is lost.
• When you try to save a project from an earlier version of Project Server in Project 2016, you receive the following error message:

Error 9000
Save job cancelled in the queue: Root element is missing.

• If you save a project as an .xml file in Project 2016, custom calendar information may not be saved. Therefore, when you open the .xml file, the calendar information is not found.
• When you open the Assign Resources dialog box in Project Standard 2016, Project Standard 2016 may crash.
• Assume that you display the Hyperlink field in Project Professional 2016. On a task, you enter an address in the Hyperlink field to a document that's stored on a SharePoint site, and then you click the link. Sometimes in this situation, the document doesn't open, and you're redirected to the root site where the document is stored.
• When you open an XML file and select the New project option, it's much slower than merging the XML file into an existing or blank project.
• When you import timephased data by using XML files in Project 2016, the <WorkContour> tags are ignored. This issue occurs when the timephased actual work values exist but the remaining work timephased values aren't complete in the XML file.
• When you open a SharePoint task list in Project 2016 and close it without saving, the %Complete fields of tasks are updated to incorrect values.
• When you start a task before the project start date, certain time scale labels in a Gantt view such as those that work from a project's start, for example, the "W1, W2, W3, W4… (From Start)" label, show the week starting at the beginning of the task instead of at the beginning of the project.
• In some cases, the font control shown on the Tasks tab in the ribbon within the Font group is empty and the font size is 0. When you try to select a font or size, Project 2016 may crash.
• When you try to print preview or pint the Team Planner view of a project in Project 2016, Project 2016 may crash or the view isn't displayed correctly. This issue occurs if the project is connected to a resource pool that has more than 20 resources.
• When you try to save a project to the Project 2007 format in Project 2016, Project 2016 crashes. This issue occurs if the project has a table defined, and the Lock first column option is enabled in the table and the locked column has a title associated with it.
• Consider the following scenario:
• A project is displayed in a time scaled view, such as the Gantt Chart view, in Project 2016.
• The timescale is formatted to display either years or half years on the top and a minor timescale of quarters or less on the bottom.

In this situation, the tick marks of the yearly or half-yearly timescale don't match with the minor timescale. For example, the year starts from December instead of January.

• When you save a password protected file by using the Save As function in Project 2016, the file may become corrupted and then can't be opened.
• When you scroll horizontally across the timescale in a Gantt type view, the nonworking time shading might not be displayed correctly. This issue occurs if you have chosen to display the shading in front of the bars.
• When you import data from an Excel workbook in Project 2016, text data that is mapped into text type fields is truncated to 128 characters. For example, a task name is truncated.

January 2016

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

16.0.4324.1000

•  Some additional properties on existing Visual Basic Application methods were added. However, in some cases, their inclusion breaks backwards compatibility with macros from earlier versions.

December 2015

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

16.0.4312.1000

• In some cases, when you save a project to Project Server, you receive a 9000 error code.

November 2015

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

16.0.4266.1001 

10/22/2015 Initial Release