Windows 10

  1. The file is protected by a digital license that has become inaccessible. Please see http://www.microsoft.com for information ...
  2. The file is protected with a digital license. The key to open this license may not reside on this computer or the license ...
  3. The file management task cannot be accessed because task conditions were modified by using WMI or Windows PowerShell interfaces. ...
  4. The file may contain scripts or try to access information in your library. Are you sure you want to download and open the ...
  5. The file may only have partial classification because a failure occurred while loading or classifying the file properties. ...
  6. The file name "%1!s!" contains a semicolon (;) and the file can't be burned to a disc. Do you want this copy of the file ...
  7. The file name '%3' is invalid. You cannot use the following names (LPTn, COMn, PRN, AUX, NUL, CON) because they are reserved ...
  8. The file name contains a semicolon (;) and the file can't be burned to a disc. Do you want this copy of the file to be renamed ...
  9. The file name is not valid because it does not have a .vfd file extension. Try again by entering a file name that includes ...
  10. The file name you are creating is too long. Try again using a shorter file name or create the file in a folder that has a ...
  11. 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 ...
  12. The file or device that you are trying to use requires a component of Windows Media Player to be upgraded. Click Upgrade ...
  13. The file or drive you are trying to scan does not exist on this computer. Choose another file or drive, and then scan your ...
  14. The file or folder associated with the specified token (%1) cannot be found. The file or folder may have been moved or deleted. ...
  15. The file or folder you are opening contains Web content that may be unsafe. The Web content has either been modified or is ...
  16. The file recovery operation has completed with errors. One or more files may not have been recovered correctly. Log of files ...
  17. The File Replication Service (FRS) is set to replicate one or more folders on this server. The replication of these folders ...
  18. The file replication service cannot communicate with the file replication service on the domain controller. The event log ...
  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 prepare the root directory %1 for replication. This is likely due to a problem creating ...
  37. The File Replication Service detected an invalid parameter value in the registry. %1. The expected registry key name is "%2". ...
  38. The File Replication Service did not grant the user "%3" access to the API "%1". Permissions for "%1" can be changed by running ...
  39. The File Replication Service failed a consistency check (%3) in "%1" at line %2. The File Replication Service will restart ...
  40. The File Replication Service has detected a duplicate connection object between this computer "%6" and a computer named "%1". ...
  41. The File Replication Service has detected a duplicate connection object between this computer "%7" and a computer named "%1". ...
  42. The File Replication Service has detected an enabled disk write cache on the drive containing the directory %2 on the computer ...
  43. The File Replication Service has detected that the replica root path has changed from "%2" to "%3". If this is an intentional ...
  44. The File Replication Service has detected that the replica set "%1" is in JRNL_WRAP_ERROR. Replica set name is : "%1" Replica ...
  45. The File Replication Service has detected what appears to be an attempt to change the root path for the following replica ...
  46. The File Replication Service is deleting this computer from the replica set "%1" as an attempt to recover from the error ...
  47. The File Replication Service is having trouble enabling replication from %1 to %2 for %3 using the DNS name %4. FRS will ...
  48. The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on ...
  49. The File Replication Service is no longer preventing the computer %1 from becoming a domain controller. The system volume ...
  50. The File Replication Service is stopping on computer %1 because there is no free space on the volume containing %2. The available ...
  51. The File Replication Service is stopping on the computer %1 because a universally unique ID (UUID) cannot be created. The ...
  52. The File Replication Service is unable to add this computer to the following replica set: "%1" This could be caused by a ...
  53. The File Replication Service is unable to open (or create) the pre-install directory under the customer designated replica ...
  54. The File Replication Service is unable to open the customer designated staging directory for replica set %1. The path used ...
  55. The File Replication Service is unable to replicate from a partner computer because the event time associated with the file ...
  56. The File Replication Service is unable to replicate with its partner computer because the difference in clock times is outside ...
  57. The File Replication Service may be preventing the computer %1 from becoming a domain controller while the system volume ...
  58. The File Replication Service may be preventing the computer %1 from becoming a domain controller while the system volume ...
  59. The File Replication Service moved the preexisting files in %1 to %2. The File Replication Service may delete the files in ...
  60. The File Replication Service on computer %1 is stopping because the database %2 is corrupted. The database can be recovered ...
  61. The File Replication Service on the computer %1 cannot communicate with the File Replication Service on the computer %2. ...
  62. The file replication service on the domain controller cannot communicate with the file replication service on this computer. ...
  63. The File Replication Service paused because the size of a file exceeds the staging space limit. Replication will resume only ...
  64. The File Replication Service paused because the staging area is full. Replication will resume if staging space becomes available ...
  65. The File Replication Service successfully added the connections shown below to the replica set: "%1" %2 %3 %4 %5 %6 %7 %8 ...
  66. The File Replication Service successfully added this computer to the following replica set: "%1" Information related to this ...
  67. The File Replication Service will not check access to the API "%1". Access checks can be enabled for "%1" by running regedt32. ...
  68. The file requires special content protection support to be transferred to portable devices. You may attempt transfer with ...
  69. The file resides under a protected namespace (such as %WINDIR%\System32). Its classification properties will not be updated. ...
  70. The File Server Resource Manager configuration file '%1' is missing. This could have been caused by inadvertent administrator ...
  71. The File Server Resource Manager configuration file '%1' is not found. It is required that the system or volume be restored ...
  72. The File Server Resource Manager configuration file '%1' is out of sync or missing records. This could have been caused by ...
  73. The File Server Resource Manager configuration file or import-export file '%1' is corrupted. If the corrupt file is a configuration ...
  74. The File Server Resource Manager detected %1 unprocessed quota or screening notifications when the service or system was ...
  75. The File Server Resource Manager global configuration cannot be accessed since the cluster service is not running. Please ...