June 7, 2016, update for Project 2013 (KB3115164)

• Updates the translation of the project check in dialog box for French to make sure that the meaning is accurate.
  
• Fixes the following issues:
  • When you save a project for sharing, and then you 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 use Project 2013 with Project Web App online, some users can't edit enterprise calendars. Meanwhile, the following error message is displayed:
    You need to have Microsoft Project Professional 2016 Preview installed and configured to connect to a profile for this Project Web App site. You can do so by opening Project Professional, and adding the URL of a site in your PWA site collection to the Manage Accounts dialog in the Info tab of the File menu. Then, close Project Professional, and open it connected to this profile before trying this operation again. If Project Professional is already loaded, ensure that it is connected to the profile for this Project Web App site and that there are no dialog boxes open.
    Note To fix this issue, you also have to install June 7, 2016, update for Office 2013 (KB3023049) together with this update.
  • 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 2013 may crash.
    
  • After you set a resource to have max units that's greater than 100%, you can't assign the resource to a task at 100% units.
    
  • When you open projects, Project 2013 may crash. This issue occurs for some projects in which certain calendars in those projects were duplicated. 
    
  • 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 is 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, he fails. Because Project tells him that the change would change work entered by a team member.
    
  • Consider this scenario:
    • A task has one 8-hour assignment and it is published to a team member. 
    • The team member opens their timesheet and enters multiple time-phased actual work values. For example, 8h on the first day and 3h on the second day.
    • The team member changes his 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.
    
  • Assume that you change the name of the project summary task and save the project in Project 2013 on a computer that has Windows 8.1 or Windows 10 installed. When you open the project again, the name is reverted to the previous one.
    
  • When you try to reset the work breakdown structure (WBS) for a selection of tasks, the whole project is updated instead.
    
  • Assume that you open a master project that has many subprojects in Project 2013. When you press ESC to cancel the loading, Project 2013 may crash.
    
  • When you open a project that has many cross project links in Project 2013, it may freeze and eventually crash if the computer runs out of memory.
    
  • When you use the Project Import Wizard, you receive an incorrect merge result if the merge key is set to a custom field.
    
  • Consider the following scenario:
    • You open a project in Project Server.
    • You close the project but don't check it in.
    • The project on the server is forced checked-in.
    • You try to open the project.
    In this situation, you don't receive a dialog message that indicates to load the latest version from the server.
    
  • When you scale a printout to fit to one page in Project 2013, the printed output is unreadable.
    
  • Assume that you change the name of an enterprise calendar. When you open projects that use that calendar, Project 2013 may crash.
    
  • When you save a project, some baseline information may be lost if you don't have permission to save a baseline.
    
  • When you set the % Work Complete value for summary tasks in Project 2013, Project 2013 may stop responding. This issue may occur if Project is connected to a Project server where the Only allow task updates via Tasks and Timesheets setting is enabled.
    
  • If you set % Work Complete progress on a summary task in Project 2013, work and actual work may incorrectly be added to subtasks that don't have a resource assigned.
    
  • When you connect to Project Server, the last modified and last published timestamps aren't displayed as your current timezone in Project 2013.
    

Microsoft Update

Download Center

• Download update KB3115164 for 32-bit version of Project 2013
• Download update KB3115164 for 64-bit version of Project 2013

rerequisite

Restart information

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

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