The Group Policy client-side extension %1 failed to execute. Please look for any errors reported earlier by that extension.

Details
Product: Windows Operating System
Event ID: 1085
Source: Userenv
Version: 5.2
Symbolic Name: EVENT_EXT_FAILED
Message: The Group Policy client-side extension %1 failed to execute. Please look for any errors reported earlier by that extension.
   
Explanation

Group Policy could not apply one of the client-side extensions. As a result, the extension settings have been only partially applied.

   
User Action

To troubleshoot the client-side extension failure, do one or all of the following:

  • Review Event Viewer for events logged by the client-side extension. If events were logged by the extension, use the information in the event description to troubleshoot the problem.
  • At the command prompt, type gpupdate, and then check Event Viewer to see whether the Userenv 1085 event is logged again.
  • If the client-side extension event descriptions indicate s there was an error loading the extension, finding a particular entry point, or finding the correct registry data, the extension might not be registered correctly on the computer. In that case, re-register the appropriate DLL files by typing
    regsvr32 at the command prompt. Note that the correct DLL to register depends on the extension. For Group Policy extensions that are included with Windows, the following table lists which DLLs are used by which extension.

    Client-side extensions DLL file name
    Registry (in Administrative Templates) Userenv.dll
    Disk Quota (in Administrative Templates) Dskquota.dll
    Folder Redirection Fdeploy.dll
    Scripts; IP Security; QoS Packet Scheduler; Wireless Gptext.dll
    Software Installation Appmgmts.dll
    Security; EFS (Encrypting File System) Recovery; PKI; Software Restriction Scecli.dll
    Internet Explorer Maintenance iedkcs32.dll
  • If re-registering the DLL files for the extension does not help, restore the file system and/or registry using the most recent backup.

If none of the above actions identified the problem, see the ‘Troubleshooting Group Policy’
white paper at the Microsoft Web site.

Related:

Leave a Reply