Windows 8

  1. The Root Certification Authority for the server's certificate is: %ws If this is the correct certificate, click OK to connect ...
  2. The root cluster {0} has not been updated to cryptographic mode 2. You must first update the cryptographic mode on the root ...
  3. The root cluster's cryptographic mode is invalid or this process could not manage to get the cryptographic mode from root ...
  4. The Root Domain Check detected a condition in your environment that is out of compliance with the licensing policy. This ...
  5. The root element of target document '{0}' is not '{1}' (or a substitution of '{1}', with derivations by '{2}' excluded). ...
  6. The root folder on this volume is full. To perform a disk check, Windows requires space in the root folder. Remove some files ...
  7. The root memory reserve key (HKLM\Software\Microsoft\Windows NT\CurrentVersion\Virtualization\MemoryReserve) is set too low. ...
  8. The root node cannot be set after the SnapIn instance is initialized. Consider adding the root node in the constructor of ...
  9. The root of drive %3 is formatted with the FAT file system and can only store a limited number of items. Store the items ...
  10. The root trust anchors were successfully retrieved and added as DS trust anchors. They will become effective when the server ...
  11. The root zone was deleted from the server. Root hints must be supplied to allow recursive queries. Would you like to add ...
  12. The RootDSE could not be retrieved from the directory. Please specify filter for the enumerate request under such circumstances. ...
  13. The round robin with subset policy executes the round robin policy only on paths designated as active. The standby paths ...
  14. The round robin with subset policy executes the round robin policy only on paths designated as active/optimized. The non-active/optimized ...
  15. The Routing and Remote Access service could not start. The most common reason could be because %1 protocol is not installed ...
  16. The Routing and Remote Access Service is in the process of stopping. Until it stops, the Incoming Connections option is not ...
  17. The Routing and Remote Access service is in the process of stopping. Until it stops, the Incoming Connections option is not ...
  18. The Routing and Remote Access Service is not currently running on %1!s!. Please use 'net start remoteaccess' on the machine ...
  19. The Routing and Remote Access Service is not currently running on %1!s!. Use 'net start remoteaccess' on the remote machine ...
  20. The Routing and Remote Access Service is not currently running on the local machine. Please use 'net start remoteaccess' ...
  21. The Routing and Remote Access Service is not currently running on the local machine. Use 'net start remoteaccess' on the ...
  22. The Routing and Remote Access service is not running. You cannot add and configure interfaces unless the service is running. ...
  23. The Routing and Remote Access service may not have been restarted because the following error occurred when trying to query ...
  24. The Routing and Remote Access Service needs to be restarted for this setting to take effect. Use 'net stop remoteaccess' ...
  25. The RPC binding failed in the Collect function of the FileReplicaConn Object. The counter data for this object will not be ...
  26. The RPC binding failed in the Collect function of the FileReplicaSet Object. The counter data for this object will not be ...
  27. The RPC binding failed in the Open function of the FileReplicaConn Object. The counter data for this object will not be available. ...
  28. The RPC binding failed in the Open function of the FileReplicaSet Object. The counter data for this object will not be available. ...
  29. The RPC call failed in the Collect function of the FileReplicaConn Object. The counter data for this object will not be available ...
  30. The RPC call failed in the Collect function of the FileReplicaSet Object. The counter data for this object will not be available ...
  31. The RPC call failed in the Open function of the FileReplicaConn Object. The counter data for this object will not be available. ...
  32. The RPC call failed in the Open function of the FileReplicaSet Object. The counter data for this object will not be available. ...
  33. The RPC server is unavailable. Please enable the Netlogon Service Authz (RPC) firewall rule on the target server and try ...
  34. The RPC/HTTP Proxy object contains the counters that display information for RPC/HTTP proxy sizing, trouble shooting and ...
  35. The RPC/HTTP Proxy per Server object contains the counters that display information for RPC/HTTP proxy sizing, trouble shooting ...
  36. The RPCSS service is the Service Control Manager for COM and DCOM servers. It performs object activations requests, object ...
  37. The RRAS server is configured to accept remote access connections that are not authenticated, or that are authenticated with ...
  38. The RRAS server is configured to use DHCP to obtain IP addresses for remote access clients, but the network adapter through ...
  39. The RSOP Security Settings Extension snap-in extends the RSOP snap-in and helps you view resultant security policies for ...
  40. The RSoP snap-in was unable to generate the computer's data due to insufficient permissions. The snap-in will continue to ...
  41. The RSoP snap-in was unable to generate the RSoP data because the target computer is currently running RSoP or processing ...
  42. The RSoP snap-in was unable to generate the user's data due to insufficient permissions. The snap-in will continue to start ...
  43. The rule is from a later version of the service. Some fields were not understood and have been ignored. This may cause the ...
  44. The rule is from a newer schema version than the service, and the unknown fields could not be ignored. The whole rule was ...
  45. The rules attached to the trigger %1 with the ID %2 are now valid. All the rules were evaluated successfully, and the actions ...
  46. The Run Continuously On New Files option cannot be selected. Notifications must not be specified and no date conditions, ...
  47. The run-time environment has detected an inconsistency in its internal state. This indicates a potential instability in the ...
  48. The run-time environment has detected the absence of a critical resource and has caused the process that hosted it to terminate. ...
  49. The run-time environment was unable to initialize for transactions required to support transactional components. Make sure ...
  50. The RunAsPassword value cannot be removed. Remove the values for RunAsUser and RunAsPassword in PowerShell by calling the ...
  51. The running command has been disconnected but is still running on the remote server. Reconnect to get command operation status ...
  52. The SAM database attempted to clear the directory %1 in order to remove files that were once used by the Directory Service. ...
  53. The SAM database attempted to delete the file %1 as it contains account information that is no longer used. The error is ...
  54. The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete ...
  55. The SAM database was unable to lockout the account of %1 due to a resource error, such as a hard disk write failure (the ...
  56. The saved console file was created with a different, incompatible version of the Local Users and Groups snap-in than the ...
  57. The SaveDelay parameter is currently set to %1 milliseconds. The idle timer was not set because Remote Desktop Virtualization ...
  58. The scan instructions contain a destination that is not recognized by the scan server. PSP Identifier (GUID): %1. PostScanJob ...
  59. The scan process was created, but an Active Directory constraint violation occurred while security settings were being applied. ...
  60. The scan server cannot support any destinations. Select another scan server or reinstall the Distributed Scan Server role ...
  61. The Scan Server Configuration Wizard failed to restart the Distributed Scan Server service. Please restart the service manually. ...
  62. The scanned images were successfully saved to the network resource. Submitting Username: %1. Job Token: %2. Filter Dialect: ...
  63. The scanned images were successfully saved to the Windows SharePoint Services site. Submitting Username: %1. Job Token: %2. ...
  64. The scanner does not support the default settings for scan to fax. Click OK to scan with the scanner's default settings, ...
  65. The scanning software could not be found, or your scanner is not connected. Please make sure your scanner and your scanning ...
  66. The Scavenger thread encountered an error while cleaning up the owner-address table. It will try again after the Verify interval ...
  67. The Scavenger thread found active replicas that needed to be verified with the owner WINS server since they were older than ...
  68. The scenario %1 has a configuration error or has been explicitly disabled in the WDI registry namespace. The Diagnostic Policy ...
  69. The Scenario Event Mapper is configured with an unsupported scenario. The scenario for provider %1 (event ID %2) encountered ...
  70. The Scenario Event Mapper is configured with more than the maximum number of context providers for the scenario with provider ...
  71. The Scenario Event Mapper is configured with more than the maximum number of end events for the scenario with provider %1 ...
  72. The Scenario Event Mapper is configured with more than the maximum number of providers. The provider %1 will be ignored. ...
  73. The Scenario Event Mapper is configured with more than the maximum number of scenarios. The scenario for provider %1 (event ...
  74. The Scenario Event Mapper started a scenario for provider %1 (event ID %2) with %4 context providers. The context logger ...
  75. The Scenario Event Mapper stopped a scenario for provider %1 (event ID %2) with %4 context providers. The context logger ...