Windows 10

  1. The processing of Group Policy failed. Windows attempted to query the list of Group Policy objects and exceeded the maximum ...
  2. The processing of Group Policy failed. Windows attempted to read the file %9 from a domain controller and was not successful. ...
  3. The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. ...
  4. The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object ...
  5. The processing of Group Policy failed. Windows could not authenticate to the Active Directory service on a domain controller. ...
  6. The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. ...
  7. The processing of Group Policy failed. Windows could not determine the computer account to enforce Group Policy settings. ...
  8. The processing of Group Policy failed. Windows could not determine the role of this computer. Role information (Workgroup, ...
  9. The processing of Group Policy failed. Windows could not determine the site associated for this computer, which is required ...
  10. The processing of Group Policy failed. Windows could not evaluate the Windows Management Instrumentation (WMI) filter for ...
  11. The processing of Group Policy failed. Windows could not locate the directory object %8. Group Policy settings will not be ...
  12. The processing of Group Policy failed. Windows could not obtain the list of Group Policy objects applicable for this computer ...
  13. The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by ...
  14. The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of ...
  15. The processing of Group Policy failed. Windows could not resolve the user name. This could be caused by one of more of the ...
  16. The processing of Group Policy failed. Windows could not search the Active Directory organization unit hierarchy. View the ...
  17. The processing of Group Policy was interrupted. Windows prematurely ended the discovery and enforcement of Group Policy settings ...
  18. The processor architecture of this computer is not the same as that of the computer that was backed up. For example, system ...
  19. The processor architecture or OS version of Windows Recovery Environment is not the same as that of the computer that was ...
  20. The processor architecture value of {0} is not supported. Run the New-ModuleManifest command again, specifying one of the ...
  21. The processor cycle counter on processor %2 has been probed by processor %1. A counter delta of %3 was detected. The approximate ...
  22. The processor cycle counter on processor %2 was synchronized against processor %1 using an adjustment of %4 cycles on attempt ...
  23. The processor family type. For example, values include \"Pentium(R) processor with MMX(TM) technology\" (14) and \"68040\" ...
  24. The Processor Information performance counter set consists of counters that measure aspects of processor activity. The processor ...
  25. The processor limit specified for virtual machine '%1' is out of range. The range is %3 through %4. (Virtual machine ID %2) ...
  26. The Processor performance object consists of counters that measure aspects of processor activity. The processor is the part ...
  27. The processor settings for virtual machine '%1' are not compatible with physical computer '%3'. To migrate this virtual machine, ...
  28. The processor topology specified for the virtual machine cannot be supported by this host. For instance, this can happen ...
  29. The processor's cycle counters have been successfully synchronized from processor %1 within acceptable operating thresholds. ...
  30. The ProcessorId property contains processor-specific information that describes the processor's features. For x86 class CPUs, ...
  31. The ProcessStartupInformation parameter represents the startup configuration of a Win32 process. It includes information ...
  32. The product key entered does not match any of the Windows images available for installation. Enter a different product key.%0 ...
  33. The product key should be with the box the DVD came in or on your email receipt. When you connect to the Internet, we'll ...
  34. The product key you entered appears to be a default product key and can't be used to activate this edition of Windows. Please ...
  35. The product key you entered can be used only in certain countries or regions. Either activate %1 where you bought it or buy ...
  36. The product key you entered can only be used to create an activation infrastructure. Please enter a different product key ...
  37. The product key you entered can't be used to activate Windows on this PC, it can only be used to set up a key management ...
  38. The product key you have entered appears to be a default product key and cannot be used for activation. Type a different ...
  39. The product key you have entered does not appear to be a valid %12 product key. Please check your product key, and type it ...
  40. The product key you have entered will not work with this edition of %12. You must either run %12 Setup or enter a %21 product ...
  41. The ProductType property indicates additional information about the system. This member can be one of the following values: ...
  42. The profile association list is invalid and could not be loaded. The profile association list for this device was not changed. ...
  43. The Profile property specifies a directory path to the user's profile. This value can be a null string, a local absolute ...
  44. The profile was applied on the network adapter. Network Adapter: %2 Interface GUID: %1 Profile Type: %3 Profile Content: ...
  45. The ProgID for a protocol handler cannot be obtained, and the protocol handler registration is invalid. Reregister the protocol ...
  46. The ProgId property contains a programmatic identifier associated with the COM component. The format of a ProgID is . . . ...
  47. The program %1 version %2 stopped interacting with Windows and was closed. To see if more information about the problem is ...
  48. The program %2, with the assigned process ID %1, could not authenticate locally by using the target name %3. The target name ...
  49. The program %2, with the assigned Process ID %1, supplied a NULL or empty target name for the pszTargetName parameter when ...
  50. The program can't find definition files that help detect unwanted software. Check for updates to the definition files, and ...
  51. The program cannot open the required dialog box because it cannot determine whether the computer named "%1" is joined to ...
  52. The Program Compatibility Assistant attempted to connect an event for process ID %1, but the Program Compatibility Assistant ...
  53. The Program Compatibility Assistant was invoked due to an unsigned driver install. This version of Windows requires all drivers ...
  54. The Program Compatibility Assistant was invoked to correct a compatibility problem. Information about the application is ...
  55. The Program Compatibility Assistant was invoked to correct a compatibility problem. Information about the application is ...
  56. The Program Compatibility Assistant was invoked to correct a compatibility problem. Information about the application is ...
  57. The Program Compatibility Assistant was invoked to correct a compatibility problem. Information about the application is ...
  58. The Program Compatibility Assistant was not invoked as the application executed correctly. Information about the application ...
  59. The Program Compatibility Assistant was not invoked because the application has been already handled previously. Information ...
  60. The Program Compatibility Assistant was requested to monitor %1, but ignored the request because of the extension of the ...
  61. The Program Compatibility Assistant was requested to monitor %1, but ignored the request because the application already ...
  62. The Program Compatibility Assistant was requested to monitor %1, but ignored the request because the application compatibility ...
  63. The Program Compatibility Assistant was requested to monitor %1, but ignored the request because the application depends ...
  64. The Program Compatibility Assistant was requested to monitor %1, but ignored the request because the application has a compatibility ...
  65. The Program Compatibility Assistant was requested to monitor %1, but ignored the request because the application has been ...
  66. The Program Compatibility Assistant was requested to monitor %1, but ignored the request because the application is a 64-bit ...
  67. The Program Compatibility Assistant was requested to monitor %1, but ignored the request because the application is excluded ...
  68. The Program Compatibility Assistant was requested to monitor %1, but ignored the request because the application is on a ...
  69. The Program Compatibility Assistant was requested to monitor %1, but ignored the request because the application is protected ...
  70. The Program Compatibility Assistant was requested to monitor %1, but ignored the request because the executable has a current ...
  71. The Program Compatibility Assistant was requested to monitor %1, but ignored the request because the executable has a UAC ...
  72. The Program Compatibility Assistant was requested to monitor %1, but ignored the request because the PCA is disabled by group ...
  73. The Program Compatibility Troubleshooter queried the application genome for information about an application. Results are ...
  74. The Program Compatibility Troubleshooter queried the Compatibility Online Service for information about an application. Results ...
  75. The Program Compatibility Troubleshooter was invoked to correct a compatibility problem. Information about the application ...