Windows 10

  1. FILE Commands Supported - createnew Creates a new file of a specified size findbysid Find a file by security identifier optimizemetadata ...
  2. File Control Bytes/sec is the overall rate at which bytes are transferred for all file system operations that are neither ...
  3. File Control Operations/sec is the combined rate of file system operations that are neither reads nor writes, such as file ...
  4. File data inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required. ...
  5. File data inconsistency was detected and was repaired successfully. File name: %2 Range offset: %4 Range length (in bytes): ...
  6. File Data Operations/ sec is the combined rate of read and write operations on all logical disks on the computer. This is ...
  7. File Data Operations/sec is the rate at which the Redirector is processing data operations. One operation should include ...
  8. File data scrub operation failed. File name: %2 Range offset: %4 Range length (in bytes): %5 Bytes repaired: %6 Bytes not ...
  9. File Description: This file is the Failover Cluster tombstone file for a disk that was previously designated as a quorum ...
  10. File Explorer and Internet Explorer may be configured to prevent active content obtained through restricted protocols from ...
  11. File History can't save copies of all of your files because of limitations with your File History drive's file system. Tap ...
  12. File History can't save copies of all of your files because of limitations with your File History drive's file system. We ...
  13. File History can't save copies of files that are encrypted with Encrypting File System, on a network location, or on a drive ...
  14. File History has found files that are encrypted with Encrypting File System, on a network location, or on a drive that doesn't ...
  15. File History is scheduled to automatically restore your files. If your drive is connected, you can start restoring files ...
  16. File leasing has been disabled for the SMB2 and SMB3 protocols. This reduces functionality and can decrease performance. ...
  17. File metadata inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required. ...
  18. File metadata inconsistency was detected and was repaired successfully. File name: %2 Metadata reference: %3 Range offset: ...
  19. File metadata scrub operation failed. File name: %2 Metadata reference: %3 Range offset: %4 Range length (in bytes): %5 Bytes ...
  20. 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! ...
  21. File Read Bytes/sec is the overall rate at which bytes are read to satisfy file system read requests to all devices on the ...
  22. File Read Operations/sec is the combined rate of file system read requests to all devices on the computer, including requests ...
  23. File Read Operations/sec is the rate at which applications are asking the Redirector for data. Each call to a file system ...
  24. File Server Resource Manager applied a file management job custom action to a file. File Management Job Name: %1 Custom Action: ...
  25. File Server Resource Manager applied a file management job expiration action to a file. File Management Job Name: %1 Expiration ...
  26. File Server Resource Manager applied a file management task RMS Encryption action to a file. File management task name: %1 ...
  27. File Server Resource Manager attempted to load a disabled module. Please ensure that all enabled modules in use (by FSRM ...
  28. File Server Resource Manager cannot start file screening on this system since the cluster service is not running. Screening ...
  29. File Server Resource Manager could not add '%1' group to '%2' group. Try adding this group manually to enable Access-Denied ...
  30. File Server Resource Manager could not add the Access-Denied Assistance Users group to the Remote Management Users group. ...
  31. File Server Resource Manager could not remove the Access-Denied Assistance Users group from the Remote Management Users group. ...
  32. File Server Resource Manager encountered a malformed claim in Active Directory Domain Services (AD DS). Please reconfigure ...
  33. File Server Resource Manager encountered an error while attempting to find the network share and DFS paths that expose the ...
  34. File Server Resource Manager encountered an error while classifying a file during automatic classification. File: %1 Module: ...
  35. File Server Resource Manager encountered an error while contacting the RMS server. The error can be caused by any of the ...
  36. File Server Resource Manager encountered an error while initializing local-to-remote path mapping. Mappings from local file ...
  37. File Server Resource Manager encountered an unexpected error during volume scan of volumes mounted at '%1' ('%2'). To find ...
  38. File Server Resource Manager encountered the claim %1 in Active Directory with the same name as a local property definition. ...
  39. File Server Resource Manager failed to automatically upgrade its configuration on volume %1. The volume cannot be added to ...
  40. File Server Resource Manager failed to change or delete property definition '%1'. Please check previous event logs for details. ...
  41. File Server Resource Manager failed to create a pipeline module object. The error is: %1 See below for additional details. ...
  42. File Server Resource Manager failed to enumerate file properties because a failure occurred while loading or classifying ...
  43. File Server Resource Manager failed to enumerate share paths or DFS paths. Mappings from local file paths to share and DFS ...
  44. File Server Resource Manager failed to find the claim list '%1' in Active Directory (ADsPath: %2). Please check that the ...
  45. File Server Resource Manager failed to initialize its shadow copy writer component. Therefore, backup and restore of the ...
  46. File Server Resource Manager failed to initialize its WMI event provider component. Therefore, WMI events will not be sent ...
  47. File Server Resource Manager failed to retrieve the mount points under the volume mounted at '%1'. Make sure the volume mounted ...
  48. File Server Resource Manager failed to set a file property to the file because a failure occurred while saving the file properties. ...
  49. File Server Resource Manager failed to take a cluster resource offline for the reports scheduled task '%1'. The report task ...
  50. File Server Resource Manager failed to update property definition '%1' with data from Active Directory. The error is: %2. ...
  51. File Server Resource Manager failed to write the properties to the file because the file is either corrupt or protected by ...
  52. File Server Resource Manager finished syncing claims from Active Directory and encountered errors during the sync (%1). Please ...
  53. File Server Resource Manager finished syncing claims from Active Directory Domain Services with no errors. Details: Domain ...
  54. File Server Resource Manager global configuration cannot be accessed since the cluster service is not running. Please start ...
  55. File Server Resource Manager had a failure when invoking an COM call on an external component: This might be a problem with ...
  56. File Server Resource Manager killed the following FSRM-initiated command-line program because it exceeded its %1-minute run ...
  57. File Server Resource Manager module '%1' took too long processing file '%2'. The module was restarted and the file skipped. ...
  58. File Server Resource Manager performed the following file management job notification: File Management Job Name: %1 Notification ...
  59. File Server Resource Manager regenerated one or more records for configuration database '%1'. The new records contain no ...
  60. File Server Resource Manager Service derived a quota from an auto apply quota. Quota ID: %1 Auto apply quota ID: %2 Path: ...
  61. File Server Resource Manager Service error: A critical component required by the File Server Resource Manager Service is ...
  62. File Server Resource Manager Service error: The COM Server with CLSID %1 and name '%2' cannot be started on machine '%3' ...
  63. File Server Resource Manager Service error: The FSRM event log source EventMessageFile '%1' found in registry key '%2' is ...
  64. File Server Resource Manager Service information: The COM Server with CLSID %1 and name '%2' cannot be started on machine ...
  65. File Server Resource Manager Service information: The COM Server with CLSID %1 and name '%2' cannot be started on machine ...
  66. File Server Resource Manager Service information: Volume '%1' appears as disconnected and it is ignored by the service. You ...
  67. File Server Resource Manager set a property on a file during automatic classification. File: %1 Property Changed: %2 Property ...
  68. File Server Resource Manager set properties on a file outside of automatic classification. This can occur if a file is manually ...
  69. File Server Resource Manager successfully created a cluster resource for the reports scheduled task '%1', but failed to bring ...
  70. File Server Resource Manager was unable to access a file or volume. Details: %1 The volume may be inaccessible for I/O operations ...
  71. File Server Resource Manager was unable to access the following directory: '%1'. You must give Local System access to this ...
  72. File Server Resource Manager was unable to access the following directory: '%s'. You must give Local System access to this ...
  73. File Server Resource Manager was unable to access the following file or volume: '%1'. This file or volume might be locked ...
  74. File Server Resource Manager was unable to access volumes mounted at '%1' ('%2'). Make sure that dismount or format operations ...
  75. File Server Resource Manager was unable to create or access the shadow copy for volumes mounted at '%1' ('%2'). Possible ...