Windows 8

  1. The %1 service was unable to log on as %2 with the currently configured password due to the following error: Logon failure: ...
  2. The %1 user is allowed a maximum number of %2 concurrent operations, which has been exceeded. Close existing operations for ...
  3. The %1 user is allowed a maximum number of %2 concurrent shells, which has been exceeded. Close existing shells or raise ...
  4. The %1!s! option can only be specified once on the command-line. Re-enter the command, specifying the %1!s! option only once. ...
  5. The %1!s! server already has 31 (maximum allowed) failover relationships. A server cannot have more than 31 failover relationships. ...
  6. The %2 home folder was not created because it already exists. The user account has been created with this home folder value ...
  7. The %2 home folder was not created because the path was not found. This could be caused by listing non-existent intermediate ...
  8. The %2 home folder was not created because you do not have create access on the server. The user account has been created ...
  9. The %2 home folder was not created because: %1 Click OK to attempt to update the user account with the new home folder value. ...
  10. The %2 home folder was not created because: %1 The user account has been created with the new home folder value but you must ...
  11. The %2 home folder was not created because: %1 The user account has been created with this home folder value but you must ...
  12. The %2 server role in server %1 has been updated with the value %3 for the configuration setting %4. The previous value was ...
  13. The %2!s! folder could not be found. Right-click the %2!s! icon, click Properties, and then check that the path to your target ...
  14. The %3 device on %1 virtual machine experienced an error %5 when completing an outgoing message. (Virtual machine ID %2) ...
  15. The %3 device on %1 virtual machine experienced an error %5 when processing a cursor shape update message. (Virtual machine ...
  16. The %3 device on %1 virtual machine experienced an error %5 when processing a dirty region message. (Virtual machine ID %2) ...
  17. The %3 device on %1 virtual machine experienced an error %5 when processing an incoming message. (Virtual machine ID %2) ...
  18. The %3 device on %1 virtual machine experienced an error %5 when processing the cursor shape update message. (Virtual machine ...
  19. The %3 device on %1 virtual machine experienced an error %5 when processing the invalidate rectangles message. (Virtual machine ...
  20. The %3 device on %1 virtual machine experienced an error %5 when processing the mode change message. (Virtual machine ID ...
  21. The %3 device on %1 virtual machine experienced an error %5 when processing the version request message. (Virtual machine ...
  22. The %FriendlyInterfaceName% adapter is experiencing problems Contact your administrator to resolve driver or hardware issues. ...
  23. The %s cannot be revoked because you have reached the limit for revoking licenses of this type. You cannot revoke another ...
  24. The %s home directory was not created because it already exists. You might want to select a different name, or make sure ...
  25. The %s home folder was not created because the path was not found. This could be caused by listing non-existant intermediate ...
  26. The %s home folder was not created because you do not have create access on the server. The user account has been updated ...
  27. The %WINDOWS_LONG% operating system and its user interface are protected by trademark and other pending or existing intellectual ...
  28. The '%1' role has been explicitly assigned in scope '%2'. '%1' is a reserved role. To prevent unwanted access to Hyper-V ...
  29. The '%1' role has been explicitly assigned in scope '%2'. '%1' is a reserved role. To prevent unwanted access to Hyper-V ...
  30. The '%1' role has been explicitly assigned in the default scope. '%1' is a reserved role. To prevent unwanted access to Hyper-V ...
  31. The '%1' role has been explicitly assigned in the default scope. '%1' is a reserved role. To prevent unwanted access to Hyper-V ...
  32. The '%3' device in '%1' virtual machine is loaded and the protocol version is negotiated to the most recent version. (Virtual ...
  33. The '%s' printer driver is not installed on this computer. Some printer properties will not be accessible unless you install ...
  34. The '-target' command requires additional arguments. Examples: -target default -target unallocated -target C: shrink -target ...
  35. The 'Default - Standard' assessment goals could not be loaded. Goals for some assessment metrics may be unavailable. Check ...
  36. The 'ModuleVersion' member is not present in the hashtable describing a module. This member must exist and be assigned a ...
  37. The 'netsh advfirewall dump' command is not implemented in this version of Windows. Instead, use the 'netsh advfirewall export' ...
  38. The 'Run this program as an administrator' compatibility setting cannot be used in combination with other compatibility settings. ...
  39. The 'VirtualMachine' {0} is assigned to Farm {1}. You must unassign the machine from the farm before you can assign it to ...
  40. The 'WS_CHANNEL_PROPERTY_ENABLE_TIMEOUTS' property query from the custom channel returned TRUE. Custom channels cannot be ...
  41. The 'WS_CHANNEL_PROPERTY_ID' id 'WS_CHANNEL_PROPERTY_CUSTOM_HTTP_PROXY' cannot be specified when 'WS_CHANNEL_PROPERTY_ID' ...
  42. The 'WS_LISTENER_PROPERTY_ID' id 'WS_LISTENER_PROPERTY_TO_HEADER_MATCHING_OPTIONS' must not have the setting 'WS_MATCH_URL_EXACT_PATH' ...
  43. The 'WS_LISTENER_PROPERTY_ID' id 'WS_LISTENER_PROPERTY_TRANSPORT_URL_MATCHING_OPTIONS' must not have the setting 'WS_MATCH_URL_EXACT_PATH' ...
  44. The 'WS_SERVICE_ENDPOINT_PROPERTY_ID' id 'WS_SERVICE_ENDPOINT_PROPERTY_METADATA_EXCHANGE_URL_SUFFIX' can only be specified ...
  45. The 'WS_SERVICE_ENDPOINT_PROPERTY_ID' id 'WS_SERVICE_ENDPOINT_PROPERTY_METADATA_EXCHANGE_URL_SUFFIX' cannot be a WS_STRING ...
  46. The '{0}' command in the {1}' module was imported, but because its name does not include an approved verb, it might be difficult ...
  47. The '{0}' command in the {2}' module was imported, but because its name does not include an approved verb, it might be difficult ...
  48. The '{0}' command was found in the module '{1}', but the module could not be loaded. For more information, run 'Import-Module ...
  49. The '{0}' module cannot be imported because its manifest contains one or more members that are not valid. The valid manifest ...
  50. The '{0}' property does not support elements from the Windows PowerShell language such as parentheses and variables. To use ...
  51. The .adm file "{0}" is in not in a valid format and must be replaced. Details: A non-empty list of items is expected at line ...
  52. The .adm file "{0}" is in not in a valid format and must be replaced. Details: There is an unexpected key name at line {1}. ...
  53. The .adm file "{0}" is not in a valid format and must be replaced. Details: A comparison operator is expected at line {1}. ...
  54. The .adm file "{0}" is not in a valid format and must be replaced. Details: A registry value is expected to be defined for ...
  55. The .adm file "{0}" is not in a valid format and must be replaced. Details: The end of the file was encountered unexpectedly. ...
  56. The .adm file "{0}" is not in a valid format and must be replaced. Details: The string {1} is not defined in the strings ...
  57. The .adm file "{0}" is not in a valid format and must be replaced. Details: The strings section is not properly formatted ...
  58. The .adm file "{0}" is not in a valid format and must be replaced. Details: There are unmatched directives (#if, #else, #endif) ...
  59. The .cab metadata file cannot be stored in the current working directory, because it is read-only. Use SET METADATA to specify ...
  60. The .chm and .chi files for the title "%s" do not match. Click OK to continue or Cancel to abort the display of topics from ...
  61. The .inf file in this profile is of a different version than expected. Upgrading this .inf file will result in the loss of ...
  62. The .msi file {0} could not be accessed. Verify that the file exists, and that this computer's account has the correct permissions ...
  63. The .rdp file contents of the desktop or farm Name:{0}, DisplayName:{1} were not updated for the following reason: '{2}'. ...
  64. The .xml file calendar value should either reference a single schedule or a single resource allocation policy. Specify a ...
  65. The .xml file is missing a value. Ensure that there are values for both the committed memory limit and the action to take ...
  66. The .xml timestamp is out-of-date. If you are using a graphical interface, click Refresh. If you are using a command-line ...
  67. The /%1!s! option does not take arguments. Try the command again without the argument. For more information, refer to the ...
  68. The /%1!s! option does not take arguments. Try the command again without the argument. For more information, refer to the ...
  69. The /AcceptEula or /GetEula options must be specified with the /Set-Edition option online. Run the command again and include ...
  70. The /CheckHealth option cannot be used on a Windows PE target image. The operation must be used on a full Windows operating ...
  71. The /csv mode makes the /showrepl command print in a Comma Separated Values (CSV)%0 format for import into Microsoft Excel ...
  72. The /Export-DefaultAppAssociations option requires a user to be logged in to the image. This option is not supported on an ...
  73. The /Image option that is specified points to a running Windows installation. To service the running operating system, use ...
  74. The /P switch allows you to set the value of a variable to a line of input entered by the user. Displays the specified promptString ...
  75. The /RestoreHealth option cannot be used on a Windows PE target image. The operation must be used on a full Windows operating ...