Windows 8

  1. ERROR: BitLocker Drive Encryption could not perform this command. The target computer might be running an earlier version ...
  2. ERROR: BitLocker protection must be turned on to force a recovery for volume %1!s!. Type "manage-bde -on -?" for more information. ...
  3. ERROR: Cannot open '%1' since it is in use. If you still wish to repair '%1', please re-run this command from another environment, ...
  4. ERROR: Cannot open '%1'. Check that it is not currently in use. To continue even when the volume is in use, add the -Force ...
  5. ERROR: Cannot resolve reference %ws. Note that centrally-installed dependencies are not processed except in desktop applications. ...
  6. ERROR: Cannot use '%1' as the log file. Check that the file does not already exist and that a valid filename is specified. ...
  7. ERROR: Cannot use password to unlock the input volume. Please try a different password or provide a recovery password, recovery ...
  8. ERROR: Component identity found in manifest does not match the identity of the component requested. Reference is %ws. Definition ...
  9. Error: Could find no servers that can take the ISTG role in site %1. Must aboandon inbound intersite replication test for ...
  10. Error: Could not locate an ISTG or a future ISTG, with which to use for the rest of the intersite test. Must abandon inbound ...
  11. Error: Couldn't retreive the meta data from %1 for site %2, error 3!x! %4 Must abandon inbound intersite replication test ...
  12. Error: Couldn't retreive the Up-to-dateness vector data from %1 for site %2, error 3!x! "%4" Must abandon inbound intersite ...
  13. Error: Detected circular loop trying to locate the ISTG. Must abandon inbound intersite replication test for this site %1. ...
  14. Error: during volume shrink initiated on volume %1 we failed to move a movable file extent. Diagnostic details: - The last ...
  15. ERROR: Failed to transfer the schema FSMO role: %1 (%2). If the error code is "Insufficient Rights", make sure you supply ...
  16. ERROR: Group policy does not permit the storage of recovery information to Active Directory. The operation was not attempted. ...
  17. ERROR: Import from file %1 failed. Error file is saved in %2. If the error is "Insufficient Rights" (Ldap error code 50), ...
  18. Error: Integrity-check of the quota-tracking table completed, but %d corruptions were detected. Quota enforcement may not ...
  19. ERROR: Invalid encryption method '%1!s!'. Valid encryption methods: aes128, aes256. Encryption methods aes128_diffuser and ...
  20. ERROR: Invalid protector type '%1!s!'. Valid protector types: RecoveryPassword, ExternalKey, Certificate, TPM, TPMAndStartupKey, ...
  21. ERROR: Keys used to automatically unlock data volumes are only found in the OS volume. The volume letter for the OS volume ...
  22. ERROR: Line %d: An application configuration manifest contains more than one dependentAssembly element for configuring the ...
  23. ERROR: Line %d: The COM class threadingModel must be specified in this type of application, and cannot be set to 'Single'. ...
  24. ERROR: Line %d: The root or application manifest contains the noInherit element but the dependent assembly manifest does ...
  25. ERROR: Line %d: The value specified for the manifest assembly element manifestVersion attribute is not currently supported. ...
  26. ERROR: Manage-bde cannot manage the Trusted Platform Module (TPM) in this version of Windows. To manage the Trusted Platform ...
  27. ERROR: Network Unlock can only be disabled within the BitLocker Drive Encryption group policy setting "Allow network unlock ...
  28. ERROR: No recovery methods exist for volume %1!s!. Type "manage-bde -protectors -add -?" for more information about adding ...
  29. ERROR: None of the parameters are specified to be changed (At least one is required). Type "SCHTASKS /CHANGE /?" for usage. ...
  30. Error: Operation not allowed because AD DS/LDS files are in the restored state. Restart the directory instance to finalize ...
  31. Error: Out of memory. The remote session will be disconnected. Close some programs on the local computer, and then try connecting ...
  32. ERROR: Schema upgrade attempted from a schema version less than 10. This is not a supported configuration. DCs in this enterprise ...
  33. ERROR: Selected writer "%1" is in a failed state - Status: %2 (%3) - Writer failure code: 4 (%5) - Writer ID: %6 - Instance ...
  34. ERROR: Specifying the parameter '-StartupKey' or '-Password' is required to BitLocker-protect the OS volume. Type "manage-bde ...
  35. ERROR: The -nov parameter is no longer required. By default the BitLocker driver will attempt to modify the boot volume to ...
  36. Error: The current ISTG is down in site %1 and further dcdiag could not contact any other servers in the site that could ...
  37. Error: The D3D assessment cannot run because the Graphics hardware does not support post pixel blending on 16-bit floating ...
  38. Error: the default security template file %S was not found. Please copy the file from Windows CD and retry the operation. ...
  39. ERROR: The directory service refused the request for schema upgrade: %1 (%2) If the error code is "Insufficient Rights", ...
  40. Error: The DNS domain name, %1, is too long. A valid Windows DNS domain name can contain a maximum of %2!d! UTF-8 bytes. ...
  41. ERROR: The encryption methods aes128_Diffuser and aes256_Diffuser are deprecated. Valid volume encryption methods: aes128, ...
  42. Error: The Graphics assessment cannot run because the Graphics hardware does not support MinFiltering on the StrechRect interface ...
  43. ERROR: The hardware test failed with code 1!08x!. All key protectors were removed. Possible reasons that the hardware test ...
  44. ERROR: The hardware test failed with code 1!08x!. All key protectors{0}were removed.{0}{0}Possible reasons that the hardware ...
  45. ERROR: The input volume has suffered damages to critical information related to the decryption key. Please try the -KeyPackage ...
  46. Error: The machine could not attach to the DC because the credentials were incorrect. Check your credentials or specify credentials ...
  47. Error: The machine, %1 could not be contacted, because of a bad net response. Check to make sure that this machine is a Directory ...
  48. ERROR: The network connection to Windows PowerShell Web Access cannot be restored. Input or output might have been lost, ...
  49. ERROR: The options /RI, /DU, /ST, /SD, /ET, /ED and /K are not applicable for the existing scheduled type. Type "SCHTASKS ...
  50. ERROR: The options /RI, /DU, /ST, /SD, /ET, /ED and /K are not applicable for the scheduled types: ONSTART, ONLOGON, ONIDLE, ...
  51. ERROR: The password you specified is incorrect. However, you have permission to access the PFX without a password. Re-run ...
  52. Error: The read operation from the volume shadow copy on one of the source volumes failed. Make sure all the volumes included ...
  53. ERROR: The recovery password '%1' is not formatted correctly according to the requirements for a numerical password. The ...
  54. ERROR: The recovery password provided is not formatted correctly according to requirements for a numerical password. The ...
  55. Error: The remote site %1, has no servers that can act as bridgeheads between the %1 and the local site %2 for the read only ...
  56. Error: The remote site %1, has no servers that can act as bridgeheads between the %1 and the local site %2 for the writeable ...
  57. Error: The syntax of the domain name, %1, is incorrect. DNS names may contain letters (a-z, A-Z), numbers (0-9), and hyphens, ...
  58. ERROR: The target machine returned an error on the discovery volume argument. Earlier versions of Windows do not support ...
  59. ERROR: The TPM cannot be used to protect this volume. The TPM does not have an owner set. To manage the Trusted Platform ...
  60. ERROR: The TPM cannot be used to protect this volume. The TPM is off. To manage the Trusted Platform Module (TPM), use either ...
  61. ERROR: The TPM cannot be used to protect this volume. The TPM Storage Root Key (SRK) has an incompatible authorization value. ...
  62. ERROR: The volume %1!s! could not be opened by BitLocker. This may be because the volume does not exist, or because it is ...
  63. ERROR: There are no password key protectors on volume %1!s!. Type "manage-bde -protectors -add -?" for more information about ...
  64. ERROR: There are no PIN key protectors on volume %1!s!. Type "manage-bde -protectors -add -?" for more information about ...
  65. ERROR: There are no TPM based startup key protectors on volume %1!s!. Type "manage-bde -protectors -add -?" for more information ...
  66. Error: there are two SDBs with the same friendly name, one 32-bit and the other 64-bit. Please use the -n:WIN32 or -n:WIN64 ...
  67. ERROR: There is more than one password key protector on volume %1!s!. Only one password key protector per volume is supported. ...
  68. ERROR: There is more than one PIN key protector on volume %1!s!. Only one PIN key protector per volume is supported. Type ...
  69. ERROR: There is more than one startup key protector on volume %1!s!. Only one startup key protector per volume is supported. ...
  70. ERROR: This volume stores external key(s) that can automatically unlock other volumes. Before you can decrypt this volume, ...
  71. ERROR: To turn on BitLocker in a pre-installation or recovery environment, a TPM must be present, enabled, and activated. ...
  72. ERROR: To turn on BitLocker in a pre-installation or recovery environment, the TPM must be enabled and activated. To manage ...
  73. ERROR: To turn on BitLocker with a SID-based Identity protector on this volume, you must provide at least one additional ...
  74. ERROR: To turn on BitLocker, a recovery method must exist. Include "-RecoveryKey path]" in the command line to generate and ...
  75. ERROR: To use the -Certificate command you must also specify either the path to the certificate file using the -cf parameter ...