Windows 8

  1. The value for the maximum number of simultaneous connections allowed to the RD Gateway server could not be updated. The following ...
  2. The value for the parameter '{0}' is not specified. To invoke this command, use explicit parameter names with all values. ...
  3. The value for the parameter {0}, specified in the context of propagation test file cleanup, is invalid. Acceptable value ...
  4. The value for the Windows System Resource Manager version specified in the .xml file is either not valid or cannot be found. ...
  5. The value is specified in seconds. Default is 5 secs This parameter is applicable only when a RADIUS server is being configured ...
  6. The value is specified in seconds. The default value is 5 seconds. This parameter can be configured only if the EnableAccountingType ...
  7. The value is specified in seconds. The default value is 5 secs. This parameter can be configured only if the Type parameter ...
  8. The value must be numeric, either in decimal or hexadecimal format. A value specified in hexadecimal format must start with ...
  9. The value named %1 in the server's registry key %2 was not valid, and was ignored. If you want to change the value, change ...
  10. The value of cCol in MQSORTSET cannot be greater than 1. Active Directory Domain Services supports only a single sort key. ...
  11. The value of InitialPoolConnections exceeds the value of MaxPoolConnections in the Active Directory Web Services configuration ...
  12. The value of MaxEnumCtxsPerSession exceeds the value of MaxEnumCtxsTotal in the Active Directory Web Services configuration ...
  13. The value of MaxReservedIdleTimeout exceeds the value of MaxReservedTimeout in the Active Directory Web Services configuration ...
  14. The value of the EnumName attribute does not translate to a valid C# identifier: {0}. Verify the EnumName attribute in Cmdlet ...
  15. The value of the EnumName attribute doesn't translate to a valid C# identifier: {0}. Verify the EnumName attribute in Cmdlet ...
  16. The value of the FilePath parameter must be a Windows PowerShell script file. Enter the path to a file with a .ps1 file name ...
  17. The value of the HelpInfoUri key in the module manifest must resolve to a container or root URL on a website where the help ...
  18. The value of the Name attribute is not a valid C# identifier: {0}. Verify the Name attribute in Cmdlet Definition XML and ...
  19. The value of the Name attribute is not a valid C# identifier: {0}. Verify the Name attribute in Cmdlet Definition XML and ...
  20. The value of the parameter {0} is invalid. The data must be a PSCredential object returned from the cmdlet of Get-Credential. ...
  21. The value of the parameter {0} is invalid. The possible expiration values are a date time such as "1/1/2020 12:00:00 PM", ...
  22. The value of the PersistencePath parameter {0} exceeds the maximum allowed length. The persistence path should not be greater ...
  23. The value of the RequestGuid parameter does not point to any running request. Specify a valid RequestGuid, and then try again. ...
  24. The value of the ServiceProvider XML element in the metadata package service information file is too long; for mobile broadband ...
  25. The value of the {0} key in {1} is {2} and the module has nested modules. When a CDXML file is the root module, the Import-Module ...
  26. The value of XaTmMinWarmRecoveryInterval is greater than the value of XaTmMaxWarmRecoveryInterval. MS DTC will ignore the ...
  27. The Value parameter is required for a member of type "{0}". Specify the Value parameter when adding members of this type. ...
  28. The Value parameter should not be null for a member of type "{0}". Specify a non-null value for the Value parameter when ...
  29. The value provided for BITS_JOB_PROPERTY_MAX_DOWNLOAD_SIZE property is invalid. Please provide value between 1 and UINT64_MAX. ...
  30. The value specified for a setting in the Active Directory Web Services configuration file is greater than the maximum value ...
  31. The value specified for a setting in the Active Directory Web Services configuration file is less than the minimum value ...
  32. The value specified for a setting in the Active Directory Web Services configuration file is not syntactically correct. A ...
  33. The value specified for Eventlist is not in the correct format. The value should specify a list of Event-Ids and/or keywords ...
  34. The value specified for the mapping 'headerMappingOptions' for 'WS_HTTP_HEADER_MAPPING' must be zero if HTTP GET support ...
  35. The value specified for the NewComputerName parameter is the same as the value of the ComputerName parameter. Provide a different ...
  36. The value specified for the property is outside the acceptable range of values. Change the value in the property to a value ...
  37. The value specified in registry (%1) has no name. The entry is ignored. It must have a valid username as name, be of type ...
  38. The value supplied for MaximumSize parameter has to be in the range of 64 KB to 4GB with an increment of 64 KB. Please enter ...
  39. The value with name %1 specified in registry (%2) is not of type REG_DWORD. The entry is ignored. It must have a valid username ...
  40. The value with name %1 specified in registry (%2) of value (%3) cannot be interpreted. The entry is ignored. It must have ...
  41. The value {0} is not supported for an ActionPreference variable. It should be used only as a value for a preference parameter. ...
  42. The ValueName and ValuePrefix parameters cannot be specified together for this command. The ValuePrefix parameter is used ...
  43. The values for /mgmtrule are EqualPerProcess, EqualPerUser, EqualPerSession, EqualPerIISAppPool or Standard. Specify a new ...
  44. The values in the Kilobytes Sent and Kilobytes Received columns are approximate, not actual values. The actual values depend ...
  45. The values specified in the section of the configuration file for Active Directory Web Services have been loaded without ...
  46. The variable with name '{0}' is defined to store results from a parallel or sequence block. Therefore, it cannot be reused ...
  47. The vault location could not be found. If the selected location is on a removable device, make sure that the device is connected. ...
  48. The VDS hardware provider for the selected object does not support this maintenance operation. Please select a different ...
  49. The VDS hardware provider for the selected object returned an unexpected error while performing the requested operation. ...
  50. The VDS provider for the subsystem did not report any supported LUN types. Depending on the subsystem, you might need to ...
  51. The version '{0}' of module '{1}' does not meet the required minimum version '{2}'. Please verify the version number and ...
  52. The version number returned from the Internet Storage Name Server (iSNS) server is not compatible with this version of the ...
  53. The version numbers for one or more GPOs on this domain controller are not in sync with the versions for the GPOs on the ...
  54. The version of Hyper-V on physical computer '%1' is not compatible with physical computer '%2'. To migrate a virtual machine ...
  55. The version of Hyper-V Replica for virtual machine '%1' is not compatible with this Hyper-V server. (Virtual machine ID %2). ...
  56. The version of integration services that supports this virtual device does not match the version expected by Hyper-V. To ...
  57. The version of Microsoft Windows that you are using is not trusted by a server that the viewer must access. Update Microsoft ...
  58. The version of the Active Directory authorization policy store doesn't match the version supported by this Hyper-V server. ...
  59. The version of the configuration file you are trying to import is not supported. You cannot import configuration files with ...
  60. The version of the data file you are attempting to load is higher than the version of the reporting transform. The report ...
  61. The version of the device '%4' of the virtual machine '%1' is not compatible with device on physical computer '%3'. (Virtual ...
  62. The version of the directory service schema of the source forest is not compatible with the version of directory service ...
  63. The version of the failover cluster that you are connected to: Windows Server version '{0}' does not support the UseLocalTime ...
  64. The version of the IPsec policy in the IPsec policy storage location is a later version (%d.%d) than expected (%d.%d). As ...
  65. The version of the IPsec policy in the IPsec policy storage location is an earlier version (%d.%d) than that expected (%d.%d). ...
  66. The version of the IPsec policy in the IPsec policy storage location is not supported. The IPsec policy in the policy storage ...
  67. The version of the IPsec policy in the IPsec policy storage location is not supported. The IPsec policy in the policy storage ...
  68. The version of the loaded CLR is '{0}'. The module '{1}' requires a minimum CLR version of '{2}' to run. Please verify the ...
  69. The version of the loaded Windows PowerShell is '{0}'. The module '{1}' requires a minimum Windows PowerShell version of ...
  70. The version of the new node does not support IP stickiness. After it is added to the cluster, IP stickiness timeout will ...
  71. The version of the operating system installed is incompatible with the current domain functional level. You must upgrade ...
  72. The version of the operating system installed is incompatible with the current forest functional level. You must upgrade ...
  73. The version of the operating system installed on this server is incompatible with the functional level of the domain or forest. ...
  74. The version of the operating system installed on this server no longer supports the current AD DS Forest functional level ...
  75. The version of the operating system installed on this server no longer supports the current domain functional level. You ...