Microsoft KB Archive/930597

= Some registry-based policy settings are lost and error messages are logged in the Application log on a Windows XP-based computer or on a Windows Vista-based computer =

Article ID: 930597

Article Last Modified on 12/7/2007

-

APPLIES TO


 * Microsoft Windows XP Professional
 * Windows Vista Enterprise 64-bit Edition
 * Windows Vista Home Basic 64-bit Edition
 * Windows Vista Home Premium 64-bit Edition
 * Windows Vista Ultimate 64-bit Edition
 * Windows Vista Enterprise
 * Windows Vista Home Basic
 * Windows Vista Home Premium
 * Windows Vista Ultimate

-



SYMPTOMS
You have a Microsoft Windows XP-based computer or a Windows Vista-based computer in a domain. Some registry-based policy settings are lost on the computer when either of the following conditions is true:
 * Group Policy settings are changed.
 * Group Policy settings have to be reapplied at set intervals to the computers in the domain.

Additionally, error messages that resemble the following may be logged in the Application log:

Message 1
Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1096

Date: 26/04/2006

Time: 06:14:57

User: NT AUTHORITY\SYSTEM

Computer: Computer_Name

Description:

Windows cannot access the registry policy file, \\Domain.NET\SysVol\Domain.NET\Policies\{82787E36-87C9-4C34-AD95-72365A389553}\Machine\registry.pol. (The process cannot access the file because it is being used by another process.).

Message 2
Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1043

Date: 26/04/2006

Time: 06:14:56

User:

Computer: Computer_Name

Description:

Windows cannot access the registry information at \\Domain.NET\SysVol\Domain.NET\Policies\{82787E36-87C9-4C34-AD95-72365A389553}\Machine\registry.pol. (The process cannot access the file because it is being used by another process.).





CAUSE
This problem occurs when one or more of the following conditions are true:
 * There is a sharing violation on the registry.pol file. This makes the registry.pol file inaccessible to the other processes.
 * Access to parse the registy.pol file is denied through NTFS permissions.
 * Network connectivity fails when the registry.pol file is parsed.



Windows XP
A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
You must have Microsoft Windows XP Service Pack 2 installed on the computer before you apply this hotfix.

Restart requirement
You must restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows XP, x86-based versions

Windows Vista
A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
There are no prerequisites for installing this hotfix.

Restart requirement
You must restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions

Windows Vista, x64-based versions



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
Registry values that were previously applied are removed from the registry of the computer in the domain when either of the following conditions is true:
 * Changes to Group Policy settings have been detected.
 * Group Policy changes have to be reapplied to the computers in the domain.

Then, the applicable registry values are written back to the registry of the computer in the domain by parsing the registry.pol files from the SYSVOL folder on the domain controller.

If access to one of the registry.pol files is denied, registry policy processing stops. Then, some registry values are lost because they cannot be retrieved from the SYSVOL folder. For more information, 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 query words: USERENV.LOG abort aborted missing lindakup

Keywords: kbfix kbqfe kbpubtypekc kbexpertiseinter kbhotfixserver KB930597

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.