Windows 8

  1. The specified image group name is not valid. The name cannot start or end with spaces, match any reserved names such as COM1 ...
  2. The specified image handle was not opened with the correct access level. In order to mount an image handle, the handle must ...
  3. The specified image handle was not used to mount an image, and cannot be used to unmount. Please call WIMUnmountImage with ...
  4. The specified image is currently being serviced by another DISM operation. Wait for the existing DISM operation to complete, ...
  5. The specified image is incompatible with this version of DISM. Please use the version of DISM that matches the image version, ...
  6. The specified image name is not valid. You must specify a name (it cannot be empty), and the name cannot start or end with ...
  7. The specified import path does not exist or you do not have permission to access the directory. Please specify a new path ...
  8. The specified install image in the client unattend file is invalid. Either it does not exist, or it will not be one of the ...
  9. The specified install image information is duplicate because the device receives a client unattend file that already specifies ...
  10. The specified install image is invalid either because it does not exist or it will not be one of the install images offered ...
  11. The specified installation root volume is invalid. The Windows Deployment Services root folder can only exist on a volume ...
  12. The specified internal adapter cannot be used for load balancing because DHCP is enabled on the IPv4 properties of the adapter. ...
  13. The specified internal adapter has DHCP enabled on the IPv4 properties of the adapter. The DHCP addresses are not used for ...
  14. The specified intranet cluster Licensing URL cannot be validated. Verify that the host name is typed correctly. If you selected ...
  15. The specified IP address block contains both public and private IP addresses. Modify the start and end IP address for this ...
  16. The specified IP address range contains both public and private IP addresses. Modify the start and end IP address for this ...
  17. The specified IP address range is invalid. The start and end IP addresses must be valid and the start IP address must be ...
  18. The specified IP address range or block, contains both public and private IP addresses. Modify the start and end IP addresses ...
  19. The specified IP-HTTPS certificate is different from the VPN SSTP certificate. IP-HTTPS and SSTP must use the same certificate ...
  20. The specified IP-HTTPS prefix is already included in a prefix configured in entry point {0} VPN prefix. Specify a unique ...
  21. The specified IPv4 address is not valid for multicast. IPv4 multicast addresses must be in the range 224.0.1.0 to 239.255.255.255. ...
  22. The specified IPv6 address is not valid for multicast. IPv6 multicast addresses must start with FF (for example, FF15::FF). ...
  23. The specified IPv6 multicast address source is invalid. Transport Server only supports using IPv6 multicast addresses from ...
  24. The specified IPv6 prefix assigned to DirectAccess client computers is not valid. Verify that the prefix is correct, and ...
  25. The specified IPv6 prefix assigned to VPN client computers is not valid. Verify that the prefix is correct, and that the ...
  26. The specified IPv6 subnet prefix length is invalid. IPv6 prefix length must be between 0 and 128 (inclusive). Please enter ...
  27. The specified iSCSI session with a connection matching the specified target, target portal, and/or initiator portal could ...
  28. The specified iSCSI target was not found. In a failover cluster configuration, you should use the iSCSI Target server instance ...
  29. The specified key storage provider does not support DPAPI++ data protection. Zone signing will not be operational until this ...
  30. The specified local administrator account is not valid. Ensure that you are using a user account in the local Administrators ...
  31. The specified local cache location for the virtual desktop template is not valid. Ensure that the local cache location is ...
  32. The specified local storage location where new virtual desktops are created is not valid. Ensure that the location is correct, ...
  33. The specified location '%3' to store replica files is not supported because it is configured with the integrity stream attribute. ...
  34. The specified location is not an NTFS-formatted volume. This wizard only supports creating shared folders on NTFS volumes. ...
  35. The specified location is not valid or you do not have permission to access the directory. Please specify a different location ...
  36. The specified location is not valid. A valid location can be a HTTP, LDAP, FTP, file address, UNC path or a local file path. ...
  37. The specified location {0} is on a volume on the cluster quorum disk. Using the cluster quorum disk for anything other than ...
  38. The specified login credentials are duplicate because the device receives a client unattend file that already specifies login ...
  39. The specified maximum application version is not valid. The maximum version must be greater than or equal to the minimum ...
  40. The specified maximum argument length is smaller than the specified minimum argument length. Update the ValidateLength attribute ...
  41. The specified maximum number of arguments for a parameter is smaller than the specified minimum number of arguments. Update ...
  42. The specified maximum range cannot be accepted because it is less than the specified minimum range. Update the ValidateRange ...
  43. The specified member is a failover cluster running an unsupported version of Windows. You cannot add failover clusters running ...
  44. The specified member is part of a failover cluster that is already a member of the replication group. You cannot add multiple ...
  45. 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 ...
  46. The specified member {0} is a failover cluster running an unsupported version of Windows. You can add failover clusters running ...
  47. The specified message security binding can only be used with an additional binding (such as the SSL binding) for message ...
  48. The specified migration store does not contain Global IP Configuration data. Specify another migration store, or run the ...
  49. The specified migration store does not include IP configuration settings with physical address {0}. Specify another migration ...
  50. The specified migration store path cannot be found or cannot be created. Verify that the path to the migration store is valid. ...
  51. The specified migration store was not found. Verify that the store path is specified correctly and does not include the migration ...
  52. The specified minimum range ({0}) cannot be accepted because it is not the same type as the specified maximum range ({1}). ...
  53. The specified missing disk cannot be deleted because it contains volume extents. Remove the volume extents from the disk ...
  54. The specified Mixer Bitmap Destination Rectangle is invalid, it must be smaller than or the same size as the current video ...
  55. The specified module '{0}' with version '{1}' was not loaded because no valid module file was found in any module directory. ...
  56. The specified mounted image cannot be committed back into the WIM. This occurs when an image has been through a partial unmount ...
  57. The specified name %1 is invalid. Valid names consist of a name and type specified in hex. For example, WINS*20 would represent ...
  58. The specified name contains characters that are not valid. The name cannot start with a hyphen (-) and cannot contain spaces ...
  59. The specified name for this object exceeds the maximum length, which is usually 2047 characters. Use a shorter name for the ...
  60. The specified namespace name is invalid. The name must be 1 to 255 characters long and cannot contain a backslash (\) character. ...
  61. The specified namespace path will not be validated. Therefore, it is possible to specify an invalid path. To set the namespace ...
  62. The specified network adapter is not valid. This operation cannot be performed on a legacy network adapter or on any network ...
  63. The specified network path is invalid. Valid network paths should start with two backslashes (\) and must include computer ...
  64. The specified network storage location where new virtual desktops are created is not valid. Ensure that the location is correct, ...
  65. The specified NetworkId {0} is not valid. Expected format is where subnet id must be a valid {1} address and prefix length ...
  66. The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence ...
  67. The specified object cannot be updated either because the server is not available or because the required service is not ...
  68. The specified offline image has not been generalized. The operation cannot proceed. Run sysprep /generalize on the image, ...
  69. The specified operation could not be performed on this Superior enlistment, because the enlistment was not created with the ...
  70. The specified operation could not be performed, because the record that would be logged was too long. This can occur because ...
  71. The specified operation could not be performed, because the record that would be logged was too long. This can occur because ...
  72. The specified organizational unit (OU) does not exist or is invalid. Ensure that the OU exists in the destination domain. ...
  73. The specified organizational unit is not valid or it does not exist. Specify the distinguished name of the organizational ...
  74. The specified OTP certificate template cannot be found. Rerun the cmdlet and specify a valid template. The template value ...
  75. The specified OTP signing certificate template cannot be found. Rerun the cmdlet and specify a valid template. The template ...