Windows 7

  1. The command cannot be run because no argument has been supplied for the OutputFormat parameter. Specify one of the following ...
  2. The command cannot be run because the File parameter requires a file path. Supply a path for the File parameter and then ...
  3. The command cannot be used to configure the service '{0}' because access to computer '{1}' is denied. Run PowerShell as admin ...
  4. The command cannot disable System Restore on the {0} drive. You may not have sufficient permissions to perform this operation. ...
  5. The command cannot find the job because the {0} name was not found. Verify the value of the Name parameter, and then try ...
  6. The command cannot find the job because the {0} session identifier was not found. Verify the value of the Id parameter and ...
  7. The command cannot find the job with the {0} instance identifier because the identifier was not found. Verify the value of ...
  8. The command cannot remove the job because it does not exist or because it is a child job. Child jobs can be removed only ...
  9. The command cannot remove the job with the {0} session identifier and the {1} instance identifier because the job is not ...
  10. The command cannot remove the job with the {0} session identifier and the {1} name because the job is not finished. To remove ...
  11. The command cannot remove the job with the {0} session identifier because the job is not finished. To remove the job, first ...
  12. The command cannot restore the computer because "{0}" has not been set as valid restore point. Enter a valid restore point ...
  13. The command cannot retrieve the jobs of the specified computers. The ComputerName parameter can be used only with jobs creating ...
  14. The command cannot turn off the restore computer infrastructure because the supplied drive is not valid. Enter a valid drive ...
  15. The command cannot turn on the restore computer infrastructure on the specified computer because the supplied drive is not ...
  16. The command could not be retrieved because the ArgumentList parameter can be specified only when retrieving a single cmdlet ...
  17. The command name '{0}' contains one or more of the following restricted characters: # , ( ) { } - / \ $ ^ ; : " ' < > | ? ...
  18. The command name '{0}' includes an unapproved verb which might make it less discoverable. The suggested alternative verbs ...
  19. The command OleInitialize failed to run. Your computer might be low on memory. Close any open programs and then try again. ...
  20. The Command parameter contains the name of the command, batch program, or binary file (along with command line parameters) ...
  21. The Command property contains the name of the command, batch program, or binary file (along with command line arguments) ...
  22. The Command property indicates the string representing the command line run by the startup command. Example: c:\winnt\ otepad.exe ...
  23. The command specified is unknown or not supported when running DISM.exe against a Windows Vista with Service Pack 1 or a ...
  24. The command used to access Trusted Platform Module (TPM) information has been blocked on this computer. Contact your domain ...
  25. The command used to change Trusted Platform Module (TPM) owner password has been blocked on this computer. How do I allow ...
  26. The command used to clear the Trusted Platform Module (TPM) has been blocked on this computer. How do I allow TPM commands? ...
  27. The command used to turn off the Trusted Platform Module (TPM) has been blocked on this computer. How do I allow TPM commands? ...
  28. The command used to turn on the Trusted Platform Module (TPM) has been blocked on this computer. How do I allow TPM commands? ...
  29. The command {0} was not found, but does exist in the current location. Windows PowerShell doesn't load commands from the ...
  30. The command {0} was not found, but does exist in the current location. Windows PowerShell doesn't load commands from the ...
  31. The command-line is missing a required servicing command. For more information, refer to the help by running DISM.exe /Image= ...
  32. The command-line is missing a required servicing command. For more information, refer to the help by running DISM.exe /Online ...
  33. The CommandLine parameter specifies the command line to execute. The system adds a null character to the command line, trimming ...
  34. The Comment parameter specifies a message to display in the shutdown dialog box and also stored as a comment in the event ...
  35. The common name of the restored CA certificate: '%ws' does not match the common name expected by Active Directory Certificate ...
  36. The Communities rating feature uses Windows Live ID to help ensure that the people who post messages in newsgroups are who ...
  37. The comparison operation specified by expression "%1" is invalid. To use comparison operations, specify "$(op)(value)", where ...
  38. The compiled schema file (%1) is invalid. This is typically due to an upgrade just occurring or the file is corrupt. The ...
  39. The complete text of the event received is below. More information on IPMI events can be found at http://go.microsoft.com/fwlink/events.asp. ...
  40. The complexType NOLOC:S1 contains a scalar list that is not alone. If other settings are located at the same location it ...
  41. The complexType NOLOC:S1 has multiple list type members. If this type is used for legacy settings it may cause unpredictable ...
  42. The component "%1" was not found in the writer components list. Aborting backup . Check the syntax of the component name. ...
  43. The component "%1" was not included in the backup. Aborting backup . Review the component and subcomponent definitions, and ...
  44. The component attempted to make a cross-context call between invocations of EnterTransactionScopeand ExitTransactionScope. ...
  45. The component DLL could not be loaded. Make sure that all required application runtime files or other dependent DLLs are ...
  46. The component DLL's self-registration routine failed. The DllRegisterServer function failed or the routine did not register ...
  47. The component information in the application file is out of date. A component CLSID or IID has been re-generated since the ...
  48. The component is already configured on the requested computer. The component is either installed in a application or configured ...
  49. The component made a call to EnterTransactionScope, but did not make a corresponding call to ExitTransactionScope before ...
  50. The component move was disallowed, because the source or destination application is either a system application or currently ...
  51. The component settings file for the target edition was not found. The upgrade cannot proceed. For more information, review ...
  52. The component's CLSID is not registered. The component may have been unregistered, or the component registration information ...
  53. The component's progID information is invalid. The component's progID information does not match the component's CLSID information. ...
  54. The Compress method compresses the logical file (or directory) specified in the object path. Compress returns an integer ...
  55. The Compressed property indicates whether the logical volume exists as a single compressed entity, such as a DoubleSpace ...
  56. The CompressEx method compresses the logical file (or directory) specified in the object path. CompressEx returns an integer ...
  57. The Compression property specifies whether hardware data compression is enabled or disabled. Values: 1 (true) or 0 (false). ...
  58. The CompressionMethod property is a free form string indicating the algorithm or tool used to compress the logical file. ...
  59. The computed account identifier is invalid because it is out of the range of the current account-identifier pool belonging ...
  60. The computer %1 is a domain controller. This snap-in cannot be used on a domain controller. Domain accounts are managed with ...
  61. The computer %1 tried to connect to the server %2 using the trust relationship established by the %3 domain. However, the ...
  62. The computer '{0}' could not be resolved. Make sure you typed the machine name correctly and that you have network access. ...
  63. The computer '{0}' does not have the Failover Clustering feature installed. Use Server Manager to install the feature on ...
  64. The computer '{0}' is unreachable. Please ensure that this server is running. Also, ensure that this server's firewall, if ...
  65. The computer '{0}' reports that it is really {1}. Please type the complete name or IP address of the machine. If this problem ...
  66. The computer (NetBIOS) name {0} contains illegal characters. A computer (NetBIOS) name can consist of the following standard ...
  67. The computer (NetBIOS) name {0} contains nonstandard characters. A computer (NetBIOS) name can contain a combination of the ...
  68. The computer account for license server %s cannot be added to the Terminal Server License Servers group in Active Directory ...
  69. The computer account for license server %s cannot be added to the Terminal Server License Servers group in the Active Directory ...
  70. The computer account for license server %s has been added to the Terminal Server License Severs group in Active Directory ...
  71. The computer account for license server %s or the Network Service account cannot be added to the Terminal Server License ...
  72. The computer account for license server %s or the Network Service account cannot be added to the Terminal Server License ...
  73. The computer account for license server %s or the Network Service account has been added to the Terminal Server License Severs ...
  74. The computer account for resource '%1' failed to be renamed from %2 to %3 using Domain Controller %4. The associated error ...
  75. The computer account for the Remote Desktop license server cannot be added to the Terminal Server License Servers group in ...