Windows 8.1

  1. The specified percentage of memory that Hyper-V should try to reserve as a buffer is not valid for '%1'. The minimum value ...
  2. The specified permissions are not valid. Ensure that you are setting the appropriate permissions for the volume, and then ...
  3. The specified phone number either contains invalid characters, or is incorrectly formatted. Click on the number box with ...
  4. The specified pipe is set to complete operations and there are current I/O operations queued so it cannot be changed to queue ...
  5. The specified plex is the last active plex in the volume. The plex cannot be removed or else the volume will go offline. ...
  6. The specified PNRP cloud is configured as Resolve Only Registry reconfiguration is required to make publication in the cloud ...
  7. The specified prefix for creating virtual desktops is already in use in another virtual desktop collection. Choose a different ...
  8. The specified prefix length {0} is invalid. IPv4 cannot have prefix length > 32, please specify prefix length between 0 and ...
  9. The specified product key could not be validated. Check that the specified product key is valid and that it matches the target ...
  10. The specified product key is not valid for the target edition. Run this command again with a product key that is correct ...
  11. The specified property name (%1) is invalid for this item. The property may not be supported by the property handler for ...
  12. The specified protocol is not recognized. Be sure that the file name and syntax, such as slashes, are correct for the protocol.%0 ...
  13. The specified protocol is not recognized. Verify that the file name and syntax, such as slashes, are correct for the protocol. ...
  14. The specified provider name '{0}' cannot be used because it contains one or more of the following characters that are not ...
  15. The specified proxy server %1!s! is invalid. Ensure you have specified a valid server name and port in the format server_name:port_number. ...
  16. The specified query options are not available for this folder because it is not within a library or Homegroup. Only folders ...
  17. The specified RD Connection Broker server {0} already has joined nodes. An RD Connection Broker server with joined nodes ...
  18. The specified RD Connection Broker server {0} is not available. Ensure that the server is available on the network and that ...
  19. The specified RD Connection Broker server {0} is not available. Ensure that the server is available on the network and that ...
  20. The specified RD Connection Broker server {0} is not part of the highly available deployment {1}. Only RD Connection Broker ...
  21. The specified RDVHost server {0} cannot be reached. You must use the '-Force' option to force remove this RDVHost server. ...
  22. The specified redirector server cannot be reached or the credentials specified are invalid. If the redirector is not reachable ...
  23. The specified registry entry for the LDAP connection pool is not valid. Parameter Reference Context: %1 RequestId: %2 %3 ...
  24. The specified Remote Desktop certificate type is not valid. Valid Remote Desktop certificate types are RDGateway, RDWebAccess, ...
  25. The specified remote shared folder already has a backup of this computer that will be overwritten by the new backup that ...
  26. The specified remote shared folder does not contain any backup. Provide the path to a remote shared folder that contains ...
  27. The specified removable media or DVD does not contain any backup information. Make sure that the last removable media or ...
  28. The specified Replica server does not authorize the Hyper-V Replica Broker for the primary failover cluster to send replication ...
  29. The specified Replica server does not support replication. It is either running an older version or a client version of Hyper-V. ...
  30. The specified Replica server is a node in failover cluster. For clusters, use the name of the Hyper-V Replica Broker as the ...
  31. The specified Replica server is part of a failover cluster. For clusters, a valid Hyper-V Replica Broker is required for ...
  32. The specified Replica server is part of a failover cluster. For clusters, a valid Hyper-V Replica Broker is required for ...
  33. The specified Replica server is part of a failover cluster. For clusters, use the name of the Hyper-V Replica Broker as the ...
  34. The specified Replica server is part of a Failover Cluster. Specify the FQDN of the Hyper-V Replica Broker on the Replica ...
  35. The specified Replica server is part of a Failover Cluster. Specify the FQDN of the Hyper-V Replica Broker on the Replica ...
  36. The specified Replica server is the name of a failover cluster. For clusters, use the name of the Hyper-V Replica Broker ...
  37. The specified Replica server is the name of a failover cluster. For clusters, use the name of the Hyper-V Replica Broker ...
  38. The specified resource name is not supported by this resource DLL. This may be due to a bad (or changed) name supplied to ...
  39. The specified ring buffer was either previously empty or previously full which implies that the caller should signal the ...
  40. The specified schedule is not valid. A valid schedule consists of 24 comma-separated values. Each value represents one hour ...
  41. The specified script file '{0}' could not be processed because the file was not found. Verify that you have provided the ...
  42. The specified search server already exists. This error is obsolete and should no longer be reported. Call Microsoft Product ...
  43. The specified security binding usage ('%1') is not applicable for the specified message security binding ('%2') in security ...
  44. The specified security groups for AllowPasswordReplicationAccountName and DenyPasswordReplicationAccountName are invalid. ...
  45. The specified security groups were not deleted because they are the only remaining security groups containing DirectAccess ...
  46. The specified separator file path is invalid. Ensure the separator file exists and is under %windir%\System32 or a path containing ...
  47. The specified server cannot be used to get expected deployment results for the specified device because the device is configured ...
  48. The specified server does not exist, or the server or printer name is invalid. Names may not contain ',' or '\' characters. ...
  49. The specified server does not have the expected resources of a Windows Deployment Services server. This server might not ...
  50. The specified server represents a domain or forest name '{0}'.It should instead target a domain controller or an ADLDS instance. ...
  51. The specified service account credential is invalid. Either the password is incorrect or the cluster uses a different service ...
  52. The specified service port range is invalid. The start port must be less than or equal to the end port, and both values must ...
  53. The specified Shadow Copy Provider does not support shadow copy storage associations. A shadow copy storage association was ...
  54. The specified site name exceeds size limit of 63 bytes. English characters are represented by one byte, but characters from ...
  55. The specified source domain controller is not running Windows Server 2008 or later. When you pre-create a read-only domain ...
  56. The specified source domain controller is not running Windows Server 2012 or later. When you install a domain controller ...
  57. The specified source license server could not be contacted. Ensure that the license server name or IP address has been correctly ...
  58. The specified storage path for the virtual desktop template is not valid. Ensure that the central storage path is correct, ...
  59. The specified switch type is not valid. Either it was used to specify an external switch or to try to enable SR-IOV on an ...
  60. The specified target drive could not be found. Specify an existing drive letter. Examples: -target C: shrink -target D: merge ...
  61. The specified target name contains one or more characters that are not valid. Do you want the target name to be converted ...
  62. The specified task status can not be retrieved due to communication failure with the remote server. It is possible the task ...
  63. The specified temporary path is not available or cannot be found. Please ensure that the % mp% environment variable is populated ...
  64. The specified tenant compartment, %1!s!, does not exist. Create it using Add-VmNetworkAdapterRoutingDomainMapping cmdlet ...
  65. The specified transaction bridge CLSID is not a valid GUID. MS DTC is being started but the transaction bridge will be disabled.%0 ...
  66. The specified transaction or Transaction.Current must match the transaction used to create or open this TransactedRegistryKey. ...
  67. The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, ...
  68. The specified trust is not a Non-Windows Realm Trust. Adding and Removing TLNs and TLN Exculsions are only supported for ...
  69. The specified trust is not a Non-Windows Realm Trust. Changing this trust attribute is only supported for Non-Windows Realm ...
  70. The specified type data file '{0}' could not be processed because the file was not found. Verify that you have provided the ...
  71. The specified type is reserved for Microsoft reserved partitions or dynamic data partitions. Specify another type and try ...
  72. The specified URL mapping is invalid. The "from" mapping is empty, or the "from" mapping is the same as the "to" mapping. ...
  73. The specified user account and password does not have administrative privileges on the computer %1. Verify that the username ...
  74. The specified user account does not have administrative permissions on the computer %1. Verify that the user name and password ...
  75. The specified user account is already in the specified group account. Also used to indicate a group cannot be deleted because ...