May 3, 2016, update for Project 2016 (KB3115105)

• 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.
    

Microsoft Update

Download Center

• Download update KB3115105 for 32-bit version of Project 2016
• Download update KB3115105 for 64-bit version of Project 2016

Prerequisite

Restart information

1. Start an Office 2016 application.
2. On the File menu, select Account.
3. For Office 2016 Click-to-Run installations, an Update Options item is displayed. For MSI-based installations, the Update Options item isn't displayed.

Office 2016 Click-to-Run installation	MSI-based Office 2016