Windows 8.1

  1. The file name you have specified does not have an extension. Some operating systems might not be able to use this file. If ...
  2. The file name you have specified does not have an extension. This might pose a security risk for your users. Some operating ...
  3. The file name you typed is incorrect. The file name cannot have more than eight characters and should not include a file ...
  4. The file name(s) would be too long for the destination folder. You can shorten the file name and try again, or try a location ...
  5. The file or device that you are trying to use requires a component of Windows Media Player to be upgraded. Click Upgrade ...
  6. The file or drive you are trying to scan does not exist on this computer. Choose another file or drive, and then scan your ...
  7. The file or folder associated with the specified token (%1) cannot be found. The file or folder may have been moved or deleted. ...
  8. The file or folder you are opening contains Web content that may be unsafe. The Web content has either been modified or is ...
  9. The file or folder {0} cannot be copied from location {1} to the deployment folder at {2} because the file or folder was ...
  10. The file or folder {0} cannot be copied from location {1} to the deployment folder because you are logged on with an account ...
  11. The file or folder {0} cannot be copied to the deployment folder at location {1}. Verify that you are logged on by using ...
  12. The file recovery operation has completed with errors. One or more files may not have been recovered correctly. Log of files ...
  13. The file reference number. On NTFS volumes, each file is assigned an identifier that is unique on the volume; the identifier ...
  14. The File Replication Service (FRS) engine was used when the backup was created. Stop the replication engine on other Active ...
  15. The File Replication Service (FRS) engine was used when the backup was created. Stop the replication engine on other Active ...
  16. The File Replication Service (FRS) is set to replicate one or more folders on this server. The replication of these folders ...
  17. The file replication service cannot communicate with the file replication service on the domain controller. The event log ...
  18. The File Replication Service cannot enable replication on the comptuer %1 until a backup/restore application completes. A ...
  19. The File Replication Service cannot enable replication on the comptuer %1 until a backup/restore application completes. A ...
  20. The File Replication Service cannot find the DNS name for the computer %1 because the "%2" attribute could not be read from ...
  21. The file replication service cannot populate the system volume because of an internal error. The event log may have more ...
  22. The file replication service cannot populate the system volume because of an internal timeout. The event log may have more ...
  23. The File Replication Service cannot replicate %1 because it overlaps the File Replication Service's logging pathname %2. ...
  24. The File Replication Service cannot replicate %1 because it overlaps the File Replication Service's working directory %2. ...
  25. The File Replication Service cannot replicate %1 because it overlaps the staging directory %2 of the replicating directory ...
  26. The File Replication Service cannot replicate %1 because the pathname of the customer designated staging directory: %2 is ...
  27. The File Replication Service cannot replicate %1 because the pathname of the replicated directory is not the fully qualified ...
  28. The File Replication Service cannot replicate %1 with the computer %2 because the computer's SID cannot be determined from ...
  29. The file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller. ...
  30. The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have ...
  31. The file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller. ...
  32. The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have ...
  33. The File Replication Service cannot start replica set %1 on computer %2 for directory %3 because the type of volume %4 is ...
  34. The file replication service cannot stop replicating the system volume because of an internal error. The event log may have ...
  35. The File Replication Service could not grant an unknown user access to the API "%1". Access checks can be disabled for "%1" ...
  36. The File Replication Service could not grant an unknown user access to the API "%1". Access checks can be disabled for "%1" ...
  37. The File Replication Service could not prepare the root directory %1 for replication. This is likely due to a problem creating ...
  38. The File Replication Service detected an invalid parameter value in the registry. %1. The expected registry key name is "%2". ...
  39. The File Replication Service detected an invalid parameter value in the registry. %1. The expected registry key name is "%2". ...
  40. The File Replication Service did not grant the user "%3" access to the API "%1". Permissions for "%1" can be changed by running ...
  41. The File Replication Service did not grant the user "%3" access to the API "%1". Permissions for "%1" can be changed by running ...
  42. The File Replication Service failed a consistency check (%3) in "%1" at line %2. The File Replication Service will restart ...
  43. The File Replication Service has detected a duplicate connection object between this computer "%6" and a computer named "%1". ...
  44. The File Replication Service has detected a duplicate connection object between this computer "%6" and a computer named "%1". ...
  45. The File Replication Service has detected a duplicate connection object between this computer "%7" and a computer named "%1". ...
  46. The File Replication Service has detected a duplicate connection object between this computer "%7" and a computer named "%1". ...
  47. The File Replication Service has detected an enabled disk write cache on the drive containing the directory %2 on the computer ...
  48. The File Replication Service has detected that one or more volumes on this computer have the same Volume Serial Number. File ...
  49. The File Replication Service has detected that the replica root path has changed from "%2" to "%3". If this is an intentional ...
  50. The File Replication Service has detected that the replica set "%1" is in JRNL_WRAP_ERROR. Replica set name is : "%1" Replica ...
  51. The File Replication Service has detected that the replica set "%1" is in JRNL_WRAP_ERROR. Replica set name is : "%1" Replica ...
  52. The File Replication Service has detected that the staging path for the replica set %1 has changed. Current staging path ...
  53. The File Replication Service has detected that the volume holding the FRS debug logs is running out of disk space. This will ...
  54. The File Replication Service has detected that the volume hosting the path %1 is low on disk space. Files may not replicate ...
  55. The File Replication Service has detected that this server is not a domain controller. Use of the File Replication Service ...
  56. The File Replication Service has detected what appears to be an attempt to change the root path for the following replica ...
  57. The File Replication Service has detected what appears to be an attempt to change the root path for the following replica ...
  58. The File Replication Service has skipped one or more files and/or directories during primary load of the following replica ...
  59. The File Replication Service is deleting this computer from the replica set "%1" as an attempt to recover from the error ...
  60. The File Replication Service is having trouble enabling replication from %1 to %2 for %3 using the DNS name %4. FRS will ...
  61. The File Replication Service is having trouble enabling replication from %1 to %2 for %3 using the DNS name %4. FRS will ...
  62. The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on ...
  63. The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on ...
  64. The File Replication Service is no longer preventing the computer %1 from becoming a domain controller. The system volume ...
  65. The File Replication Service is stopping on computer %1 because there is no free space on the volume containing %2. The available ...
  66. The File Replication Service is stopping on the computer %1 because a universally unique ID (UUID) cannot be created. The ...
  67. The File Replication Service is unable to add this computer to the following replica set: "%1" This could be caused by a ...
  68. The File Replication Service is unable to open (or create) the pre-install directory under the customer designated replica ...
  69. The File Replication Service is unable to open the customer designated staging directory for replica set %1. The path used ...
  70. The File Replication Service is unable to replicate from a partner computer because the event time associated with the file ...
  71. The File Replication Service is unable to replicate with its partner computer because the difference in clock times is outside ...
  72. The File Replication Service is unable to replicate with its partner computer because the difference in clock times is outside ...
  73. The File Replication Service may be preventing the computer %1 from becoming a domain controller while the system volume ...
  74. The File Replication Service may be preventing the computer %1 from becoming a domain controller while the system volume ...
  75. The File Replication Service may be preventing the computer %1 from becoming a domain controller while the system volume ...