Windows 8.1

  1. The File Replication Service moved the preexisting files in %1 to %2. The File Replication Service may delete the files in ...
  2. The File Replication Service on computer %1 is stopping because the database %2 is corrupted. The database can be recovered ...
  3. The File Replication Service on computer %1 is stopping because the database %2 is corrupted. The database can be recovered ...
  4. The File Replication Service on the computer %1 cannot communicate with the File Replication Service on the computer %2. ...
  5. The file replication service on the domain controller cannot communicate with the file replication service on this computer. ...
  6. The File Replication Service paused because the size of a file exceeds the staging space limit. Replication will resume only ...
  7. The File Replication Service paused because the size of a file exceeds the staging space limit. Replication will resume only ...
  8. The File Replication Service paused because the staging area is full. Replication will resume if staging space becomes available ...
  9. The File Replication Service paused because the staging area is full. Staging files are used to replicate created, deleted ...
  10. The File Replication Service successfully added the connections shown below to the replica set: "%1" %2 %3 %4 %5 %6 %7 %8 ...
  11. The File Replication Service successfully added this computer to the following replica set: "%1" Information related to this ...
  12. The File Replication Service was unable to create the directory "%1" to store debug log files. If this directory does not ...
  13. The File Replication Service will not check access to the API "%1". Access checks can be enabled for "%1" by running regedit. ...
  14. The File Replication Service will not check access to the API "%1". Access checks can be enabled for "%1" by running regedt32. ...
  15. The file requires special content protection support to be transferred to portable devices. You may attempt transfer with ...
  16. The file resides under a protected namespace (such as %WINDIR%\System32). Its classification properties will not be updated. ...
  17. The file server name "{0}" is not in a valid DNS format. DNS names must contain only alphanumeric characters. The following ...
  18. The File Server resource '{0}' cannot be copied because another File Server resource already exists in '{1}'. The file shares ...
  19. The File Server Resource Manager configuration file '%1' is missing. This could have been caused by inadvertent administrator ...
  20. The File Server Resource Manager configuration file '%1' is not found. It is required that the system or volume be restored ...
  21. The File Server Resource Manager configuration file '%1' is out of sync or missing records. This could have been caused by ...
  22. The File Server Resource Manager configuration file or import-export file '%1' is corrupted. If the corrupt file is a configuration ...
  23. The File Server Resource Manager detected %1 unprocessed quota or screening notifications when the service or system was ...
  24. The File Server Resource Manager global configuration cannot be accessed since the cluster service is not running. Please ...
  25. The File Server Resource Manager Reports service is shutting down due to shutdown event from the Service Control Manager. ...
  26. The File Server Resource Manager server is managed remotely using the File Server Resource Manager snap-in or the dirquota.exe, ...
  27. The File Server Resource Manager service could not send email due to an error. Check the application event log for more information. ...
  28. The File Server Resource Manager service encountered an unexpected error. Check the application event log for more information. ...
  29. The File Server Resource Manager service failed to analyze the mount points under the volume mounted at {0}. Please reconfigure ...
  30. The File Server Resource Manager service failed to analyze the namespaces for volume mounted at {0}. Please reconfigure the ...
  31. The File Server Resource Manager service, or Storage Reports Manager service is either not running or was restarted. Closing ...
  32. The File Server Storage Reports Manager service implements the runtime functionality to run file server storage reports, ...
  33. The file size is too large. Reduce the size, and then try again. The maximum file size for ANSI files is 32 KB and for UNICODE ...
  34. The file system container attempted to insert a file name twice. This is invalid, the wim service should only receive one ...
  35. The file system could not be mounted on the volume. Ensure that the volume is configured correctly, and then try the operation ...
  36. The file system detected a corruption on a file. The file has been removed from the file system namespace. The name of the ...
  37. The file system detected a corruption on a file. The file system may have failed to remove it from the file system namespace. ...
  38. The file system detected a corruption on a folder. Contents of the folder have been removed from the file system namespace. ...
  39. The file system detected a corruption on a folder. The file system may have failed to remove contents of the folder from ...
  40. The file system entries for package %1 could not be cleaned up after reboot. The package is removed from the purge list. ...
  41. The file system for one or more partitions on the disk for resource '%1' may be corrupt. Run the Validate a Configuration ...
  42. The file system on the folder may be damaged. If the problem persists, contact the person that is responsible for your network ...
  43. The file system on this folder may be damaged. If there are any hard drives that are listed as missing on the Dashboard, ...
  44. The file system on volume "%1" is potentially corrupted. Please run the CHKDSK utility to verify and fix the file system. ...
  45. The file system on volume '%1' is potentially corrupted. Please run the CHKDSK utility to verify and fix the file system. ...
  46. The file system size is larger than the partition size in the partition table. This drive may be corrupt or may have been ...
  47. The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the device %1 with label ...
  48. The file system structure that maintains security information on volume %1 (%2) has grown excessively large and fragmented. ...
  49. The file system was unable to write metadata to the media backing volume %2. A write failed with status "%3" ReFS will take ...
  50. The file that loaded this contact has been moved or no longer exists. Saving this contact will result in a new contact being ...
  51. The file that was specified as a target is a directory and the caller specified that it could be anything but a directory. ...
  52. The file that you are trying to use requires a software component on your computer to be upgraded. We recommend that you ...
  53. The file type association details in the database are corrupted. More than one file type association is published for the ...
  54. The file type is not recognized and cannot be played. Either the correct codec (a file that compresses/decompresses audio ...
  55. The file version entered contains one or more parts that are greater than the maximum value of a WORD (16-bit number). Should ...
  56. The file was in use and could not be classified. Another attempt to classify the file will be made after the retry period. ...
  57. The file was modified during this classification session so its properties will not be updated. Another attempt to update ...
  58. The file was not downloaded because the server where the file is stored redirected the request to a web page. This might ...
  59. The file with extension %1 cannot be faxed because faxing requires the file to be rendered to TIF. This file cannot be rendered ...
  60. The file you are attempting to play has an extension (.%s) that does not match the file format. Playing the file may result ...
  61. The file you are attempting to preview could harm your computer. If you trust the file and the source you received it from, ...
  62. The file you are downloading cannot be opened by the default program. It is either corrupted or it has an incorrect file ...
  63. The file you are downloading has been reported to be unsafe. The download website contains links to viruses or other software ...
  64. The file you are downloading has been reported to be unsafe. The download website contains links to viruses or other software ...
  65. The file you entered is not a unattend setup information file (SIF) or the SIF is not portable to other images. Only SIFs ...
  66. The file {0} is not digitally signed. You cannot run this script on the current system. For more information about running ...
  67. The file {0} you are trying to play does not have a license. Try playing the file using Windows Media Player to acquire a ...
  68. The filename '%1' is invalid. You cannot use the following names (LPTn, COMn, PRN, AUX, NUL, CON) as they are reserved by ...
  69. The filename '%3' is unsupported. You cannot use the following names (LPTn, COMn, PRN, AUX, NUL, CON) as they are reserved ...
  70. The FileName input parameter is a string representing the fully qualified name of the copy of the file (or directory). Example: ...
  71. The FileName input parameter is a string representing the fully qualified name of the copy of the file (or directory). Example: ...
  72. The FileName input parameter is a string representing the new name for the logical file (or directory). The FileName input ...
  73. The FileName parameter was not specified. The FileName parameter is required when Import-LocalizedData is not called from ...
  74. The files cannot be added to the Briefcase because it is on a read-only disk or share. Make the Briefcase writable, then ...
  75. The files cannot be added to the Briefcase because the disk is full. Remove some files from the disk, or move the Briefcase ...