Windows 8.1

  1. The specified IPv6 address is not valid for multicast. IPv6 multicast addresses must start with FF (for example, FF15::FF). ...
  2. The specified IPv6 multicast address source is invalid. Transport Server only supports using IPv6 multicast addresses from ...
  3. The specified IPv6 prefix assigned to DirectAccess client computers is not valid. Verify that the prefix is correct, and ...
  4. The specified IPv6 prefix assigned to VPN client computers is not valid. Verify that the prefix is correct, and that the ...
  5. The specified IPv6 subnet prefix length is invalid. IPv6 prefix length must be between 0 and 128 (inclusive). Please enter ...
  6. The specified iSCSI session with a connection matching the specified target, target portal, and/or initiator portal could ...
  7. The specified iSCSI target was not found. In a failover cluster configuration, you should use the iSCSI Target server instance ...
  8. The specified key storage provider does not support DPAPI++ data protection. Zone signing will not be operational until this ...
  9. The specified local administrator account is not valid. Ensure that you are using a user account in the local Administrators ...
  10. The specified local cache location for the virtual desktop template is not valid. Ensure that the local cache location is ...
  11. The specified local storage location where new virtual desktops are created is not valid. Ensure that the location is correct, ...
  12. The specified location '%3' to store replica files is not supported because it is configured with the integrity stream attribute. ...
  13. The specified location is not an NTFS-formatted volume. This wizard only supports creating shared folders on NTFS volumes. ...
  14. The specified location is not valid. A valid location can be a HTTP, LDAP, FTP, file address, UNC path or a local file path. ...
  15. The specified location {0} is on a volume on the cluster quorum disk. Using the cluster quorum disk for anything other than ...
  16. The specified login credentials are duplicate because the device receives a client unattend file that already specifies login ...
  17. The specified maximum application version is not valid. The maximum version must be greater than or equal to the minimum ...
  18. The specified maximum character length of the argument is shorter than the specified minimum argument character length. Update ...
  19. The specified maximum number of arguments for a parameter is fewer than the specified minimum number of arguments. Update ...
  20. The specified maximum range cannot be accepted because it is less than the specified minimum range. Update the ValidateRange ...
  21. The specified member is a failover cluster running an unsupported version of Windows. You cannot add failover clusters running ...
  22. The specified member is part of a failover cluster that is already a member of the replication group. You cannot add multiple ...
  23. The specified member is part of the core cluster group on a failover cluster. An access point that is a part of a core cluster ...
  24. The specified member {0} is a failover cluster running an unsupported version of Windows. You can add failover clusters running ...
  25. The specified message security binding can only be used with an additional binding (such as the SSL binding) for message ...
  26. The specified MIDI device is not installed on the system. To install the driver, go to Control Panel, click Printers and ...
  27. The specified migration store does not contain Global IP Configuration data. Specify another migration store, or run the ...
  28. The specified migration store does not include IP configuration settings with physical address {0}. Specify another migration ...
  29. The specified migration store path cannot be found or cannot be created. Verify that the path to the migration store is valid. ...
  30. The specified migration store was not found. Verify that the store path is specified correctly and does not include the migration ...
  31. The specified minimum range ({0}) cannot be accepted because it is not the same type as the specified maximum range ({1}). ...
  32. The specified missing disk cannot be deleted because it contains volume extents. Remove the volume extents from the disk ...
  33. The specified Mixer Bitmap Destination Rectangle is invalid, it must be smaller than or the same size as the current video ...
  34. The specified module '{0}' with version '{1}' was not loaded because no valid module file was found in any module directory. ...
  35. The specified mounted image cannot be committed back into the WIM. This occurs when an image has been through a partial unmount ...
  36. The specified name %1 is invalid. Valid names consist of a name and type specified in hex. For example, WINS*20 would represent ...
  37. The specified name for this object exceeds the maximum length, which is usually 2047 characters. Use a shorter name for the ...
  38. The specified name is too long or uses incompatible characters. Try the operation again after ensuring that the name is less ...
  39. The specified name matched more than one driver package on the server. Please specify the driver package ID to uniquely identify ...
  40. The specified namespace name is invalid. The name must be 1 to 255 characters long and cannot contain a backslash (\) character. ...
  41. The specified namespace path will not be validated. Therefore, it is possible to specify an invalid path. To set the namespace ...
  42. The specified network adapter is not valid. This operation cannot be performed on a legacy network adapter or on any network ...
  43. The specified network path is invalid. Valid network paths should start with two backslashes (\) and must include computer ...
  44. The specified network storage location where new virtual desktops are created is not valid. Ensure that the location is correct, ...
  45. The specified NetworkId %1 is not valid. Expected format is where SubnetId must be a valid %2 address and PrefixLength must ...
  46. The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence ...
  47. The specified object cannot be updated either because the server is not available or because the required service is not ...
  48. The specified offline image has not been generalized. The operation cannot proceed. Run sysprep /generalize on the image, ...
  49. The specified operation could not be performed on this Superior enlistment, because the enlistment was not created with the ...
  50. The specified operation could not be performed, because the record that would be logged was too long. This can occur because ...
  51. The specified operation could not be performed, because the record that would be logged was too long. This can occur because ...
  52. The specified operator requires both the -Property and -Value parameters. Provide values for both parameters, and then try ...
  53. The specified organizational unit %1 does not match the organizational unit %2 where the cluster computer object is found. ...
  54. The specified organizational unit (OU) does not exist or is invalid. Ensure that the OU exists in the destination domain. ...
  55. The specified organizational unit is not valid or it does not exist. Specify the distinguished name of the organizational ...
  56. The specified OTP certificate template cannot be found. Rerun the cmdlet and specify a valid template. The template value ...
  57. The specified OTP signing certificate template cannot be found. Rerun the cmdlet and specify a valid template. The template ...
  58. The specified OTP signing certificate template does not exist on any of the enterprise CA servers. Rerun the cmdlet, and ...
  59. The specified package cannot be added to an offline image. Add this package to a running operating system using the /Online ...
  60. The specified package cannot be added to this Windows Image due to a version mismatch. Update the Windows image and try the ...
  61. The specified package full name %1 is not eligible for a StageUserDataAsync call. The operation cannot be performed on an ...
  62. The specified parameters do not match any valid parameter set. Please refer to the cmdlet help to make sure the command line ...
  63. The specified parameters matched more than one image on the server. Please specify more parameters to uniquely identify one ...
  64. The specified partition does not exist or you do not have permission to perform the requested action. Make sure that you ...
  65. The specified path cannot be created because access was denied. Verify that you are logged on by using an account that has ...
  66. The specified path for the installation root is not valid. You must specify a full path (including drive letters) that is ...
  67. The specified path is not valid. A directory name in the specified path contains a colon (:) character. Specify a valid path, ...
  68. The specified path isn't valid. The path must be on a local NTFS volume and can't be the root directory for the volume, a ...
  69. The specified path or the path of a subfolder that this command tried to create exceeds the system-defined maximum length ...
  70. The specified path points to a font file that may not be available during later Windows sessions. Do you want to continue? ...
  71. The specified path {0} for the cmdlet of {1} is invalid. The valid path for the cmdlet is {2}:\TrustPolicy\MicrosoftFederationGateway. ...
  72. The specified path {0} for the cmdlet of {1} is invalid. The valid path for the cmdlet is {2}:\TrustPolicy\TrustedPublishingDomain. ...
  73. The specified path {0} for the cmdlet of {1} is invalid. The valid path for the cmdlet is {2}:\TrustPolicy\TrustedUserDomain. ...
  74. The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and ...
  75. The specified percentage of memory that Hyper-V should try to reserve as a buffer is not valid for '%1'. The maximum value ...