| 103 | Local Group Policy |
Local Group Policy |
| 107 | Registry |
Registry |
| 108 | Applying %.50s policy |
Applying %.50s policy |
| 109 | Applying your personal settings |
Applying your personal settings |
| 110 | Applying computer settings |
Applying computer settings |
| 111 | Group Policy Infrastructure |
Group Policy Infrastructure |
| 112 | Local Group Policy\%s |
Local Group Policy\%s |
| 113 | Non-Administrators |
Non-Administrators |
| 114 | Denied (WMI Filter) |
Denied (WMI Filter) |
| 115 | Disabled (Link) |
Disabled (Link) |
| 116 | Disabled (GPO) |
Disabled (GPO) |
| 117 | Denied (Security) |
Denied (Security) |
| 118 | Not Applied (Empty) |
Not Applied (Empty) |
| 119 | Not Applied (Unknown Reason) |
Not Applied (Unknown Reason) |
| 120 | None |
None |
| 121 | Use the Event Viewer to analyse the Group Policy operational log for details on Group Policy service activity. |
Use the Event Viewer to analyze the Group Policy operational log for details on Group Policy service activity. |
| 122 | Waiting for Workplace Connectivity |
Waiting for Workplace Connectivity |
| 10002 | Applying user settings |
Applying user settings |
| 0x3EA | The processing of Group Policy failed because of a system allocation failure. Please ensure the computer is not running low on resources (memory, available disk space). Group Policy processing will be attempted at the next refresh cycle. |
The processing of Group Policy failed because of a system allocation failure. Please ensure the computer is not running low on resources (memory, available disk space). Group Policy processing will be attempted at the next refresh cycle. |
| 0x3EE | The processing of Group Policy failed. Windows could not authenticate to the Active Directory service on a domain controller. (LDAP Bind function call failed). Look in the details tab for error code and description. |
The processing of Group Policy failed. Windows could not authenticate to the Active Directory service on a domain controller. (LDAP Bind function call failed). Look in the details tab for error code and description. |
| 0x3EF | The processing of Group Policy failed. Windows could not determine the site associated for this computer, which is required for Group Policy processing. |
The processing of Group Policy failed. Windows could not determine the site associated for this computer, which is required for Group Policy processing. |
| 0x406 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 0x41C | The processing of Group Policy failed. Windows could not determine the role of this computer. Role information (Workgroup, Member Server or Domain Controller) is required to process Group Policy. |
The processing of Group Policy failed. Windows could not determine the role of this computer. Role information (Workgroup, Member Server, or Domain Controller) is required to process Group Policy. |
| 0x41D | The processing of Group Policy failed. Windows could not resolve the username. This could be caused by one of more of the following: %na) Name Resolution failure on the current domain controller. %nb) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). |
The processing of Group Policy failed. Windows could not resolve the user name. This could be caused by one of more of the following: %na) Name Resolution failure on the current domain controller. %nb) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). |
| 0x41E | The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly. |
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly. |
| 0x41F | The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: %na) Name Resolution failure on the current domain controller. %nb) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). |
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: %na) Name Resolution failure on the current domain controller. %nb) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). |
| 0x422 | The processing of Group Policy failed. Windows attempted to read the file %9 from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: %na) Name Resolution/Network Connectivity to the current domain controller. %nb) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). %nc) The Distributed File System (DFS) client has been disabled. |
The processing of Group Policy failed. Windows attempted to read the file %9 from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: %na) Name Resolution/Network Connectivity to the current domain controller. %nb) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). %nc) The Distributed File System (DFS) client has been disabled. |
| 0x429 | The processing of Group Policy failed. Windows could not evaluate the Windows Management Instrumentation (WMI) filter for the Group Policy object %8. This could be caused by RSOP being disabled or Windows Management Instrumentation (WMI) service being disabled, stopped or other WMI errors. Make sure the WMI service is started and the start-up type is set to automatic. New Group Policy objects or settings will not process until this event has been resolved. |
The processing of Group Policy failed. Windows could not evaluate the Windows Management Instrumentation (WMI) filter for the Group Policy object %8. This could be caused by RSOP being disabled or Windows Management Instrumentation (WMI) service being disabled, stopped, or other WMI errors. Make sure the WMI service is started and the startup type is set to automatic. New Group Policy objects or settings will not process until this event has been resolved. |
| 0x42C | The processing of Group Policy was interrupted. Windows prematurely ended the discovery and enforcement of Group Policy settings because the computer was requested to shutdown or the user logged off. Group Policy processing will be attempted next refresh cycle, on the next computer reboot or the next user logon. |
The processing of Group Policy was interrupted. Windows prematurely ended the discovery and enforcement of Group Policy settings because the computer was requested to shutdown or the user logged off. Group Policy processing will be attempted next refresh cycle, on the next computer reboot, or the next user logon. |
| 0x437 | The processing of Group Policy failed. Windows could not obtain the list of Group Policy objects applicable for this computer or user. View the event details for more information. |
The processing of Group Policy failed. Windows could not obtain the list of Group Policy objects applicable for this computer or user. View the event details for more information. |
| 0x438 | The processing of Group Policy failed. Windows could not search the Active Directory organisation unit hierarchy. View the event details for more information. |
The processing of Group Policy failed. Windows could not search the Active Directory organization unit hierarchy. View the event details for more information. |
| 0x43D | Windows failed to apply the %8 settings. %8 settings might have its own log file. Please click on the \"More information\" link. |
Windows failed to apply the %8 settings. %8 settings might have its own log file. Please click on the \"More information\" link. |
| 0x440 | The processing of Group Policy failed. Windows attempted to query the list of Group Policy objects and exceeded the maximum limit (999). |
The processing of Group Policy failed. Windows attempted to query the list of Group Policy objects and exceeded the maximum limit (999). |
| 0x441 | Windows failed to record Resultant Set of Policy (RSoP) information, which describes the scope of Group Policy objects applied to the computer or user. This could be caused by RSOP being disabled or Windows Management Instrumentation (WMI) service being disabled, stopped or other WMI errors. Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately. |
Windows failed to record Resultant Set of Policy (RSoP) information, which describes the scope of Group Policy objects applied to the computer or user. This could be caused by RSOP being disabled or Windows Management Instrumentation (WMI) service being disabled, stopped, or other WMI errors. Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately. |
| 0x442 | Windows failed to record Resultant Set of Policy (RSoP) information, which describes the scope of Group Policy objects applied to the computer or user. This could be caused by Windows Management Instrumentation (WMI) service being disabled, stopped or other WMI errors. Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately. |
Windows failed to record Resultant Set of Policy (RSoP) information, which describes the scope of Group Policy objects applied to the computer or user. This could be caused by Windows Management Instrumentation (WMI) service being disabled, stopped, or other WMI errors. Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately. |
| 0x443 | Windows could not record the Resultant Set of Policy (RSoP) information for the Group Policy extension . Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately. |
Windows could not record the Resultant Set of Policy (RSoP) information for the Group Policy extension . Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately. |
| 0x447 | Windows encountered an error while recording Resultant Set of Policy (RSoP) information, which describes the scope of Group Policy objects applied to the computer or user. Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately. |
Windows encountered an error while recording Resultant Set of Policy (RSoP) information, which describes the scope of Group Policy objects applied to the computer or user. Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately. |
| 0x448 | The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object %8. Group Policy settings will not be resolved until this event is resolved. View the event details for more information on the filename and path that caused the failure. |
The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object %8. Group Policy settings will not be resolved until this event is resolved. View the event details for more information on the file name and path that caused the failure. |
| 0x449 | The processing of Group Policy failed. Windows could not determine the computer account to enforce Group Policy settings. This may be transient. Group Policy settings, including computer configuration, will not be enforced for this computer. |
The processing of Group Policy failed. Windows could not determine the computer account to enforce Group Policy settings. This may be transient. Group Policy settings, including computer configuration, will not be enforced for this computer. |
| 0x44D | The processing of Group Policy failed. Windows could not locate the directory object %8. Group Policy settings will not be enforced until this event is resolved. View the event details for more information on this error. |
The processing of Group Policy failed. Windows could not locate the directory object %8. Group Policy settings will not be enforced until this event is resolved. View the event details for more information on this error. |
| 0x450 | Windows was unable to read the Windows Management Instrumentation (WMI) filter information associated with the Group Policy object %8. This may be caused by a deleted WMI Filter defined in the domain that is still in use by Group Policy objects. Group Policy settings for this Group Policy object will not be enforced. Other Group Policy objects may still apply. Windows will attempt to retrieve this information at the next policy cycle. This specific problem may be resolved by identifying all GPOs that reference the WMI filter and removing the references. Contact an administrator if this event recurs for several hours. |
Windows was unable to read the Windows Management Instrumentation (WMI) filter information associated with the Group Policy object %8.This may be caused by a deleted WMI Filter defined in the domain that is still in use by Group Policy objects. Group Policy settings for this Group Policy object will not be enforced. Other Group Policy objects may still apply. Windows will attempt to retrieve this information at the next policy cycle. This specific problem may be resolved by identifying all GPOs that reference the WMI filter and removing the references. Contact an administrator if this event recurs for several hours. |
| 0x455 | The user account is in a different forest than the computer account. The processing of Group Policy from another forest is not allowed. Group Policy will be processed using Loopback Replace mode. The scope of the user policy settings will be determined by the location of the computer object in Active Directory. The settings will be acquired from the User Configuration of these policies. |
The user account is in a different forest than the computer account. The processing of Group Policy from another forest is not allowed. Group Policy will be processed using Loopback Replace mode. The scope of the user policy settings will be determined by the location of the computer object in Active Directory. The settings will be acquired from the User Configuration of these policies. |
| 0x456 | The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. |
The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. |
| 0x458 | The Group Policy Client Side Extension %8 was unable to apply one or more settings because the changes must be processed before system start-up or user logon. The system will wait for Group Policy processing to finish completely before the next start-up or logon for this user, and this may result in slow start-up and boot performance. |
The Group Policy Client Side Extension %8 was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance. |
| 0x465 | The processing of Group Policy failed because of an internal system error. Please see the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle. |
The processing of Group Policy failed because of an internal system error. Please see the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle. |
| 0x466 | Windows was unable to determine whether new Group Policy settings defined by a network administrator should be enforced for this user or computer because this computer's clock is not synchronised with the clock of one of the domain controllers for the domain. Because of this issue, this computer system may not be in compliance with the network administrator’s requirements, and users of this system may not be able to use some functionality on the network. Windows will periodically attempt to retry this operation, and it is possible that either this system or the domain controller will correct the time settings without intervention by an administrator, so the problem will be corrected. %n%nIf this issue persists for more than an hour, checking the local system's clock settings to ensure they are accurate and are synchronised with the clocks on the network's domain controllers is one way to resolve this problem. A network administrator may be required to resolve the issue if correcting the local time settings does not address the problem. |
Windows was unable to determine whether new Group Policy settings defined by a network administrator should be enforced for this user or computer because this computer's clock is not synchronized with the clock of one of the domain controllers for the domain. Because of this issue, this computer system may not be in compliance with the network administrator’s requirements, and users of this system may not be able to use some functionality on the network. Windows will periodically attempt to retry this operation, and it is possible that either this system or the domain controller will correct the time settings without intervention by an administrator, so the problem will be corrected. %n%nIf this issue persists for more than an hour, checking the local system's clock settings to ensure they are accurate and are synchronized with the clocks on the network's domain controllers is one way to resolve this problem. A network administrator may be required to resolve the issue if correcting the local time settings does not address the problem. |
| 0x467 | The processing of Group Policy failed due to an internal error. Please look into the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle. |
The processing of Group Policy failed due to an internal error. Please look into the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle. |
| 0x468 | The Group Policy Client Side Extension %3 may have caused the Group Policy Service to terminate unexpectedly. To prevent further failures in the Group Policy Service, this extension has been temporarily disabled until after the next system restart. Group Policy settings managed by this extension may no longer be enforced until the system is restarted. The vendor of this extension should be contacted if this issue recurs. |
The Group Policy Client Side Extension %3 may have caused the Group Policy Service to terminate unexpectedly. To prevent further failures in the Group Policy Service, this extension has been temporarily disabled until after the next system restart. Group Policy settings managed by this extension may no longer be enforced until the system is restarted. The vendor of this extension should be contacted if this issue recurs. |
| 0x469 | The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. |
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. |
| 0x46A | %5 failed. %n%tGPO Name: %6%n%tGPO File System Path: %7%n%tScript Name: %8 |
%5 failed. %n%tGPO Name : %6%n%tGPO File System Path : %7%n%tScript Name: %8 |
| 0x5DC | The Group Policy settings for the computer were processed successfully. There were no changes detected since the last successful processing of Group Policy. |
The Group Policy settings for the computer were processed successfully. There were no changes detected since the last successful processing of Group Policy. |
| 0x5DD | The Group Policy settings for the user were processed successfully. There were no changes detected since the last successful processing of Group Policy. |
The Group Policy settings for the user were processed successfully. There were no changes detected since the last successful processing of Group Policy. |
| 0x5DE | The Group Policy settings for the computer were processed successfully. New settings from %6 Group Policy objects were detected and applied. |
The Group Policy settings for the computer were processed successfully. New settings from %6 Group Policy objects were detected and applied. |
| 0x5DF | The Group Policy settings for the user were processed successfully. New settings from %6 Group Policy objects were detected and applied. |
The Group Policy settings for the user were processed successfully. New settings from %6 Group Policy objects were detected and applied. |
| 0x1000 | Retrieving Domain Controller details. |
Retrieving Domain Controller details. |
| 0x1001 | Forcing rediscovery of Domain Controller details. |
Forcing re-discovery of Domain Controller details. |
| 0x1002 | Network state change detected. |
Network state change detected. |
| 0x1003 | seconds |
seconds |
| 0x1004 | minutes |
minutes |
| 0x1005 | No changes were detected. |
No changes were detected. |
| 0x1006 | Changes were detected. |
Changes were detected. |
| 0x1007 | Group Policy wait for network subsystem failed at computer boot. Group Policy processing will continue. |
Group Policy wait for network subsystem failed at computer boot. Group Policy processing will continue. |
| 0x1008 | Group Policy cannot be applied because the computer has been booted in Directory Services Restore Mode. |
Group Policy cannot be applied because the computer has been booted in Directory Services Restore Mode. |
| 0x1009 | Access check based on security descriptor failed. |
Access check based on security descriptor failed. |
| 0x100A | Start-up scripts are not visible. Start-up scripts are visible only when start-up scripts are configured to run synchronously. |
Startup scripts are not visible. Startup scripts are visible only when startup scripts are configured to run synchronously. |
| 0x100B | Failed to get the active console session. |
Failed to get the active console session. |
| 0x100C | Group Policy refresh access check failed. |
Group Policy refresh access check failed. |
| 0x100D | Group Policy notify access check failed. |
Group Policy notify access check failed. |
| 0x100E | Group Policy notify access check for console session failed. |
Group Policy notify access check for console session failed. |
| 0x100F | Policy to deny users from refreshing computer policy is set. |
Policy to deny users from refreshing computer policy is set. |
| 0x1010 | slow |
slow |
| 0x1011 | fast |
fast |
| 0x1012 | Attempting to retrieve the account information. |
Attempting to retrieve the account information. |
| 0x1013 | Retrieved account information. |
Retrieved account information. |
| 0x1014 | Retrying to retrieve account information. |
Retrying to retrieve account information. |
| 0x1015 | Making system call to get account information. |
Making system call to get account information. |
| 0x1016 | The system call to get account information completed. |
The system call to get account information completed. |
| 0x1017 | Making LDAP calls to connect and bind to Active Directory. |
Making LDAP calls to connect and bind to Active Directory. |
| 0x1018 | The LDAP call to connect and bind to Active Directory completed. |
The LDAP call to connect and bind to Active Directory completed. |
| 0x1019 | Bandwidth estimation failure: Failed to refresh network data associated with query. |
Bandwidth estimation failure: Failed to refresh network data associated with query. |
| 0x101A | Bandwidth estimation failure: Failed to enumerate network signatures associated with query. |
Bandwidth estimation failure: Failed to enumerate network signatures associated with query. |
| 0x101B | Bandwidth estimation failure: Failed to query Intranet capability. |
Bandwidth estimation failure: Failed to query Intranet capability. |
| 0x101C | Bandwidth estimation failure: Failed to inspect result of NLA query. |
Bandwidth estimation failure: Failed to inspect result of NLA query. |
| 0x101D | Failed to register for connectivity notification. |
Failed to register for connectivity notification. |
| 0x101E | Failed to query information about security package. |
Failed to query information about security package. |
| 0x101F | Failed to acquire handle to pre-existing credentials of security principal. |
Failed to acquire handle to preexisting credentials of security principal. |
| 0x1020 | Failed to initiate security context. |
Failed to initiate security context. |
| 0x1021 | Failed to establish security context. |
Failed to establish security context. |
| 0x1022 | Failed to obtain access token for security context. |
Failed to obtain access token for security context. |
| 0x1023 | Making system calls to access specified file. |
Making system calls to access specified file. |
| 0x1024 | The system calls to access specified file completed. |
The system calls to access specified file completed. |
| 0x1025 | Failed to determine the Group Policy properties of the installed system. Only a subset of Group Policy functionality will be available. |
Failed to determine the Group Policy properties of the installed system. Only a subset of Group Policy functionality will be available. |
| 0x1026 | Failed to determine the Group Policy properties of the installed system. Group Policy will wait for the network at start-up and logon. |
Failed to determine the Group Policy properties of the installed system. Group Policy will wait for the network at startup and logon. |
| 0x1027 | Failed to determine the Group Policy properties of the installed system. Group Policy will wait for the network at start-up and logon for a maximum of 120 seconds. |
Failed to determine the Group Policy properties of the installed system. Group Policy will wait for the network at startup and logon for a maximum of 120 seconds. |
| 0x1040 | Initialising and reading current service configuration for the Group Policy Client service. |
Initializing and reading current service configuration for the Group Policy Client service. |
| 0x1041 | Checking for Group Policy client extensions that are not part of the system. |
Checking for Group Policy client extensions that are not part of the system. |
| 0x1042 | Service configuration must be updated to standalone due to the presence of a Group Policy client extension that is not part of the operating system. |
Service configuration must be updated to standalone due to the presence of a Group Policy client extension that is not part of the operating system. |
| 0x1043 | Service configuration update to standalone is not required and will be skipped. |
Service configuration update to standalone is not required and will be skipped. |
| 0x1044 | Attempting to update service configuration to standalone. |
Attempting to update service configuration to standalone. |
| 0x1045 | Finished checking for non-system extensions. |
Finished checking for non-system extensions. |
| 0x1046 | Initialising service instance state to detect previous instances of the service. |
Initializing service instance state to detect previous instances of the service. |
| 0x1047 | A previous instance of the Group Policy Client Service has been detected. |
A previous instance of the Group Policy Client Service was detected. |
| 0x1048 | The Group Policy Client service is currently configured as a shared service. |
The Group Policy Client service is currently configured as a shared service. |
| 0x1049 | The Group Policy Client service is currently configured as a standalone service. |
The Group Policy Client service is currently configured as a standalone service. |
| 0x1050 | Computer determined to be not in a site. |
Computer determined to be not in a site. |
| 0x1051 | Group Policy wait for Direct Access CorpNet connectivity failed at computer boot. Group Policy processing will continue. |
Group Policy wait for Direct Access CorpNet connectivity failed at computer boot. Group Policy processing will continue. |
| 0x1052 | Group Policy Service aborted due to computer shut-down or user logoff. |
Group Policy Service aborted due to computer shutdown or user logoff. |
| 0x1060 | A non-group policy SYSVOL file is locked. This may prevent synchronising important Group Policy files between domain controllers. |
A non group policy SYSVOL file is locked. This may prevent synchronizing important Group Policy files between domain controllers. |
| 0x1061 | A group policy file in SYSVOL is locked. This may prevent synchronising important Group Policy files between domain controllers. Forcefully closed it. |
A group policy file in SYSVOL is locked. This may prevent synchronizing important Group Policy files between domain controllers. Forcefully closed it. |
| 0x1062 | A group policy file in SYSVOL is locked. This may prevent synchronising important Group Policy files between domain controllers. Failed to forcefully close it. |
A group policy file in SYSVOL is locked. This may prevent synchronizing important Group Policy files between domain controllers. Failed to forcefully close it. |
| 0x30000001 | Start |
Start |
| 0x30000002 | Stop |
Stop |
| 0x50000002 | Error |
Error |
| 0x50000003 | Warning |
Warning |
| 0x50000004 | Information |
Information |
| 0x90000001 | Microsoft-Windows-GroupPolicy |
Microsoft-Windows-GroupPolicy |
| 0x90000002 | System |
System |
| 0x90000003 | Microsoft-Windows-GroupPolicy/Operational |
Microsoft-Windows-GroupPolicy/Operational |
| 0xB0000FB0 | Starting %2 Extension Processing. %n%nList of applicable Group Policy objects: (%5)%n%n%6 |
Starting %2 Extension Processing. %n%nList of applicable Group Policy objects: (%5)%n%n%6 |
| 0xB0000FB1 | %1 %n%2 |
%1 %n%2 |
| 0xB0000FB2 | Starting %2 for %1. |
Starting %2 for %1. |
| 0xB0000FB3 | Running script name %1. |
Running script name %1. |
| 0xB0001013 | Group Policy Service started. |
Group Policy Service started. |
| 0xB0001014 | Started the Group Policy service initialisation phase. |
Started the Group Policy service initialization phase. |
| 0xB000101E | Group Policy receiving applicable GPOs from the domain controller. |
Group Policy receiving applicable GPOs from the domain controller. |
| 0xB0001078 | Starting to save policies to the local datastore. |
Starting to save policies to the local datastore. |
| 0xB0001079 | Starting to load policies from the local datastore. |
Starting to load policies from the local datastore. |
| 0xB000107A | Starting the first WMI query for the policy. |
Starting the first WMI query for the policy. |
| 0xB00010A1 | Starting to download policies. |
Starting to download policies. |
| 0xB00010E6 | Group Policy is trying to discover the Domain Controller information. |
Group Policy is trying to discover the Domain Controller information. |
| 0xB0001398 | Completed %3 Extension Processing in %1 milliseconds. |
Completed %3 Extension Processing in %1 milliseconds. |
| 0xB0001399 | %3 %n%4%nThe call completed in %1 milliseconds. |
%3 %n%4%nThe call completed in %1 milliseconds. |
| 0xB000139A | Completed %4 for %3 in %1 seconds. |
Completed %4 for %3 in %1 seconds. |
| 0xB000139B | Completed %3 in %1 seconds. |
Completed %3 in %1 seconds. |
| 0xB00013FB | Group Policy Service stopped. |
Group Policy Service stopped. |
| 0xB00013FC | Successfully completed the Group Policy Service initialisation phase. |
Successfully completed the Group Policy Service initialization phase. |
| 0xB00013FD | Group policy session completed successfully. |
Group policy session completed successfully. |
| 0xB0001406 | Group Policy successfully got applicable GPOs from the domain controller. |
Group Policy successfully got applicable GPOs from the domain controller. |
| 0xB0001460 | Successfully saved policies to the local datastore. |
Successfully saved policies to the local datastore. |
| 0xB0001461 | Successfully loaded policies from the local datastore. |
Successfully loaded policies from the local datastore. |
| 0xB0001462 | Successfully completed the first WMI query. |
Successfully completed the first WMI query. |
| 0xB0001489 | Successfully completed downloading policies. |
Successfully completed downloading policies. |
| 0xB00014BC | Domain Controller details: %n%tDomain Controller Name: %1%n%tDomain Controller IP Address: %2 |
Domain Controller details: %n%tDomain Controller Name : %1%n%tDomain Controller IP Address : %2 |
| 0xB00014BD | Computer details: %n%tComputer role: %1%n%tNetwork name: %2 |
Computer details: %n%tComputer role : %1%n%tNetwork name : %2 |
| 0xB00014BE | Account details: %n%tAccount Name: %1%n%tAccount Domain Name: %2%n%tDC Name: %3%n%tDC Domain Name: %4 |
Account details: %n%tAccount Name : %1%n%tAccount Domain Name : %2%n%tDC Name : %3%n%tDC Domain Name : %4 |
| 0xB00014BF | The loopback policy processing mode is %1. |
The loopback policy processing mode is %1. |
| 0xB00014C0 | List of applicable Group Policy objects: %n%n%1 |
List of applicable Group Policy objects: %n%n%1 |
| 0xB00014C1 | The following Group Policy objects were not applicable because they were filtered out: %n%n%1 |
The following Group Policy objects were not applicable because they were filtered out : %n%n%1 |
| 0xB00014C2 | A %6 link was detected. The Estimated bandwidth is %1 kbps. The slow link threshold is %3 kbps. |
A %6 link was detected. The Estimated bandwidth is %1 kbps. The slow link threshold is %3 kbps. |
| 0xB00014C3 | Next policy processing for %1 will be attempted in %2 %3. |
Next policy processing for %1 will be attempted in %2 %3. |
| 0xB00014C8 | %1 |
%1 |
| 0xB00014C9 | %1 Parameter: %2 |
%1 Parameter: %2 |
| 0xB00014CA | Group policy waited for %3 milliseconds for the network subsystem at computer boot. |
Group Policy waited for %3 milliseconds for the network subsystem at computer boot. |
| 0xB00014CC | Group Policy received the notification %1 from Winlogon for session %2. |
Group Policy received the notification %1 from Winlogon for session %2. |
| 0xB00014CD | Group Policy received %1 notification from Service Control Manager. |
Group Policy received %1 notification from Service Control Manager. |
| 0xB00014CE | Group Policy successfully discovered the Domain Controller in %1 milliseconds. |
Group Policy successfully discovered the Domain Controller in %1 milliseconds. |
| 0xB00014CF | Estimated network bandwidth on one of the connections: %1 kbps. |
Estimated network bandwidth on one of the connections: %1 kbps. |
| 0xB00014D3 | Service configuration update to standalone was attempted due to the presence of Group Policy client extension %1 that is not part of the operating system and completed with status %3. |
Service configuration update to standalone was attempted due to the presence of Group Policy client extension %1 that is not part of the operating system and completed with status %3. |
| 0xB00014D4 | Group policy waited for %3 milliseconds for the Direct Access CorpNet connectivity at computer boot. |
Group Policy waited for %3 milliseconds for the Direct Access CorpNet connectivity at computer boot. |
| 0xB00014DC | The Group Policy processing mode is %1. |
The Group Policy processing mode is %1. |
| 0xB00014E7 | Group policy session returned to winlogon. |
Group policy session returned to winlogon. |
| 0xB0001770 | Invalid Error Message. |
Invalid Error Message. |
| 0xB0001791 | Skipped %1 Extension based on Group Policy client-side processing rules. Refer to a Resultant Set of Policy report for more information. |
Skipped %1 Extension based on Group Policy client-side processing rules. Refer to a Resultant Set of Policy report for more information. |
| 0xB0001792 | Group Policy changed from synchronous foreground to asynchronous foreground based on slow link detection. |
Group Policy changed from synchronous foreground to asynchronous foreground based on slow link detection. |
| 0xB0001793 | %1 Extension deferred processing until next synchronous foreground. Refer to a Resultant Set of Policy report for more information. |
%1 Extension deferred processing until next synchronous foreground. Refer to a Resultant Set of Policy report for more information. |
| 0xB00018AA | Group policy bandwidth estimation failed. Group policy processing will continue. Assuming %6 link. |
Group Policy bandwidth estimation failed. Group Policy processing will continue. Assuming %6 link. |
| 0xB00018B0 | Warning: %1 Warning code %2. |
Warning: %1 Warning code %2. |
| 0xB00018B1 | Warning: %1 Parameter: %3 : Warning code %2. |
Warning: %1 Parameter: %3 : Warning code %2. |
| 0xB00018B3 | Group Policy dependency (%1) did not start. As a result, network related features of Group Policy such as bandwidth estimation and response to network changes will not work. |
Group Policy dependency (%1) did not start. As a result, network related features of Group Policy such as bandwidth estimation and response to network changes will not work. |
| 0xB00018BA | An unfinished invocation of the Group Policy Client Side Extension %1 from a previous instance of the Group Policy Service has been detected. This may indicate that the extension caused the Group Policy Client Service to terminate unexpectedly. |
An unfinished invocation of the Group Policy Client Side Extension %1 from a previous instance of the Group Policy Service was detected. This may indicate that the extension caused the Group Policy Client Service to terminate unexpectedly. |
| 0xB00018C1 | Group Policy network connection is via Direct Access. |
Group Policy network connection is via Direct Access. |
| 0xB00018C2 | Group Policy Winlogon status reporting has completed. |
Group Policy Winlogon status reporting has completed. |
| 0xB00018C3 | Group Policy Winlogon Start Shell handling completed. |
Group Policy Winlogon Start Shell handling completed. |
| 0xB00018C5 | A Group Policy setting was used to override the fast/slow link detection. |
A Group Policy setting was used to override the fast/slow link detection. |
| 0xB00018C6 | The network connection is using a WWAN device for connectivity. |
The network connection is using a WWAN device for connectivity. |
| 0xB00018C8 | Group Policy network status is slowlink during sync mode process. |
Group Policy detected a slow link during sync mode processing. |
| 0xB00018C9 | The contact to dc is time-out during group policy sync mode process. |
The connection to DC timed out during the Group Policy sync mode process. |
| 0xB00018CA | Group Policy switches sync mode process to async mode. |
Group Policy switched the sync mode process to async mode. |
| 0xB0001B69 | %3 %n%4%nThe call failed after %1 milliseconds. |
%3 %n%4%nThe call failed after %1 milliseconds. |
| 0xB0001B6A | Script for %3 failed in %1 seconds. |
Script for %3 failed in %1 seconds. |
| 0xB0001BCD | Group policy session completed with error. |
Group policy session completed with error. |
| 0xB0001BD6 | Group Policy could not get applicable GPOs from the domain controller. |
Group Policy could not get applicable GPOs from the domain controller. |
| 0xB0001C30 | Saved policies to the local datastore with error. |
Saved policies to the local datastore with error. |
| 0xB0001C31 | Loaded policies from the local datastore with error. |
Loaded policies from the local datastore with error. |
| 0xB0001C59 | Downloaded policies with error. |
Downloaded policies with error. |
| 0xB0001C98 | Error: %1 Error code %2. |
Error: %1 Error code %2. |
| 0xB0001C99 | Error: %1 Parameter: %3 : Error code %2. |
Error: %1 Parameter: %3 : Error code %2. |
| 0xB0001C9E | Group Policy failed to discover the Domain Controller details in %1 milliseconds. |
Group Policy failed to discover the Domain Controller details in %1 milliseconds. |
| 0xB0001F50 | %1 Extension (%2) requests a sync mode process. |
%1 Extension (%2) requests a sync mode process. |
| 0xB0002329 | This machine is configured to retrieve Group Policy files from a file share in an insecure way.%n%nUNC Path: %1%nMutual Authentication Enforced: %2%nIntegrity Enforced: %3%n%nGuidance: The UNC path contains log-on scripts and/or files that control system security policies. Microsoft recommends configuring Windows to require both mutual authentication and integrity when accessing files on this UNC path.%n%nFor details on configuring Windows machines to require additional security when accessing specific UNC paths, visit http://support.microsoft.com/kb/3000483. |
This machine is configured to retrieve Group Policy files from a file share in an insecure way.%n%nUNC Path: %1%nMutual Authentication Enforced: %2%nIntegrity Enforced: %3%n%nGuidance: The UNC path contains logon scripts and/or files that control system security policies. Microsoft recommends configuring Windows to require both mutual authentication and integrity when accessing files on this UNC path.%n%nFor details on configuring Windows machines to require additional security when accessing specific UNC paths, visit http://support.microsoft.com/kb/3000483. |
| 0xB0010FA0 | Starting computer boot policy processing for %2. %nActivity id: %1 |
Starting computer boot policy processing for %2. %nActivity id: %1 |
| 0xB0010FA1 | Starting user logon Policy processing for %2. %nActivity id: %1 |
Starting user logon Policy processing for %2. %nActivity id: %1 |
| 0xB0010FA2 | Starting policy processing due to network state change for computer %2. %nActivity id: %1 |
Starting policy processing due to network state change for computer %2. %nActivity id: %1 |
| 0xB0010FA3 | Starting policy processing due to network state change for user %2. %nActivity id: %1 |
Starting policy processing due to network state change for user %2. %nActivity id: %1 |
| 0xB0010FA4 | Starting manual processing of policy for computer %2. %nActivity id: %1 |
Starting manual processing of policy for computer %2. %nActivity id: %1 |
| 0xB0010FA5 | Starting manual processing of policy for user %2. %nActivity id: %1 |
Starting manual processing of policy for user %2. %nActivity id: %1 |
| 0xB0010FA6 | Starting periodic policy processing for computer %2. %nActivity id: %1 |
Starting periodic policy processing for computer %2. %nActivity id: %1 |
| 0xB0010FA7 | Starting periodic policy processing for user %2. %nActivity id: %1 |
Starting periodic policy processing for user %2. %nActivity id: %1 |
| 0xB0011B58 | Computer boot policy processing failed for %3 in %1 seconds. |
Computer boot policy processing failed for %3 in %1 seconds. |
| 0xB0011B59 | User logon policy processing failed for %3 in %1 seconds. |
User logon policy processing failed for %3 in %1 seconds. |
| 0xB0011B5A | Policy processing due to network state change failed for computer %3 in %1 seconds. |
Policy processing due to network state change failed for computer %3 in %1 seconds. |
| 0xB0011B5B | Policy processing due to network state change failed for user %3 in %1 seconds. |
Policy processing due to network state change failed for user %3 in %1 seconds. |
| 0xB0011B5C | Manual processing of policy failed for computer %3 in %1 seconds. |
Manual processing of policy failed for computer %3 in %1 seconds. |
| 0xB0011B5D | Manual processing of policy failed for user %3 in %1 seconds. |
Manual processing of policy failed for user %3 in %1 seconds. |
| 0xB0011B5E | Periodic policy processing failed for computer %3 in %1 seconds. |
Periodic policy processing failed for computer %3 in %1 seconds. |
| 0xB0011B5F | Periodic policy processing failed for user %3 in %1 seconds. |
Periodic policy processing failed for user %3 in %1 seconds. |
| 0xB0011F40 | Completed computer boot policy processing for %3 in %1 seconds. |
Completed computer boot policy processing for %3 in %1 seconds. |
| 0xB0011F41 | Completed user logon policy processing for %3 in %1 seconds. |
Completed user logon policy processing for %3 in %1 seconds. |
| 0xB0011F42 | Completed policy processing due to network state change for computer %3 in %1 seconds. |
Completed policy processing due to network state change for computer %3 in %1 seconds. |
| 0xB0011F43 | Completed policy processing due to network state change for user %3 in %1 seconds. |
Completed policy processing due to network state change for user %3 in %1 seconds. |
| 0xB0011F44 | Completed manual processing of policy for computer %3 in %1 seconds. |
Completed manual processing of policy for computer %3 in %1 seconds. |
| 0xB0011F45 | Completed manual processing of policy for user %3 in %1 seconds. |
Completed manual processing of policy for user %3 in %1 seconds. |
| 0xB0011F46 | Completed periodic policy processing for computer %3 in %1 seconds. |
Completed periodic policy processing for computer %3 in %1 seconds. |
| 0xB0011F47 | Completed periodic policy processing for user %3 in %1 seconds. |
Completed periodic policy processing for user %3 in %1 seconds. |
| 0xD0000001 | No need for synchronous |
No need for synchronous |
| 0xD0000002 | First policy refresh |
First policy refresh |
| 0xD0000003 | CSE requires foreground |
CSE requires foreground |
| 0xD0000004 | CSE returned error |
CSE returned error |
| 0xD0000005 | Forced synchronous refresh |
Forced synchronous refresh |
| 0xD0000006 | Synchronous policy |
Synchronous policy |
| 0xD0000007 | SKU |
SKU |
| 0xD0000008 | Scripts synchronous |
Scripts synchronous |
| 0xD0000009 | Synchronous due to internal processing error |
Synchronous due to internal processing error |
| 0xD000000A | Background |
Background |
| 0xD000000B | Foreground synchronous |
Foreground synchronous |
| 0xD000000C | Foreground asynchronous |
Foreground asynchronous |
| 0xD000000D | \"No loopback mode\" |
\"No loopback mode\" |
| 0xD000000E | \"Merge\" |
\"Merge\" |
| 0xD000000F | \"Replace\" |
\"Replace\" |
| 0xD0000010 | Start-up script |
Startup script |
| 0xD0000011 | Logon script |
Logon script |
| 0xD0000012 | Logoff script |
Logoff script |
| 0xD0000013 | Shutdown script |
Shutdown script |
| 0xD0000014 | User |
User |
| 0xD0000015 | Computer |
Computer |
| 0xD0000016 | CreateSession |
CreateSession |
| 0xD0000017 | Logon |
Logon |
| 0xD0000018 | Logoff |
Logoff |
| 0xD0000019 | StartShell |
StartShell |
| 0xD000001A | EndShell |
EndShell |
| 0xD000001B | Preshutdown |
Preshutdown |