Enabling Debug Logging

There are optional debug logging for the Group Policy Editor that provide much more detailed logging than is available from within Event Viewer. You can enable debug logging by creating and configuring the following REG_DWORD registry value.

The value normally used for troubleshooting purposes is 0x10002. Configuring this registry value will create a GpEdit.log in the %SystemRoot%\debug\usermode folder. The following sample output for this log file indicates malformed ADMX files named test.admx and test.adml.

GPEDIT(b6c.10c8) 12:10:03:713 PDX parser: Parsing file 'C:\Windows\PolicyDefinitions
     \FolderRedirection.admx'.
GPEDIT(b6c.10c8) 12:10:03:716 PDX parser: Obtained appropriate PDX resource file
     'C:\Windows\PolicyDefinitions\en-US\FolderRedirection.adml' for language 'en-US'.
GPEDIT(b6c.10c8) 12:10:03:717 PDX parser: Parsing resource file
     'C:\Windows\PolicyDefinitions\en-US\FolderRedirection.adml'.
GPEDIT(b6c.10c8) 12:10:03:719 PDX parser: Parsing resource file completed successfully.
GPEDIT(b6c.10c8) 12:10:03:720 PDX parser: Successfully parsed file.
GPEDIT(b6c.10c8) 12:10:03:720 PDX parser: Parsing file 'C:\Windows\PolicyDefinitions
     \test.admx'.
GPEDIT(b6c.10c8) 12:10:03:721 CSAXErrorHandlerImpl::fatalError: Parsing error, hr =
     0xc00cee2d, message = 'Incorrect document syntax.
GPEDIT(b6c.10c8) 12:10:11:223 CSAXParser::ParseURL: parseURL for C:\Windows
     \PolicyDefinitions\test.admx failed with 0xc00cee2d.
GPEDIT(b6c.10c8) 12:10:11:223 PDX parser: Failed to parse C:\Windows\PolicyDefinitions
     \test.admx with 0xc00cee2d.