Windows 8.1

  1. Failover protocol message UPDREQALL from server %1 for failover relationship %2 was rejected because message digest was not ...
  2. Failover protocol message UPDREQALL from server {0} for failover relationship {1} is rejected because message digest was ...
  3. Failover protocol message UPDREQALL from server {0} for failover relationship {1} was rejected because message digest failed ...
  4. Failover protocol message UPDREQALL from server {0} for failover relationship {1} was rejected because message digest was ...
  5. Failure HCAP Response was returned with result code %1 HCAP client host name: %2 HCAP client IP address: %3 Request ID: %4 ...
  6. Failure in binding to default Active Directory Domain Services server on localhost. %rMake sure user has credentials to access ...
  7. Failure involving Persistent Reservation REGISTER. After a REGISTER call using invalid RESERVATION KEY 0x{0:x}, valid SERVICE ...
  8. Failure issuing call to Persistent Reservation CLEAR on Test Disk {0} from node {1} when another node has reserved the disk. ...
  9. Failure issuing call to Persistent Reservation PREEMPT on Test Disk {0} from node {1} using RESERVATION KEY 0x{2:x} and SERVICE ...
  10. Failure issuing call to Persistent Reservation READ RESERVATION on Test Disk {0} from node {1} when that node has successfully ...
  11. Failure issuing call to Persistent Reservation REGISTER AND IGNORE EXISTING on Test Disk {0} from node {1} when the disk ...
  12. Failure issuing call to Persistent Reservation REGISTER AND IGNORE EXISTING on Test Disk {0} from node {1} while being reserved ...
  13. Failure issuing call to Persistent Reservation REGISTER AND IGNORE EXISTING to unregister a key on Test Disk {0} from node ...
  14. Failure issuing call to Persistent Reservation REGISTER AND IGNORE EXISTING to unregister key 0x{0:0} using RESERVATION KEY ...
  15. Failure issuing call to Persistent Reservation REGISTER AND IGNORE EXISTING to unregister key for Test Disk {0} from node ...
  16. Failure issuing call to Persistent Reservation REGISTER AND IGNORE EXISTING to unregister on Test Disk {0} from node {1}. ...
  17. Failure issuing call to Persistent Reservation REGISTER AND IGNORE EXISTING. SERVICE ACTION RESERVATION KEY 0x{0:x} for Test ...
  18. Failure issuing call to Persistent Reservation REGISTER. RESERVATION KEY 0x{0:x} SERVICE ACTION RESERVATION KEY 0x{1:x} for ...
  19. Failure issuing call to Persistent Reservation REGISTER. RESERVATION KEY 0x{0:x} SERVICE ACTION RESERVATION KEY 0x{1:x} for ...
  20. Failure issuing call to Persistent Reservation REGISTER. RESERVATION KEY 0x{0:x}, SERVICE ACTION RESERVATION KEY 0x{1:x} ...
  21. Failure issuing call to Persistent Reservation RESERVE on Test Disk {0} from node {1} when that node has successfully registered. ...
  22. Failure occured while attempting to process application manifest {0}. Please ensure that your application is installed correctly ...
  23. Failure occurred during testing, Error code {0} occurred while running {1}. Please consider re-running the test and avoid ...
  24. Failure occurred while configuring the system for testing. Please consider re-running the test and avoid running applications ...
  25. Failure occurred while processing application {0}. Please consider re-running the test and avoid interacting with the application ...
  26. Failure occurred while reading configuration file entries. The configuration file was missing or an entry was missing from ...
  27. Failure occurred while reading configuration parameters from the configuration file. Please verify that {0} was correctly ...
  28. Failure reading password sync configuration. %rApply configuration changes again and if the problem persists, contact your ...
  29. Failure to get the requested feature {0} information from the target machine. Wildcard pattern is not supported in the feature ...
  30. Failure while validating Server Message Block (SMB) share access. Cluster Shared Volumes are not enabled on node {0}. Cluster ...
  31. Failure while validating Server Message Block (SMB) share access. The Cluster service is not running on node {0}. The Cluster ...
  32. Failure. After UNREGISTER, unexpected Persistent Reservation Registration key 0x{0:x} found for Test Disk {1} from node {2}. ...
  33. Failure. Persistent Reservation not present on Test Disk {0} from node {1} after failed call to invalid registration key ...
  34. Failure. Persistent Reservation not present on Test Disk {0} from node {1} after successful call to update reservation holder's ...
  35. Failure. Persistent Reservation not present on Test Disk {0} from node {1} after successful call to update reservation holder's ...
  36. Failure. Persistent Reservation not present on Test Disk {0} from node {1} after successful call using the RESERVE service ...
  37. Failure. Persistent Reservation not present on Test Disk {0} from node {1} after successful call using the RESERVE service ...
  38. Failure. Persistent Reservation READ KEYS for Test Disk {0} from node {1} found a Registration key(s). This is not expected. ...
  39. Failure. Persistent Reservation Registration key 0x{0:x} found for Test Disk {1} from node {2} after successful call to PREEMPT ...
  40. Failures Adapter is the number of connections that were dropped due to an adapter failure. This number is an accumulator ...
  41. Failures have occurred during migration of MTS packages and program settings to COM+ applications and program settings. See ...
  42. Failures Link is the number of connections that were dropped due to a link failure. This number is an accumulator and shows ...
  43. Failures No Listen is the number of connections that were rejected because the remote computer was not listening for connection ...
  44. Failures Not Found is the number of connection attempts that failed because the remote computer could not be found. This ...
  45. Failures Resource Local is the number of connections that failed because of resource problems or shortages on the local computer. ...
  46. Failures Resource Remote is the number of connections that failed because of resource problems or shortages on the remote ...
  47. Family Safety can't monitor an administrator account. To monitor this account with Family Safety, you must change it to a ...
  48. Family Safety can't monitor Guest accounts. It's a good idea to turn off Guest accounts if you're using Family Safety for ...
  49. Family Safety can't monitor this account because it's the only local administrator account. Do you want to create a standard ...
  50. Family Safety has blocked this download To find out why this download is blocked, check your Family Safety settings. If you ...
  51. Family Safety monitoring will be turned on for this account when your child signs in to this PC for the first time. You can ...
  52. Family Safety monitoring will be turned on for this account. You can always change what your child sees in the Windows Store ...
  53. Family Safety monitoring will be turned on for this account. You can always change what your child sees in the Windows Store ...
  54. Fast re-authentication was terminated and a full authentication was initiated because the client and server were out of sequence ...
  55. Fast Read Not Possibles/sec is the frequency of attempts by an Application Program Interface (API) function call to bypass ...
  56. Fast Read Resource Misses/sec is the frequency of cache misses necessitated by the lack of available resources to satisfy ...
  57. Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the ...
  58. FastPurple installs drivers that are incompatible with this 64bit version of Windows. Installing this application may cause ...
  59. FAT32 is not recognized by the disk utilities in Norton Utilities 2.0. Using Disk Doctor or Speed Disk on a drive formatted ...
  60. Fatal System Error} The %hs system process terminated unexpectedly with a status of 08x ( 08x 08x). The system has been shut ...
  61. Fatal System Error} The system image %s is not properly signed. The file has been replaced with the signed file. The system ...
  62. Fatal System Error} The system image %s is not properly signed. The file has been replaced with the signed file. The system ...
  63. Fault bucket %1, type %2 Event Name: %3 Response: %4 Cab Id: %5 Problem signature: P1: %6 P2: %7 P3: %8 P4: %9 P5: %10 P6: ...
  64. Faulting application name: %1, version: %2, time stamp: 3 Faulting module name: %4, version: %5, time stamp: 6 Exception ...
  65. Fax %1 cannot be archived to %2. Verify that archive folder %2 exists and that it has write permissions for the Network Service ...
  66. Fax Cover Page Editor Cover Page Cover Page Editor Document Fax Cover Page Files (*.cov) .cov FaxCover.Document Fax Cover ...
  67. Fax Sent. Sender: %1. Billing code: %2. Sender company: %3. Sender dept: %4. Receiver CSID: %5. Pages: %6. Transmission time: ...
  68. Fax Server sends and receives faxes and allows you to manage fax resources such as jobs, settings, reports, and fax devices ...
  69. Fax Service could not initialize any Fax Service Provider (FSP). No faxes can be sent or received until a provider is installed.%r%r ...
  70. Fax Service could not initialize Fax Service Provider '%1' because it failed to load the required Extended FSPI interface.%r%r ...
  71. Fax Service could not initialize Fax Service Provider '%1' because it failed to load the required Legacy FSPI interface.%r%r ...
  72. Fax Service could not initialize Fax Service Provider '%1' because it provided an interface version (%3) that is not supported.%r%r ...
  73. Fax Service could not initialize Fax Service Provider '%1' because its registration data is not valid.%r%r Fax Service Provider ...
  74. Fax Service could not initialize Fax Service Provider '%1' because of an internal error.%r%r Fax Service Provider Path: '%2'%r%r ...
  75. Fax Service could not initialize Fax Service Provider '%1' because of an internal error.%r%r Fax Service Provider Path: '%2'%r%r ...