Windows 8

  1. The command cannot remove the job with the job ID {0} and the instance identifier {1} because the job is not finished. To ...
  2. The command cannot remove the job with the job ID {0} and the name {1} because the job is not finished. To remove the job, ...
  3. The command cannot remove the job with the job ID {0} because the job is not finished. To remove the job, first stop the ...
  4. The command cannot restore the computer because "{0}" has not been set as valid restore point. Enter a valid restore point ...
  5. The command cannot retrieve the jobs of the specified computers. The ComputerName parameter can be used only with jobs creating ...
  6. The command cannot turn off the restore computer infrastructure because the supplied drive is not valid. Enter a valid drive ...
  7. The command cannot turn on the restore computer infrastructure on the specified computer because the supplied drive is not ...
  8. The command could not be retrieved because the ArgumentList parameter can be specified only when retrieving a single cmdlet ...
  9. The command could not find computer "{0}" in Active Directory; verify that the computer name is correct. You can still create ...
  10. The command found the request information defined by the RequestGuid parameter, but the original request is of a different ...
  11. The command is producing an excessive amount of output that cannot be sent to the Windows PowerShell Web Access client. The ...
  12. The command is trying to display a very large amount of data that cannot be sent to the Windows PowerShell Web Access client. ...
  13. The command name '{0}' from the module '{1}' contains one or more of the following restricted characters: # , ( ) { } - / ...
  14. The command name '{0}' is ambiguous and cannot be processed. To use this command, specify a module qualified name such as: ...
  15. The command OleInitialize failed to run. Your computer might be low on memory. Close any open programs and then try again. ...
  16. The command used to access Trusted Platform Module (TPM) information has been blocked on this computer. Contact your domain ...
  17. The command used to change Trusted Platform Module (TPM) owner password has been blocked on this computer. How do I allow ...
  18. The command used to clear the Trusted Platform Module (TPM) has been blocked on this computer. How do I allow TPM commands? ...
  19. The command used to turn off the Trusted Platform Module (TPM) has been blocked on this computer. How do I allow TPM commands? ...
  20. The command used to turn on the Trusted Platform Module (TPM) has been blocked on this computer. How do I allow TPM commands? ...
  21. The command {0} was not found, but does exist in the current location. Windows PowerShell does not load commands from the ...
  22. The command {0} was not found, but does exist in the current location. Windows PowerShell does not load commands from the ...
  23. The command-line is missing a required servicing command. For more information, refer to the help by running DISM.exe /Image= ...
  24. The command-line is missing a required servicing command. For more information, refer to the help by running DISM.exe /Online ...
  25. The common name of the restored CA certificate: '%ws' does not match the common name expected by Active Directory Certificate ...
  26. The compatibility of Server for Network File System is limited because it performs identity mapping by using a deprecated, ...
  27. The complete text of the event received is below. More information on IPMI events can be found at http://go.microsoft.com/fwlink/?linkid=47400. ...
  28. The component "%1" was not found in the writer components list. Aborting backup . Check the syntax of the component name. ...
  29. The component "%1" was not included in the backup. Aborting backup . Review the component and subcomponent definitions, and ...
  30. The component attempted to make a cross-context call between invocations of EnterTransactionScopeand ExitTransactionScope. ...
  31. The component DLL could not be loaded. Make sure that all required application runtime files or other dependent DLLs are ...
  32. The component DLL's self-registration routine failed. The DllRegisterServer function failed or the routine did not register ...
  33. The component information in the application file is out of date. A component CLSID or IID has been re-generated since the ...
  34. The component is already configured on the requested computer. The component is either installed in a application or configured ...
  35. The component made a call to EnterTransactionScope, but did not make a corresponding call to ExitTransactionScope before ...
  36. The component move was disallowed, because the source or destination application is either a system application or currently ...
  37. The component registration information could not be read from an unknown root\virtualization\v2:%3 WMI object: %1 (%2). If ...
  38. The component registration information could not be read from the %3 WMI object: %1 (%2). If this error persists, try re-installing ...
  39. The component settings file for the target edition was not found. The upgrade cannot proceed. For more information, review ...
  40. The component's CLSID is not registered. The component may have been unregistered, or the component registration information ...
  41. The component's progID information is invalid. The component's progID information does not match the component's CLSID information. ...
  42. The computed account identifier is invalid because it is out of the range of the current account-identifier pool belonging ...
  43. The computer "{0}" does not support a RemoteFX 3D video adapter. To use the virtual machine on this computer, remove the ...
  44. The computer %1 is a domain controller. This snap-in cannot be used on a domain controller. Domain accounts are managed with ...
  45. The computer %1 tried to connect to the server %2 using the trust relationship established by the %3 domain. However, the ...
  46. The computer '{0}' could not be resolved. Make sure you typed the machine name correctly and that you have network access. ...
  47. The computer '{0}' is unreachable. Please ensure that this server is running. Also, ensure that this server's firewall, if ...
  48. The computer '{0}' reports that it is really {1}. Please type the complete name or IP address of the machine. If this problem ...
  49. The computer (NetBIOS) name {0} contains illegal characters. A computer (NetBIOS) name can consist of the following standard ...
  50. The computer (NetBIOS) name {0} contains nonstandard characters. A computer (NetBIOS) name can contain a combination of the ...
  51. The computer account for license server %s cannot be added to the Terminal Server License Servers group in Active Directory ...
  52. The computer account for license server %s cannot be added to the Terminal Server License Servers group in the Active Directory ...
  53. The computer account for license server %s has been added to the Terminal Server License Severs group in Active Directory ...
  54. The computer account for license server %s or the Network Service account cannot be added to the Terminal Server License ...
  55. The computer account for license server %s or the Network Service account cannot be added to the Terminal Server License ...
  56. The computer account for license server %s or the Network Service account has been added to the Terminal Server License Severs ...
  57. The computer account for resource '%1' failed to be renamed from %2 to %3 using Domain Controller %4. The associated error ...
  58. The computer account for the Remote Desktop license server could not be added to the Terminal Server License Servers group ...
  59. The computer account for the Remote Desktop license server has been removed from the Terminal Server License Servers group ...
  60. The computer account for the Remote Desktop license server was successfully added to the Terminal Server License Servers ...
  61. The computer account for this Remote Desktop license server or Network Service account has been added to the Terminal Server ...
  62. The computer attempted to validate the credentials for an account. Authentication Package: %1 Logon Account: %2 Source Workstation: ...
  63. The computer belongs to the %1 domain. It is recommended that you use the MoveTree utility to move the msmq (MSMQ Configuration) ...
  64. The computer cannot be joined to the domain "%1" because there is not enough disk space on either the computer or a domain ...
  65. The computer doesn't appear to have a microphone connected to it that supports Speech Recognition. Please connect a supported ...
  66. The computer doesn't appear to have a microphone connected to it. Please connect a microphone to the computer and try again. ...
  67. The computer failed to join the domain "%1". Please contact your domain administrator and indicate that the computer failed ...
  68. The computer failed to join the domain "%1". Please do one of the following: - Configure the computer to update its primary ...
  69. The computer firmware (BIOS) is not compatible with Windows. Contact your computer manufacturer for an update to the computer ...
  70. The computer group you just attempted to use has been removed from the database by another party. Adding a child group to ...
  71. The computer group you just requested has been removed from the database by another party. It will be removed from the snap-in. ...
  72. The computer has been joined to a failover cluster. The File Server Resource Manager service (SRMSVC) must be restarted to ...
  73. The computer hosting Active Directory Certificate Services cannot be contacted. It is either unavailable or does not exist. ...
  74. The computer hosting the file or folder does not support setting secure properties. This can occur if the computer is running ...
  75. The computer is a domain controller undergoing upgrade. You must complete the Active Directory Installation Wizard before ...