GPO import fails and rollback results in the target policy being deleted on a Windows Server 2012 R2-based DC

This article describes an issue in which the Group Policy Object (GPO) import fails and the target policy is deleted during the rollback process on a Windows Server 2012 R2-based domain controller (DC). An update is available to fix this issue. Before you install this update, see the Prerequisites section.

Symptoms

When you use Group Policy Management Console (GPMC) to import a backed up GPO, the import may fail if a file is held open in one of the temporary directories that is created during the import process. When this issue occurs, you receive the following error message:

The process cannot access the file because it is being used by another process

The GPMC will then roll back the import process, which may result in the target policy being deleted.

GPMC uses the following temporary directories when it process the Group Policy import:
  • MachineOld
  • UserOld
  • MachineStaging
  • UserStaging
  • AdmOld
If a file is held open in one of these directories, the import can't be completed. The rollback logic also doesn't restore the target policy if we don't close all the files in the staging directories.

How to get this update

Important If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.

Method 1: Windows Update

This update is provided as a Recommended update on Windows Update. For more information on how to run Windows Update, see How to get an update through Windows Update.

Method 2: Microsoft Update Catalog

To get the stand-alone package for this update, go to the Microsoft Update Catalog website.

Update detail information

Prerequisites

To install this update, you should first install April 2014, update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) in Windows 8.1 or Windows Server 2012 R2.

Registry information

To apply this update, you don't have to make any changes to the registry.

Restart requirement

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

Update replacement information

This update doesn't replace a previously released update.

Workaround

To work around this issue, exclude the temporary directories that GPMC uses from Distributed File System Replication (DFSR) or the File Replication Service (FRS) replication. See Importing a GPO using GPMC fails with "The Directory is not empty" for more information about how to exclude these folders from the DFSR replication.

Note Any component that keeps a file open in one of these directories could cause the issue to occur. However, this workaround will only work if DFSR or FRS was causing the file to be held open.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

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

File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables.
Windows 8.1 and Windows Server 2012 R2
Additional file information
Properties

Article ID: 3146601 - Last Review: May 11, 2016 - Revision: 1

Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1

Feedback