Windows 8

  1. File %1 has been orphaned since all its filenames were invalid Windows will recover the file in the orphan recovery phase. ...
  2. File %1 is not Unicode (UTF-16LE). Unable to rename it. This will block spell checkers from using wordlists in this directory. ...
  3. File %s has an unsupported format version of %s. The parser expects version %s or any other minor revision compatible with ...
  4. File and iSCSI Services provides technologies that help you manage file servers and storage, reduce disk space utilization, ...
  5. File and Print Sharing has no network binding to the fault tolerant network driver for failover clustering, NetFt, on node ...
  6. File and Storage Services includes services that are always installed, as well as functionality that you can install to help ...
  7. File Backup could not start a new backup using your existing settings for the following reason: %1!s! The configuration wizard ...
  8. FILE Commands Supported - createnew Creates a new file of a specified size findbysid Find a file by security identifier queryallocranges ...
  9. File Control Bytes/sec is the overall rate at which bytes are transferred for all file system operations that are neither ...
  10. File Control Operations/sec is the combined rate of file system operations that are neither reads nor writes, such as file ...
  11. File data inconsistency was detected and was repaired successfully. File name: %2; range offset: %4; range length: %5 bytes; ...
  12. File Data Operations/ sec is the combined rate of read and write operations on all logical disks on the computer. This is ...
  13. File Data Operations/sec is the rate at which the Redirector is processing data operations. One operation should include ...
  14. File data scrub operation failed. File name: %2; range offset: %4; range length: %5 bytes; repaired: %6 bytes; not repaired: ...
  15. File Description: This file is the Failover Cluster tombstone file for a disk that was previously designated as a quorum ...
  16. File History can't save copies of all of your files because of limitations with your File History drive's file system. Tap ...
  17. File History can't save copies of all of your files because of limitations with your File History drive's file system. We ...
  18. File History can't save copies of files that are encrypted with Encrypting File System, on a network location, or on a drive ...
  19. File History has found files that are encrypted with Encrypting File System, on a network location, or on a drive that doesn't ...
  20. File Installs Retried shows the number of file installs that are being retried due to sharing violations or other errors ...
  21. File Installs Succeeded shows the number of files that were successfully received from sending members and installed locally ...
  22. File log configuration: - Accounting = %1!s! Authentication = %2!s! Periodic accounting status = %3!s! Periodic authentication ...
  23. File metadata inconsistency was detected and was repaired successfully. File name: %2; metadata reference: %3; range offset: ...
  24. File metadata scrub operation failed. File name: %2; metadata reference: %3; range offset: %4; range length: %5 bytes; repaired: ...
  25. File Name : %1!s! Last Write Time : %2!0.2d!/%3!0.2d!/%4!0.4d! %5!0.2d!:%6!0.2d! Creation Time : %7!0.2d!/%8!0.2d!/%9!0.4d! ...
  26. File names may appear and be accessed differently depending on whether the user is using the NFS or SMB protocol to access ...
  27. File Read Bytes/sec is the overall rate at which bytes are read to satisfy file system read requests to all devices on the ...
  28. File Read Operations/sec is the combined rate of file system read requests to all devices on the computer, including requests ...
  29. File Read Operations/sec is the rate at which applications are asking the Redirector for data. Each call to a file system ...
  30. File Replication Service (FRS) supports legacy distributed files environments. If you're running in an environment with Windows ...
  31. File Replication Service has been repeatedly prevented from updating: File Name : "%1" File GUID : "%2" %rdue to consistent ...
  32. File Replication Service has detected and suppressed an average of %1 or more file updates every hour for the last %2 hours ...
  33. File Replication Service is initializing the system volume with data from another domain controller. Computer %1 cannot become ...
  34. File Replication Service is scanning the data in the system volume. Computer %1 cannot become a domain controller until this ...
  35. File Server could not start because expected dependency on 'Network Name' resource was not found or it was not configured ...
  36. File Server Resource Manager (FSRM) enables you to generate storage reports, configure quotas, and define file screening ...
  37. File Server Resource Manager (FSRM) will not function properly when resources fail over to nodes that do not have FSRM installed. ...
  38. File Server Resource Manager allows you to record file screening activity in an auditing database which can be later reviewed ...
  39. File Server Resource Manager applied a file management job custom action to a file. File Management Job Name: %1 Custom Action: ...
  40. File Server Resource Manager applied a file management job expiration action to a file. File Management Job Name: %1 Expiration ...
  41. File Server Resource Manager applied a file management task RMS Encryption action to a file. File management task name: %1 ...
  42. File Server Resource Manager attempted to load a disabled module. Please ensure that all enabled modules in use (by FSRM ...
  43. File Server Resource Manager cannot manage the computer because it is running a version of Windows Server that is earlier ...
  44. File Server Resource Manager cannot start file screening on this system since the cluster service is not running. Screening ...
  45. File Server Resource Manager could not add '%1' group to '%2' group. Try adding this group manually to enable Access-Denied ...
  46. File Server Resource Manager could not add the Access-Denied Assistance Users group to the Remote Management Users group. ...
  47. File Server Resource Manager could not load WMI objects on '{0}'. Possible causes include: The File Server Resource Manager ...
  48. File Server Resource Manager could not remove the Access-Denied Assistance Users group from the Remote Management Users group. ...
  49. File Server Resource Manager encountered a malformed claim in Active Directory Domain Services (AD DS). Please reconfigure ...
  50. File Server Resource Manager encountered an error while attempting to find the network share and DFS paths that expose the ...
  51. File Server Resource Manager encountered an error while classifying a file during automatic classification. File: %1 Module: ...
  52. File Server Resource Manager encountered an error while contacting the RMS server. The error can be caused by any of the ...
  53. File Server Resource Manager encountered an error while initializing local-to-remote path mapping. Mappings from local file ...
  54. File Server Resource Manager encountered an unexpected error during volume scan of volumes mounted at '%1' ('%2'). To find ...
  55. File Server Resource Manager encountered the claim %1 in Active Directory with the same name as a local property definition. ...
  56. File Server Resource Manager failed to automatically upgrade its configuration on volume %1. The volume cannot be added to ...
  57. File Server Resource Manager failed to change or delete property definition '%1'. Please check previous event logs for details. ...
  58. File Server Resource Manager failed to create a pipeline module object. The error is: %1 See below for additional details. ...
  59. File Server Resource Manager failed to enumerate file properties because a failure occurred while loading or classifying ...
  60. File Server Resource Manager failed to enumerate share paths or DFS paths. Mappings from local file paths to share and DFS ...
  61. File Server Resource Manager failed to find the claim list '%1' in Active Directory (ADsPath: %2). Please check that the ...
  62. File Server Resource Manager failed to initialize its shadow copy writer component. Therefore, backup and restore of the ...
  63. File Server Resource Manager failed to initialize its WMI event provider component. Therefore, WMI events will not be sent ...
  64. File Server Resource Manager failed to retrieve the mount points under the volume mounted at '%1'. Make sure the volume mounted ...
  65. File Server Resource Manager failed to set a file property to the file because a failure occurred while saving the file properties. ...
  66. File Server Resource Manager failed to take a cluster resource offline for the reports scheduled task '%1'. The report task ...
  67. File Server Resource Manager failed to update property definition '%1' with data from Active Directory. The error is: %2. ...
  68. File Server Resource Manager failed to write the properties to the file because the file is either corrupt or protected by ...
  69. File Server Resource Manager finished syncing claims from Active Directory and encountered errors during the sync (%1). Please ...
  70. File Server Resource Manager finished syncing claims from Active Directory Domain Services with no errors. Details: Domain ...
  71. File Server Resource Manager global configuration cannot be accessed since the cluster service is not running. Please start ...
  72. File Server Resource Manager had a failure when invoking an COM call on an external component: This might be a problem with ...
  73. File Server Resource Manager helps you manage and understand the files and folders on a file server by scheduling file management ...
  74. File Server Resource Manager is configured to classify read-only files, and cannot save classification properties for the ...
  75. File Server Resource Manager is stopping a file management task because it has reached its duration limit. The task might ...