Windows 8

  1. The specified OTP signing certificate template does not exist on any of the enterprise CA servers. Rerun the cmdlet, and ...
  2. The specified package cannot be added to an offline image. Add this package to a running operating system using the /Online ...
  3. The specified package cannot be added to this Windows Image due to a version mismatch. Update the Windows image and try the ...
  4. The specified parameters do not match any valid parameter set. Please refer to the cmdlet help to make sure the command line ...
  5. The specified partition does not exist or you do not have permission to perform the requested action. Make sure that you ...
  6. The specified path cannot be created because access was denied. Verify that you are logged on by using an account that has ...
  7. The specified path for database location is either not an absolute valid path or the drive specified is invalid. The path ...
  8. The specified path for the installation root is not valid. You must specify a full path (including drive letters) that is ...
  9. The specified path is not valid or you do not have permission to access the directory. Ensure that the path has been typed ...
  10. The specified path is not valid. A directory name in the specified path contains a colon (:) character. Specify a valid path, ...
  11. The specified path or the path of a subfolder that this command tried to create exceeds the system-defined maximum length ...
  12. The specified path points to a font file that may not be available during later Windows sessions. Do you want to continue? ...
  13. The specified path {0} for the cmdlet of {1} is invalid. The valid path for the cmdlet is {2}:\TrustPolicy\MicrosoftFederationGateway. ...
  14. The specified path {0} for the cmdlet of {1} is invalid. The valid path for the cmdlet is {2}:\TrustPolicy\TrustedPublishingDomain. ...
  15. The specified path {0} for the cmdlet of {1} is invalid. The valid path for the cmdlet is {2}:\TrustPolicy\TrustedUserDomain. ...
  16. The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and ...
  17. The specified percentage of memory that Hyper-V should try to reserve as a buffer is not valid for '%1'. The maximum value ...
  18. The specified percentage of memory that Hyper-V should try to reserve as a buffer is not valid for '%1'. The minimum value ...
  19. The specified phone number either contains invalid characters, or is incorrectly formatted. Click on the number box with ...
  20. The specified pipe is set to complete operations and there are current I/O operations queued so it cannot be changed to queue ...
  21. The specified plex is the last active plex in the volume. The plex cannot be removed or else the volume will go offline. ...
  22. The specified PNRP cloud is configured as Resolve Only Registry reconfiguration is required to make publication in the cloud ...
  23. The specified policy interval does not match any of the policy intervals in the schedule name. Specify another policy interval. ...
  24. The specified prefix for creating virtual desktops is already in use in another virtual desktop collection. Choose a different ...
  25. The specified process matching criteria name is a word used by Windows System Resource Manager and cannot be used as a name. ...
  26. The specified product key could not be validated. Check that the specified product key is valid and that it matches the target ...
  27. The specified product key is not valid for the target edition. Run this command again with a product key that is correct ...
  28. The specified property name (%1) is invalid for this item. The property may not be supported by the property handler for ...
  29. The specified protocol is not recognized. Be sure that the file name and syntax, such as slashes, are correct for the protocol.%0 ...
  30. The specified protocol is not recognized. Verify that the file name and syntax, such as slashes, are correct for the protocol. ...
  31. 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. ...
  32. The specified query does not have enough information to be processed. Check the query for proper parentheses and quotation ...
  33. The specified query options are not available for this folder because it is not within a library or Homegroup. Only folders ...
  34. The specified RD Connection Broker server {0} already has joined nodes. An RD Connection Broker server with joined nodes ...
  35. The specified RD Connection Broker server {0} is not available. Ensure that the server is available on the network and that ...
  36. The specified RD Connection Broker server {0} is not available. Ensure that the server is available on the network and that ...
  37. The specified RD Connection Broker server {0} is not part of the highly available deployment {1}. Only RD Connection Broker ...
  38. The specified RDVHost server {0} cannot be reached. You must use the '-Force' option to force remove this RDVHost server. ...
  39. The specified redirector server cannot be reached or the credentials specified are invalid. If the redirector is not reachable ...
  40. The specified registry entry for the LDAP connection pool is not valid. Parameter Reference Context: %1 RequestId: %2 %3 ...
  41. The specified Remote Desktop certificate type is not valid. Valid Remote Desktop certificate types are RDGateway, RDWebAccess, ...
  42. The specified remote shared folder already has a backup of this computer that will be overwritten by the new backup that ...
  43. The specified remote shared folder does not contain any backup. Provide the path to a remote shared folder that contains ...
  44. The specified removable media or DVD does not contain any backup information. Make sure that the last removable media or ...
  45. The specified Replica server does not authorize the Hyper-V Replica Broker for the primary failover cluster to send replication ...
  46. The specified Replica server does not support replication. It is either running an older version or a client version of Hyper-V. ...
  47. The specified Replica server is a node in failover cluster. For clusters, use the name of the Hyper-V Replica Broker as the ...
  48. The specified Replica server is part of a failover cluster. For clusters, a valid Hyper-V Replica Broker is required for ...
  49. The specified Replica server is part of a failover cluster. For clusters, a valid Hyper-V Replica Broker is required for ...
  50. The specified Replica server is part of a failover cluster. For clusters, use the name of the Hyper-V Replica Broker as the ...
  51. The specified Replica server is part of a Failover Cluster. Specify the FQDN of the Hyper-V Replica Broker on the Replica ...
  52. The specified Replica server is part of a Failover Cluster. Specify the FQDN of the Hyper-V Replica Broker on the Replica ...
  53. The specified Replica server is the name of a failover cluster. For clusters, use the name of the Hyper-V Replica Broker ...
  54. The specified Replica server is the name of a failover cluster. For clusters, use the name of the Hyper-V Replica Broker ...
  55. The specified resource allocation policy is being used by Windows System Resource Manager and hence cannot be renamed. To ...
  56. The specified resource allocation policy name is a word used by Windows System Resource Manager and cannot be used as a name. ...
  57. The specified resource allocation value for this CPU is too large. The maximum CPU resource allocation value is dependent ...
  58. The specified resource name is not supported by this resource DLL. This may be due to a bad (or changed) name supplied to ...
  59. The specified ring buffer was either previously empty or previously full which implies that the caller should signal the ...
  60. The specified schedule is not valid. A valid schedule consists of 24 comma-separated values. Each value represents one hour ...
  61. The specified script file '{0}' could not be processed because the file was not found. Please correct the path and try again. ...
  62. The specified search server already exists. This error is obsolete and should no longer be reported. Call Microsoft Product ...
  63. The specified security binding usage ('%1') is not applicable for the specified message security binding ('%2') in security ...
  64. The specified security groups for AllowPasswordReplicationAccountName and DenyPasswordReplicationAccountName are invalid. ...
  65. The specified security groups were not deleted because they are the only remaining security groups containing DirectAccess ...
  66. The specified server cannot be used to get expected deployment results for the specified device because the device is configured ...
  67. The specified server does not have the expected resources of a Windows Deployment Services server. This server might not ...
  68. The specified server represents a domain or forest name '{0}'.It should instead target a domain controller or an ADLDS instance. ...
  69. The specified service account credential is invalid. Either the password is incorrect or the cluster uses a different service ...
  70. The specified service port range is invalid. The start port must be less than or equal to the end port, and both values must ...
  71. The specified Shadow Copy Provider does not support shadow copy storage associations. A shadow copy storage association was ...
  72. The specified site name exceeds size limit of 63 bytes. English characters are represented by one byte, but characters from ...
  73. The specified source domain controller is not running Windows Server 2008 or later. When you pre-create a read-only domain ...
  74. The specified source domain controller is not running Windows Server 2012 or later. When you install a domain controller ...
  75. The specified source license server could not be contacted. Ensure that the license server name or IP address has been correctly ...