Symptoms
Assume that you have a client computer in a Windows Server 2008 R2-based or Windows Server 2012-based domain environment. Additionally, assume that the client computer has an exclusive lock on the Registry.pol file. In this situation, the following issues may occur:
-
A "File in use" error message is received when the administrator tries to edit a specific Group Policy.
-
A "File in use" error message is received when the Distributed File System Replication (DFSR) service tries to replicate updates to the Registry.pol file.
Additionally, you receive the following event log:
Cause
This issue occurs because a Server Message Block (SMB) protocol prevents the release of the exclusive lock for the client computer.
Resolution
After you apply this hotfix and set the registry key value on the Domain Controller, the event information is changed as follows:Note Depending on results of different operations, Event ID 6321 displays one of the following three possible description messages:
Hotfix information
To resolve this issue, install this hotfix on the Domain Controller or a client computer that has the Remote Server Administration Tools feature installed. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running Windows Server 2008 R2 Service Pack 1 (SP1) or Windows Server 2012.Additionally, Windows Server 2008 R2-based or Windows Server 2012-based computer must be a Domain Controller.
Registry information
To resolve this issue, you have to create the following registry key on the Domain Controller:
-
Start Registry Editor. To do this, press WIN+R, type regedit, and then click OK.
-
Locate and then click the following registry key:HKLM\Software\Policies\Microsoft\Windows\System
-
On the Edit menu, point to New, and then click DWORD Value.
-
Type GroupPolicyForceCloseSysvolFileHandle, and then chick Modify.
-
In the value data box, type 1, and then click OK.
-
Exit Registry Editor.
-
Restart the Domain Controller.
Notes
-
Any nonzero value will enable this feature.
-
You can also apply this hotfix and then create the registry key. You have to restart the Group Policy service on the Domain controller to enable the setting.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 and Windows Server 2012 file information notesImportant Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.ImportantWindows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.1.760 1.22xxx
Windows Server 2008 R2
SP1
LDR
6.2.920 0.20 xxx
Windows Server 2012
RTM
LDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Gpapi.dll |
6.1.7601.22244 |
96,256 |
07-Feb-2013 |
14:41 |
x64 |
|
Gpsvc.dll |
6.1.7601.22244 |
786,944 |
07-Feb-2013 |
14:41 |
x64 |
|
Gpapi.dll |
6.1.7601.22244 |
79,360 |
07-Feb-2013 |
13:38 |
x86 |
For all supported x64-based versions of Windows Server 2012
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Gpapi.dll |
6.2.9200.20626 |
108,544 |
07-Feb-2013 |
01:48 |
x64 |
|
Gpsvc.dll |
6.2.9200.20626 |
1,370,112 |
07-Feb-2013 |
01:48 |
x64 |
|
Gpapi.dll |
6.2.9200.20626 |
95,232 |
07-Feb-2013 |
01:25 |
x86 |
For all supported IA-64-based versions of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Gpapi.dll |
6.1.7601.22244 |
168,448 |
07-Feb-2013 |
13:37 |
IA-64 |
|
Gpsvc.dll |
6.1.7601.22244 |
1,336,832 |
07-Feb-2013 |
13:37 |
IA-64 |
|
Gpapi.dll |
6.1.7601.22244 |
79,360 |
07-Feb-2013 |
13:38 |
x86 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information for Windows Server 2008 R2 and Windows Server 2012
Additional files for all supported x64-based versions of Windows Server 2008 R2
|
File name |
Amd64_microsoft-windows-grouppolicy-base_31bf3856ad364e35_6.1.7601.22244_none_86b275f516d848e8.manifest |
|
File version |
Not applicable |
|
File size |
131,926 |
|
Date (UTC) |
07-Feb-2013 |
|
Time (UTC) |
15:15 |
|
Platform |
Not applicable |
|
File name |
Wow64_microsoft-windows-grouppolicy-base_31bf3856ad364e35_6.1.7601.22244_none_910720474b390ae3.manifest |
|
File version |
Not applicable |
|
File size |
61,003 |
|
Date (UTC) |
07-Feb-2013 |
|
Time (UTC) |
13:57 |
|
Platform |
Not applicable |
Additional files for all supported x64-based versions of Windows Server 2012
|
File name |
Amd64_microsoft-windows-grouppolicy-base_31bf3856ad364e35_6.2.9200.20626_none_81b989f689b2011c.manifest |
|
File version |
Not applicable |
|
File size |
137,806 |
|
Date (UTC) |
07-Feb-2013 |
|
Time (UTC) |
03:39 |
|
Platform |
Not applicable |
|
File name |
Wow64_microsoft-windows-grouppolicy-base_31bf3856ad364e35_6.2.9200.20626_none_8c0e3448be12c317.manifest |
|
File version |
Not applicable |
|
File size |
64,120 |
|
Date (UTC) |
07-Feb-2013 |
|
Time (UTC) |
01:58 |
|
Platform |
Not applicable |
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
|
File name |
Ia64_microsoft-windows-grouppolicy-base_31bf3856ad364e35_6.1.7601.22244_none_2a957e675e78e0ae.manifest |
|
File version |
Not applicable |
|
File size |
131,923 |
|
Date (UTC) |
07-Feb-2013 |
|
Time (UTC) |
14:06 |
|
Platform |
Not applicable |
|
File name |
Wow64_microsoft-windows-grouppolicy-base_31bf3856ad364e35_6.1.7601.22244_none_910720474b390ae3.manifest |
|
File version |
Not applicable |
|
File size |
61,003 |
|
Date (UTC) |
07-Feb-2013 |
|
Time (UTC) |
13:57 |
|
Platform |
Not applicable |
