Windows 8

  1. The private key module encountered a mismatch between the CSP type and the persisted private key information. The configuration ...
  2. The private key module expects a single issued principal in the server licensor certificate of a domain licensor certificate. ...
  3. The private key module failed to initialize and cannot access its internal cache. Your system configuration may be corrupted. ...
  4. The private key module failed to initialize and it cannot access the database. The configuration database or the registry ...
  5. The private key module received a request for a private key value that did not have a corresponding entry in the trusted ...
  6. The Private Key module received a request for a private key value that didn't match the public key value recorded in the ...
  7. The private key module requires a password when importing a key pair. The key file you are attempting to import may be corrupted. ...
  8. The private key module requires an ID value when exporting a key pair. The configuration database or the registry may be ...
  9. The private key module requires key information when importing a key pair to establish a trusted publishing domain. The key ...
  10. The problem might be that either this document has invalid permissions or the Windows Rights Management Client software must ...
  11. The process %1 has initiated the %5 of computer %2 on behalf of user %7 for the following reason: %3 Reason Code: %4 Shutdown ...
  12. The process %1 with the process identifier (PID) %2 exceeded its committed memory limit of %3 megabytes. As a result, it ...
  13. The process %1 with the process identifier (PID) %2 exceeded its committed memory limit of %3 megabytes. As a result, it ...
  14. The process %1 with the process identifier (PID) %2 exceeded its committed memory limit of %3 megabytes. As a result, the ...
  15. The process %1 with the process identifier (PID) %2 exceeded its committed memory limit of %3 megabytes. As a result, the ...
  16. The process %1 with the process identifier (PID) %2 exceeded its committed memory limit of %3 megabytes. However, it was ...
  17. The process %1 with the process identifier (PID) %2 exceeded its committed memory limit of %3 megabytes. However, it was ...
  18. The process '%1' was terminated by the process '%2' with termination code %3. The creation time for the exiting process was ...
  19. The Process Address Space performance object consists of counters that monitor memory allocation and use for a selected process. ...
  20. The process cannot convert a server feature entry to PSObject, because the entry is in the wrong configuration file format. ...
  21. The process identifier (PID) corresponding to the chosen process. A value of "Various" indicates the PID for this process ...
  22. The Process Image Dump feature allows the user to dump a static image of this application. This image can be loaded in the ...
  23. The Process Matching Criteria - "Residual" cannot be referred to by any policy. Please remove the reference to "Residual" ...
  24. The Process performance object consists of counters that monitor running application program and system processes. All the ...
  25. The processing of Group Policy failed because of a system allocation failure. Please ensure the computer is not running low ...
  26. The processing of Group Policy failed because of an internal system error. Please see the Group Policy operational log for ...
  27. The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient ...
  28. The processing of Group Policy failed due to an internal error. Please look into the Group Policy operational log for the ...
  29. The processing of Group Policy failed. Windows attempted to query the list of Group Policy objects and exceeded the maximum ...
  30. The processing of Group Policy failed. Windows attempted to read the file %9 from a domain controller and was not successful. ...
  31. The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. ...
  32. The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object ...
  33. The processing of Group Policy failed. Windows could not authenticate to the Active Directory service on a domain controller. ...
  34. The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. ...
  35. The processing of Group Policy failed. Windows could not determine the computer account to enforce Group Policy settings. ...
  36. The processing of Group Policy failed. Windows could not determine the role of this computer. Role information (Workgroup, ...
  37. The processing of Group Policy failed. Windows could not determine the site associated for this computer, which is required ...
  38. The processing of Group Policy failed. Windows could not evaluate the Windows Management Instrumentation (WMI) filter for ...
  39. The processing of Group Policy failed. Windows could not locate the directory object %8. Group Policy settings will not be ...
  40. The processing of Group Policy failed. Windows could not obtain the list of Group Policy objects applicable for this computer ...
  41. The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by ...
  42. The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of ...
  43. The processing of Group Policy failed. Windows could not resolve the user name. This could be caused by one of more of the ...
  44. The processing of Group Policy failed. Windows could not search the Active Directory organization unit hierarchy. View the ...
  45. The processing of Group Policy was interrupted. Windows prematurely ended the discovery and enforcement of Group Policy settings ...
  46. The processor architecture of this computer is not the same as that of the computer that was backed up. For example, system ...
  47. The processor architecture or OS version of Windows Recovery Environment is not the same as that of the computer that was ...
  48. The processor architecture value of {0} is not supported. Run the New-ModuleManifest command again specifying one of the ...
  49. The processor cycle counter on processor %2 has been probed by processor %1. A counter delta of %3 was detected. The approximate ...
  50. The processor cycle counter on processor %2 was synchronized against processor %1 using an adjustment of %4 cycles on attempt ...
  51. The Processor Information performance counter set consists of counters that measure aspects of processor activity. The processor ...
  52. The processor limit specified for virtual machine '%1' is out of range. The range is %3 through %4. (Virtual machine ID %2) ...
  53. The processor manufacturer is not consistent across all of the nodes. This is important because Hyper-V requires that the ...
  54. The Processor performance object consists of counters that measure aspects of processor activity. The processor is the part ...
  55. The processor settings for virtual machine '%1' are not compatible with physical computer '%3'. To migrate this virtual machine, ...
  56. The processor topology specified for the virtual machine cannot be supported by this host. For instance, this can happen ...
  57. The processor type '%1!s!' is not supported by this assessment. Try running the assessment on supported processor hardware. ...
  58. The processor version is not consistent across all the nodes. This is important because Hyper-V may not be able to live migrate ...
  59. The processor's cycle counters have been successfully synchronized from processor %1 within acceptable operating thresholds. ...
  60. The processors specified in resource allocation policy cannot be found. Ensure that the processors exist, and then try again. ...
  61. The product key entered does not match any of the Windows images available for installation. Enter a different product key.%0 ...
  62. The product key has been installed. The product may need to be activated. Select Activate Product and click Next to complete ...
  63. The product key you entered appears to be a default product key and can't be used to activate this edition of Windows. Please ...
  64. The product key you entered can be used only in certain countries or regions. Either activate %1 where you bought it or buy ...
  65. The product key you entered can only be used to create an activation infrastructure. Please enter a different product key ...
  66. The product key you have entered appears to be a default product key and cannot be used for activation. Type a different ...
  67. The product key you have entered does not appear to be a valid %12 product key. Please check your product key, and type it ...
  68. 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 ...
  69. The profile association list is invalid and could not be loaded. The profile association list for this device was not changed. ...
  70. The profile cannot be created. Verify that the IP-HTTPS certificate is valid and that you have write permissions for the ...
  71. The profile should be edited using the language version of Windows that matches the profile. Do you want to continue editing ...
  72. The profile source for %s cannot be found. If you delete %s from this profile then you will be unable to re-merge it into ...
  73. The profile was applied on the network adapter. Network Adapter: %2 Interface GUID: %1 Profile Type: %3 Profile Content: ...
  74. The ProgID for a protocol handler cannot be obtained, and the protocol handler registration is invalid. Reregister the protocol ...
  75. The program %1 version %2 stopped interacting with Windows and was closed. To see if more information about the problem is ...