Windows 8.1

  1. The COM+ explorer was unable to locate information required to perform the requested action. This may be caused by running ...
  2. The COM+ sub system is suppressing duplicate event log entries for a duration of %1 seconds. The suppression timeout can ...
  3. The combination of IP address and subnet mask is invalid. All of the bits in the host address portion of the IP address are ...
  4. The combination of IP address and subnet mask is invalid. All of the bits in the host address portion of the IP address are ...
  5. The combination of IP address and subnet mask is invalid. All of the bits in the network address portion of the IP address ...
  6. The command cannot be completed because a domain with the following LDAP path cannot be found: "{0}". The Path parameter ...
  7. The command cannot be completed because a GPO that is named "{0}" was not found in the {1} domain. Make sure that the GPO ...
  8. The command cannot be completed because a GPO with ID {0} was not found in the {1} domain. Make sure that the GUID parameter ...
  9. The command cannot be completed because an Active Directory container with the following LDAP path cannot be found: "{0}". ...
  10. The command cannot be completed because an organizational unit (OU) with the following LDAP path cannot be found: "{0}". ...
  11. The command cannot be completed because the LDAP path that is specified by the Target parameter is not valid: "{0}". For ...
  12. The command cannot be completed because the ValueName parameter was not provided. If you want to set the default value, specify ...
  13. The command cannot be completed. Script invocation is not supported in this session configuration. This can occur if the ...
  14. The command cannot be executed. The Base Filtering Engine (BFE) service is not running. You can start the BFE service by ...
  15. The command cannot be run because no argument has been supplied for the OutputFormat parameter. Specify one of the following ...
  16. The command cannot be run because the File parameter requires a file path. Supply a path for the File parameter and then ...
  17. The command cannot be run because using the AsHashTable parameter with more than one property requires adding the AsString ...
  18. The command cannot be used to configure the service '{0}' because access to computer '{1}' is denied. Run Windows PowerShell ...
  19. The command cannot disable System Restore on the {0} drive. You may not have sufficient permissions to perform this operation. ...
  20. The command cannot find a job with the instance identifier {0}. Verify the value of the InstanceId parameter, and then try ...
  21. The command cannot find the job because the job name {0} was not found. Verify the value of the Name parameter, and then ...
  22. The command cannot remove the job because it does not exist or because it is a child job. Child jobs can be removed only ...
  23. The command cannot remove the job with the job ID {0} and the instance identifier {1} because the job is not finished. To ...
  24. 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, ...
  25. The command cannot remove the job with the job ID {0} because the job is not finished. To remove the job, first stop the ...
  26. The command cannot restore the computer because "{0}" has not been set as valid restore point. Enter a valid restore point ...
  27. The command cannot retrieve the jobs of the specified computers. The ComputerName parameter can be used only with jobs created ...
  28. The command cannot turn off the restore computer infrastructure because the supplied drive is not valid. Enter a valid drive ...
  29. The command cannot turn on the restore computer infrastructure on the specified computer because the supplied drive is not ...
  30. The command could not be retrieved because the ArgumentList parameter can be specified only when retrieving a single cmdlet ...
  31. The command could not find computer "{0}" in Active Directory; verify that the computer name is correct. You can still create ...
  32. The command could not update Help topics for the Windows PowerShell core modules, or for any modules in the $pshome\Modules ...
  33. The command found the request information defined by the RequestGuid parameter, but the original request is of a different ...
  34. The command is producing an excessive amount of output that cannot be sent to the Windows PowerShell Web Access client. The ...
  35. The command is trying to display a very large amount of data that cannot be sent to the Windows PowerShell Web Access client. ...
  36. The command name '{0}' from the module '{1}' contains one or more of the following restricted characters: # , ( ) { } - / ...
  37. The command name '{0}' is ambiguous and cannot be processed. To use this command, specify a module qualified name such as: ...
  38. The command OleInitialize failed to run. Your computer might be low on memory. Close any open programs and then try again. ...
  39. The Command parameter contains the name of the command, batch program, or binary file (along with command line parameters) ...
  40. The Command property contains the name of the command, batch program, or binary file (along with command line arguments) ...
  41. The Command property indicates the string representing the command line run by the startup command. Example: c:\winnt\ otepad.exe ...
  42. The command specified is unknown or not supported when running DISM.exe against this target image. For more information, ...
  43. The command used to access Trusted Platform Module (TPM) information has been blocked on this computer. Contact your domain ...
  44. The command used to change Trusted Platform Module (TPM) owner password has been blocked on this computer. How do I allow ...
  45. The command used to clear the Trusted Platform Module (TPM) has been blocked on this computer. How do I allow TPM commands? ...
  46. The command used to turn off the Trusted Platform Module (TPM) has been blocked on this computer. How do I allow TPM commands? ...
  47. The command used to turn on the Trusted Platform Module (TPM) has been blocked on this computer. How do I allow TPM commands? ...
  48. The command {0} of the PS module {1} does not implement the key property {2} mentioned in the corresponding MOF schema file ...
  49. The command {0} of the PS module {1} does not implement the write property {2} mentioned in the corresponding MOF schema ...
  50. The command {0} was not found, but does exist in the current location. Windows PowerShell does not load commands from the ...
  51. The command {0} was not found, but does exist in the current location. Windows PowerShell does not load commands from the ...
  52. The command-line is missing a required servicing command. For more information, refer to the help by running DISM.exe /Image= ...
  53. The command-line is missing a required servicing command. For more information, refer to the help by running DISM.exe /Online ...
  54. The CommandLine parameter specifies the command line to execute. The system adds a null character to the command line, trimming ...
  55. The Comment parameter specifies a message to display in the shutdown dialog box and also stored as a comment in the event ...
  56. The common name of the restored CA certificate: '%ws' does not match the common name expected by Active Directory Certificate ...
  57. The common name on the certificate that is bound to the WSS Certificate Web Service website does not match the server name ...
  58. The Communities rating feature uses Windows Live ID to help ensure that the people who post messages in newsgroups are who ...
  59. The comparator to use, and values to compare Fqdn with. The first element is the comparator {EQ, NE, Isl, Insl}, and subsequent ...
  60. The compatibility of Server for Network File System is limited because it performs identity mapping by using a deprecated, ...
  61. The compatibility section of the app manifest helps the operating system provide your app the proper compatibility behavior ...
  62. 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. ...
  63. The complexType NOLOC:S1 contains a scalar list that is not alone. If other settings are located at the same location it ...
  64. The complexType NOLOC:S1 has multiple list type members. If this type is used for legacy settings it may cause unpredictable ...
  65. The component "%1" was not found in the writer components list. Aborting backup . Check the syntax of the component name. ...
  66. The component "%1" was not included in the backup. Aborting backup . Review the component and subcomponent definitions, and ...
  67. The component attempted to make a cross-context call between invocations of EnterTransactionScopeand ExitTransactionScope. ...
  68. The component DLL could not be loaded. Make sure that all required application runtime files or other dependent DLLs are ...
  69. The component DLL's self-registration routine failed. The DllRegisterServer function failed or the routine did not register ...
  70. The component information in the application file is out of date. A component CLSID or IID has been re-generated since the ...
  71. The component is already configured on the requested computer. The component is either installed in a application or configured ...
  72. The component made a call to EnterTransactionScope, but did not make a corresponding call to ExitTransactionScope before ...
  73. The component move was disallowed, because the source or destination application is either a system application or currently ...
  74. The component registration information could not be read from an unknown root\virtualization\v2:%3 WMI object: %1 (%2). If ...
  75. The component registration information could not be read from the %3 WMI object: %1 (%2). If this error persists, try re-installing ...