Windows 8

  1. The backup catalog is corrupt or was created with a different version of Windows. Restore from a different backup or create ...
  2. The backup catalog is corrupted. Please recover the catalog from a backup using the Windows Server Backup snap-in or the ...
  3. The backup catalog is corrupted. Please recover the catalog from a backup using the Windows Server Backup snap-in or the ...
  4. The backup catalog on the selected disk '%1' is corrupted so that you will not be able to perform a recovery operation from ...
  5. The Backup Components XML document was rejected. In this case the reason could be that it is not a Backup Components Document ...
  6. The Backup contain references to Domain Local Groups. You should specify a migration table to map these entries correctly. ...
  7. The Backup contain references to security principals and/or UNC paths. To specify how the wizard should transfer these references, ...
  8. The backup contains Active Directory Domain Service which can be recovered only when the computer is started in Directory ...
  9. The backup contains the Active Directory Domain Service which can be recovered only when the computer is started in Directory ...
  10. The backup could take up to %1!d! GB of disk space. Because a previous backup already exists, all of this space might not ...
  11. The backup destination specified is on the same physical hard disk as your operating system. In case of a hardware failure ...
  12. The backup does not contain the tombstone-lifetime attribute required for recovery of Active Directory. Choose another backup. ...
  13. The backup drive could not be found. System Restore is looking for restore points on your backup. Make sure the backup drive ...
  14. The backup file could not be found. Make sure the drive that the backup is saved on is attached or try to restore from a ...
  15. The backup file to save uninstall information could not initialize. Do you want to continue? If you choose to continue, you ...
  16. The backup has some corrupted application metadata and cannot be used to perform a recovery. Run CHKDSK /R to determine if ...
  17. The backup image cannot be verified because the image may be corrupted. To preserve your data, it is recommended that you ...
  18. The backup information on this location has details of backups created up to %1. You may not be able to access backups created ...
  19. The backup information on this location has details of backups created up to {0}. You might not be able to access backups ...
  20. The backup of volume '%2' on the backup storage location is corrupted. Run CHKDSK /R to determine if the storage location ...
  21. The backup operation attempted at '%1' has failed to start, error code '%2' (%3). Please review the event details for a solution, ...
  22. The backup operation attempted at '%2' has failed to start, error code '%1' ('%6'). Please review the event details for a ...
  23. The backup operation attempted at '%4' has failed to start, error code '%5'. Please review the event details for a solution, ...
  24. The backup operation failed because there is not enough free space on your backup storage location. Internal error: Cannot ...
  25. The backup operation for the cluster configuration data has been aborted because quorum for the cluster has not yet been ...
  26. The backup operation for the cluster configuration data has been canceled. The cluster Volume Shadow Copy Service (VSS) writer ...
  27. The backup operation has completed with warning(s) - Volume '%2' has developed new bad clusters. This may be an indication ...
  28. The backup operation has failed because another backup or recovery operation is in progress. Please stop the conflicting ...
  29. The backup operation has failed because no backup storage location could be found. Please confirm that the backup storage ...
  30. The backup operation has failed because recovery planning is in progress through some other client. If multiple instances ...
  31. The backup operation has failed because the remote shared folder that you are using for a backup storage location is not ...
  32. The backup operation has failed because the required space was not available on the backup storage location. Free up space ...
  33. The backup operation that completed with warning(s) - Volume '%2' has developed new bad clusters. This may be an indication ...
  34. The backup operation that started at '%1' has encountered errors for the volume(s) '%2'. Log of files not successfully backed ...
  35. The backup operation that started at '%1' has failed because another backup or recovery operation is in progress. Please ...
  36. The backup operation that started at '%1' has failed because no backup storage location could be found. Please confirm that ...
  37. The backup operation that started at '%1' has failed because recovery planning is in progress through some other client. ...
  38. The backup operation that started at '%1' has failed because the remote shared folder '%2' that you are using for a backup ...
  39. The backup operation that started at '%1' has failed because the Volume Shadow Copy Service operation to create a shadow ...
  40. The backup operation that started at '%1' has failed because the Volume Shadow Copy Service operation to create a shadow ...
  41. The backup operation that started at '%1' has failed because the Windows Server Backup engine could not be contacted, error ...
  42. The backup operation that started at '%1' has failed to back up volume(s) '%2'. Please review the event details for a solution, ...
  43. The backup operation that started at '%1' has failed with following error code '%2' (%3). Please review the event details ...
  44. The backup operation that started at '%2' has failed because another backup or recovery operation is in progress. Please ...
  45. The backup operation that started at '%2' has failed because recovery planning is in progress through some other client. ...
  46. The backup operation that started at '%6' has completed with errors. Please review the event details for a solution, and ...
  47. The backup operation that started at '%6' has encountered errors, some of the files could not be backed up. Log of files ...
  48. The backup operation that started at '%6' has failed with following error code '%2' (%4). Please review the event details ...
  49. The backup operation that started at '%6' has failed with following error code '%2'. Please review the event details for ...
  50. The backup policy does not contain locations to store backups. Use New-WBBackupTarget and Add-WBBackupTarget to specify locations ...
  51. The backup policy does not contain scheduled times to create backups. Use Set-WBSchedule to specify the times to create daily ...
  52. The Backup program is not installed on your computer. To install it, double-click the Add or Remove Programs icon in Control ...
  53. The backup schedule was not found. Configure the scheduled backup by adding a backup location, items to back up, and times ...
  54. The backup storage destination that you have selected is on a dynamic disk. Doing this will give you limited functionality ...
  55. The backup storage location is a virtual volume that is dependent on the recovery location. Choose an alternate recovery ...
  56. The backup storage location is running low on free space. Future backup operations that store backups on this location may ...
  57. The backup storage location specified is offline. If it is a disk, make sure it is connected properly. If it is a DVD, make ...
  58. The backup storage location that you selected is on the same physical hard disk as your operating system. If the hard disk ...
  59. The backup storage location that you selected is on the same physical hard disk as your operating system. If the hard disk ...
  60. The backup you are using is either not valid or was made with a previous version of GPMC. To populate from this GPO, you ...
  61. The Base Application Partition has been marked changes disabled. Partitions are not currently visible. Partitions can be ...
  62. The Base Filtering Engine (BFE) is a service that manages firewall and Internet Protocol security (IPsec) policies and implements ...
  63. The base schema was not set. You may have problems importing the generated LDIF file because it may contain definitions of ...
  64. The basic constraints extension is used to indicate whether the certificate is a CA certificate or an end entity certificate. ...
  65. The behavior of GetCommandLine differs from Windows 9x to Windows XP. For example, if a user enters the command line: E: ...
  66. The best practice number would be the number of nodes in the cluster minus 1, because this makes the cluster try to start ...
  67. The Best Practices Analyzer will not be able to check the status of File Server Resource Manager on the following nodes: ...
  68. The billing information specified as part of the phone number has been rejected. Check to make sure you've entered it correctly, ...
  69. The BinarySecurityToken and AdditionalContext elements must be null. The "RequestID" and "TokenID" elements can't be specified ...
  70. The bind operation was successful but NLB is not responding to queries. Check the system event log on the specified computer ...
  71. The binding order determines when network interfaces will be used to make network connections by the computer. A disabled ...
  72. The BIOS did not correctly communicate with the master boot record (MBR). Contact the computer manufacturer for BIOS upgrade ...
  73. The BIOS did not correctly communicate with the Trusted Platform Module (TPM). Contact the computer manufacturer for BIOS ...
  74. The BIOS failure prevented the successful execution of the requested TPM operation (e.g. invalid TPM operation request, BIOS ...
  75. The BiosGuid, BiosSerialNumber, BaseBoardSerialNumber or ChassisAssetTag cannot be modified when the virtual machine is online. ...