Windows 8

  1. The requested value was not set by the filter process. This is a recoverable internal error. The document may still succeed. ...
  2. The requester specified invalid or unsupported backup options for virtual machine '%1': %3 (%4). (Virtual machine ID %2) ...
  3. The requester specified the VSS_ONLUNSTATECHANGE_DO_MASK_LUNS flag when calling the BreakSnaphsotSetEx method, but the hardware ...
  4. The RequestSecurityToken message received was not in the correct format. Binary secret type '%1' was specified but '%2' was ...
  5. The RequestSecurityToken message received was not in the correct format. The element with name '%1' and namespace '%2' was ...
  6. The RequestSecurityToken message received was not in the correct format. The element with name '%1' and namespace '%2' was ...
  7. The RequestSecurityToken message received was not in the correct format. Token type '%1' was specified but '%2' was expected. ...
  8. The RequestSecurityTokenResponse message received was not in the correct format. Algorithm '%1' was specified but '%2' was ...
  9. The RequestSecurityTokenResponse message received was not in the correct format. AppliesTo URL '%1' was specified but '%2' ...
  10. The RequestSecurityTokenResponse message received was not in the correct format. Key type '%1' was specified but '%2' was ...
  11. The RequestSecurityTokenResponse message received was not in the correct format. RequestType '%1' was specified but '%2' ...
  12. The RequestSecurityTokenResponse message received was not in the correct format. The element with name '%1' and namespace ...
  13. The RequestSecurityTokenResponse message received was not in the correct format. The element with name '%1' and namespace ...
  14. The RequestSecurityTokenResponse message received was not in the correct format. The element with name '%1' and namespace ...
  15. The RequestSecurityTokenResponse message received was not in the correct format. The element with name '%1' and namespace ...
  16. The required assemblies to run the virtual machine management tools were not found on the system. You can install these tools ...
  17. The required assemblies to run the virtual machine management tools were not found on the system. You can install these tools ...
  18. The required buffer size is greater than the buffer size passed to the collect function of the "%1!s!" Extensible Counter ...
  19. The required cluster version in order to run this test is not met. The cluster {0} is a {1} cluster (version {2}). A {3} ...
  20. The required files are already installed on your hard disk. Setup can use these existing files, or Setup can recopy them ...
  21. The required GPU resources could not be accessed. This server cannot run as a RemoteFX host without a GPU. Verify that the ...
  22. The required module '{0}' is not loaded. The module '{0}' has a requiredModule '{1}' in its module manifest '{2}' that points ...
  23. The required module '{0}' with GUID '{1}' and version '{2}' was not loaded because no valid module file was found in any ...
  24. The required module '{1}' with GUID '{2}' is not loaded. Load the module or remove the module from 'RequiredModules' in the ...
  25. The required module '{1}' with version '{2}' is not loaded. Load the module or remove the module from 'RequiredModules' in ...
  26. The required parameter of ProxyAuthenticationScheme or ProxyAuthenticationCredential is not specified. The two parameters ...
  27. The required role or feature for this clustered role cannot be found on any node. To add roles or features, use Server Manager. ...
  28. The required role or feature for this clustered role cannot start on any node, or requires additional configuration steps. ...
  29. The required role or feature for this clustered role is either missing or cannot be verified as installed on the following ...
  30. The required role or feature, '{0}', cannot start on any node, or requires additional configuration steps. To configure roles ...
  31. The required role or feature, '{0}', is either missing or cannot be verified as installed on the following node(s): {1}. ...
  32. The required security upgrade cannot be validated. Try installing the latest Internet Explorer service pack. To install the ...
  33. The required services cannot be configured to start automatically. Review the way your services are configured, restart Windows ...
  34. The required Windows Media Digital Rights Management (DRM) component cannot be validated. You might be able to resolve the ...
  35. The required Windows Media Digital Rights Management (DRM) component cannot be validated. You might be able to resolve the ...
  36. The reservation specified does not fall within any configured address range. Reserve only addresses that fall within a configured ...
  37. The reserve page set for the virtualization infrastructure driver is too small to use in the lock request. Restarting the ...
  38. The resident attribute for attribute of type 4 and instance tag 5 is incorrect. The attribute has value of length 1, and ...
  39. The resident attribute name is colliding with the resident value for attribute of type 4 and instance tag 5. The attribute ...
  40. The resolution requested by the remote client could not be set. The default resolution will be set for the RemoteFX session. ...
  41. The resolution requested by the remote client is not supported by RemoteFX. The connection will be made with RemoteFX using ...
  42. The resource allocation policy "{0}" will be deleted and all references to it in Calendar events and Schedules will be replaced ...
  43. The resource allocation policy %1 could not be set as the managing/profiling policy. Resource allocation policy: %1 User ...
  44. The resource allocation policy %1 could not be set as the managing/profiling policy.%r%rResource allocation policy: %1%r%rUser ...
  45. The resource allocation policy %1 was set as the managing policy at service start time.%r%rResource allocation policy: %1 ...
  46. The resource allocation policy %1 was set as the managing policy by the calendar event %2. Resource allocation policy: %1 ...
  47. The resource allocation policy %1 was set as the managing policy by the calendar event %2.%r%rResource allocation policy: ...
  48. The resource allocation policy %1 was set as the managing policy by the user %2. Resource allocation policy: %1 User: %2 ...
  49. The resource allocation policy %1 was set as the managing policy by the user %2.%r%rResource allocation policy: %1%rUser: ...
  50. The resource allocation policy %1 was set as the managing policy upon triggering of the "%2 Node is Down" condition. Resouce ...
  51. The resource allocation policy %1 was set as the managing policy upon triggering of the "%2 Node is Down" condition. Resouce ...
  52. The resource allocation policy %1 was set as the managing policy upon triggering of the "%2 Node is Up" condition. Resouce ...
  53. The resource allocation policy %1 was set as the managing policy upon triggering of the "%2 Node is Up" condition. Resouce ...
  54. The resource allocation policy %1 was set as the managing policy upon triggering of the "%2 Resource Group is Offline" condition.%r%rResouce ...
  55. The resource allocation policy %1 was set as the managing policy upon triggering of the "%2 Resource Group is Offline" condition.%r%rResouce ...
  56. The resource allocation policy %1 was set as the managing policy upon triggering of the "%2 Resource Group is Online" condition.%r%rResouce ...
  57. The resource allocation policy %1 was set as the managing policy upon triggering of the "%2 Resource Group is Online" condition.%r%rResouce ...
  58. The resource allocation policy %1 was set as the managing policy upon triggering of the "Memory Greater Than %2" condition. ...
  59. The resource allocation policy %1 was set as the managing policy upon triggering of the "Memory Greater Than %2" condition. ...
  60. The resource allocation policy %1 was set as the managing policy upon triggering of the "New Memory Added" condition. Resouce ...
  61. The resource allocation policy %1 was set as the managing policy upon triggering of the "New Memory Added" condition. Resouce ...
  62. The resource allocation policy %1 was set as the managing policy upon triggering of the "New Processor Added" Condition. ...
  63. The resource allocation policy %1 was set as the managing policy upon triggering of the "New Processor Added" Condition. ...
  64. The resource allocation policy %1 was set as the managing policy upon triggering of the "Processor Greater Than %2" condition. ...
  65. The resource allocation policy %1 was set as the managing policy upon triggering of the "Processor Greater Than %2" condition. ...
  66. The resource allocation policy %1 was set as the managing policy upon triggering of the"%2 Node is Down" Condition.%r%rResouce ...
  67. The resource allocation policy %1 was set as the managing policy upon triggering of the"%2 Node is Up" Condition.%r%rResouce ...
  68. The resource allocation policy %1 was set as the managing policy upon triggering of the"%2 Resource Group is Offline" Condition.%r%rResouce ...
  69. The resource allocation policy %1 was set as the managing policy upon triggering of the"%2 Resource Group is Online" Condition.%r%rResouce ...
  70. The resource allocation policy %1 was set as the managing policy upon triggering of the"Memory Greater Than %2" Condition.%r%rResouce ...
  71. The resource allocation policy %1 was set as the managing policy upon triggering of the"New Memory Added" Condition.%r%rResouce ...
  72. The resource allocation policy %1 was set as the managing policy upon triggering of the"New Processor Added" Condition.%r%rResouce ...
  73. The resource allocation policy %1 was set as the managing policy upon triggering of the"Processor Greater Than %2" Condition.%r%rResouce ...
  74. The resource allocation policy %1 was set as the profiling policy at service start time.%r%rResource allocation policy: %1 ...
  75. The resource allocation policy %1 was set as the profiling policy by the user %2. Resource allocation policy: %1 User: %2 ...