Windows 8

  1. The File Server Resource Manager global configuration cannot be accessed since the cluster service is not running. Please ...
  2. The File Server Resource Manager Reports service is shutting down due to shutdown event from the Service Control Manager. ...
  3. The File Server Resource Manager server is managed remotely using the File Server Resource Manager snap-in or the dirquota.exe, ...
  4. The File Server Resource Manager service could not send email due to an error. Check the application event log for more information. ...
  5. The File Server Resource Manager service encountered an unexpected error. Check the application event log for more information. ...
  6. The File Server Resource Manager service failed to analyze the mount points under the volume mounted at {0}. Please reconfigure ...
  7. The File Server Resource Manager service failed to analyze the namespaces for volume mounted at {0}. Please reconfigure the ...
  8. The File Server Resource Manager service, or Storage Reports Manager service is either not running or was restarted. Closing ...
  9. The File Server Storage Reports Manager service implements the runtime functionality to run file server storage reports, ...
  10. 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 ...
  11. The file system container attempted to insert a file name twice. This is invalid, the wim service should only receive one ...
  12. The file system detected a corruption on a file. The file has been removed from the file system namespace. The name of the ...
  13. The file system detected a corruption on a file. The file system may have failed to remove it from the file system namespace. ...
  14. The file system detected a corruption on a folder. Contents of the folder have been removed from the file system namespace. ...
  15. The file system detected a corruption on a folder. The file system may have failed to remove contents of the folder from ...
  16. The file system for one or more partitions on the disk for resource '%1' may be corrupt. Run the Validate a Configuration ...
  17. The file system on volume "%1" is potentially corrupted. Please run the CHKDSK utility to verify and fix the file system. ...
  18. The file system on volume '%1' is potentially corrupted. Please run the CHKDSK utility to verify and fix the file system. ...
  19. The file system size is larger than the partition size in the partition table. This drive may be corrupt or may have been ...
  20. The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the device %1 with label ...
  21. The file system structure that maintains security information on volume %1 (%2) has grown excessively large and fragmented. ...
  22. The file system was unable to write metadata to the media backing volume %2. A write failed with status "%3" ReFS will take ...
  23. The file that was specified as a target is a directory and the caller specified that it could be anything but a directory. ...
  24. The file that you are trying to use requires a software component on your computer to be upgraded. We recommend that you ...
  25. The file type association details in the database are corrupted. More than one file type association is published for the ...
  26. The file type is not recognized and cannot be played. Either the correct codec (a file that compresses/decompresses audio ...
  27. The file version entered contains one or more parts that are greater than the maximum value of a WORD (16-bit number). Should ...
  28. The file was in use and could not be classified. Another attempt to classify the file will be made after the retry period. ...
  29. The file was modified during this classification session so its properties will not be updated. Another attempt to update ...
  30. The file was not downloaded because the server where the file is stored redirected the request to a web page. This might ...
  31. The file with extension %1 cannot be faxed because faxing requires the file to be rendered to TIF. This file cannot be rendered ...
  32. The file you are attempting to play has an extension (.%s) that does not match the file format. Playing the file may result ...
  33. The file you are attempting to preview could harm your computer. If you trust the file and the source you received it from, ...
  34. The file you are downloading cannot be opened by the default program. It is either corrupted or it has an incorrect file ...
  35. The file you are downloading has been reported to be unsafe. The download website contains links to viruses or other software ...
  36. The file you are downloading has been reported to be unsafe. The download website contains links to viruses or other software ...
  37. The file you entered is not a unattend setup information file (SIF) or the SIF is not portable to other images. Only SIFs ...
  38. The file {0} is not digitally signed. The script will not execute on the system. For more information, see about_Execution_Policies ...
  39. The file {0} you are trying to play does not have a license. Try playing the file using Windows Media Player to acquire a ...
  40. The filename '%1' is invalid. You cannot use the following names (LPTn, COMn, PRN, AUX, NUL, CON) as they are reserved by ...
  41. The filename '%3' is unsupported. You cannot use the following names (LPTn, COMn, PRN, AUX, NUL, CON) as they are reserved ...
  42. The FileName parameter was not specified. The FileName parameter is required when Import-LocalizedData is not called from ...
  43. The files cannot be added to the Briefcase because it is on a read-only disk or share. Make the Briefcase writable, then ...
  44. The files cannot be added to the Briefcase because the disk is full. Remove some files from the disk, or move the Briefcase ...
  45. The files cannot be added to the Briefcase because the disk is inaccessible. Verify that the disk is accessible, then click ...
  46. The files cannot be added to the Briefcase because the source cannot be opened. Verify that the files are accessible, then ...
  47. The files could not be imported because they were compiled for a different processor type than the components already installed ...
  48. The files do not fit to the boot-block configuration file %1. Change the BASE and ORG definitions or the order of the files. ...
  49. The files for this update failed to download. The update can be approved but will not be available to computers until the ...
  50. The files for this update have not yet been downloaded. The update can be approved but will not be available to computers ...
  51. The files needed to create a system repair disc were not found on this computer. You can still create a system repair disc ...
  52. The files or folders encrypted using the previous smart card can only be accessed by using that card or by an administrator ...
  53. The files, settings, and applications are moved to the newer Hyper-V Server with this option. This option is only available ...
  54. The files, settings, and applications aren't moved to the newer version of Hyper-V Server with this option. If you want to ...
  55. The FileSystem Disk Activity performance counter set consists of counters that measure the aspect of filesystem's IO Activity. ...
  56. The FileSystem provider supports credentials only on the New-PSDrive cmdlet. Perform the operation again without specifying ...
  57. The filter contains a property (%1) that is of an unsupported type. Filtering is not supported on properties with the following ...
  58. The filter daemon process MSFTEFD exited unexpectedly because of document %1. Batch Id: %2 Locale Id: %3 Property Id: %4 ...
  59. The filter daemon process MSFTEFD timed out for an unknown reason. This may indicate a bug in a filter, wordbreaker, or protocol ...
  60. The filter dialect (the type associated with the filter) was not supported for this resource. Change the filter dialect or ...
  61. The filter host process cannot be started. The system is most likely low on resources, or the filter host process binary ...
  62. The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been ...
  63. The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been ...
  64. The Filter Manager had an internal error from which it cannot recover, therefore the operation has been failed. This is usually ...
  65. The Filter Manager had an internal error from which it cannot recover, therefore the operation has been failed. This is usually ...
  66. The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded ...
  67. The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded ...
  68. The filter must cleanup any operation specific context at this time because it is being removed from the system before the ...
  69. The filter must cleanup any operation specific context at this time because it is being removed from the system before the ...
  70. The filter or custom view you are creating references more than {0} event logs. The result might perform poorly and consume ...
  71. The filter process cannot be started. The system is most likely low on resources, or the filter process binary was modified. ...
  72. The filtering process ended and is now unavailable. The address will be retried, but it is possible that the system is low ...
  73. The firewall exception to allow Internet Storage Name Server (iSNS) client functionality is not enabled. iSNS client functionality ...
  74. The firewall exception, Windows Peer-to-Peer Collaboration Foundation, is blocked by group policy. Talk to your administrator ...
  75. The firewall exception, Windows Peer-to-Peer Collaboration Foundation, is disabled. The exception can be enabled by accepting ...