February 6, 2018, update for Project 2013 (KB4011679)

Improvements and fixes

This update fixes the following issues:

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

• Consider the following scenario:

  • You have a task that has a resource assigned.

  • The task has a split in it. For example, there is 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 is no work.

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

• Consider the following scenario:

  • You have a Project Web App site and Project Professional 2013 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 for these custom fields.

  • You open the project in Project Professional 2013, 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.

How to download and install the update

Update information

Prerequisites

To apply this update, you must have Microsoft Project 2013 Service Pack 1 installed.

Restart information

You may have to restart the computer after you install this update.

More Information

To determine whether your Office installation is Click-to-Run or MSI-based, follow these steps:

1. Start an Office 2013 application, such as Microsoft Word 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.

How to uninstall this update

Windows 10

1. Go to Start, enter View Installed Updates in the Search Windows box, and then press Enter.

2. In the list of updates, locate and select update KB4011679, and then select Uninstall.

Windows 8 and Windows 8.1

1. Swipe in from the right edge of the screen, and then tap Search. If you're using a mouse, point to the lower-right corner of the screen, and then select Search.

2. Enter windows update, select Windows Update, and then select Installed Updates.

3. In the list of updates, locate and select update KB4011679, and then select Uninstall.

Windows 7

1. Go to Start, enter Run, and then select Run.

2. Enter Appwiz.cpl, and then select OK.

3. Select View installed updates.

4. In the list of updates, locate and then select update KB4011679, and then select Uninstall.

References

Learn about the standard terminology that Microsoft uses to describe software updates.

The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all versions of Office.

File information

x86

project-x-none.msp file information

x64

project-x-none.msp file information