Microsoft KB Archive/319006

= Event ID 1000: Windows Cannot Read the History of GPOs from the Registry =

Article ID: 319006

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition

-



This article was previously published under Q319006



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
The following event may be logged in the Application event log:

Event ID: 1000

Event Source: Userenv

Description:

Windows cannot read the history of GPOs from the registry



CAUSE
This behavior may occur if some values (such as Options or FileSysPath) are missing in subkeys of the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\History

When this occurs, Group Policy cannot be applied on the computer.



RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this behavior:  Use Registry Editor Regedt32 to check the permissions on the History key. Make sure that the permissions are:  Administrators (Read, Full Control) Authenticated Users (Read) System (Read, Full Control)

 Delete all of the subkeys in the History key, and then refresh the group policy. To immediately regenerate the deleted keys in the registry, type the following command at a command prompt on the affected computer:

secedit /refreshpolicy machine_policy /enforce

The subkeys are re-created in the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\History

</li></ol>

You can also check the Application event log for informational event ID 1704.

Additional query words: userenv logging

Keywords: kbenv kberrmsg kbprb KB319006

-

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

© Microsoft Corporation. All rights reserved.