Windows 8

  1. The member {0} has one or more primary memberships. If this member is deleted then you must manually configure new primary ...
  2. The membership {0} cannot be modified to use shared staging. Shared staging is not supported on memberships that are part ...
  3. The memory block page for the virtualization infrastructure driver cannot be mapped because the page map limit has been reached. ...
  4. The memory configuration for one or more virtual machines might require the use of Smart Paging if the virtual machine is ...
  5. The memory mapped I/O for this page range no longer exists. Restarting the virtual machine may fix the problem. If the problem ...
  6. The memory page at physical address %1 has encountered multiple corrected hardware error events. As a result it will no longer ...
  7. The Memory performance object consists of counters that describe the behavior of physical and virtual memory on the computer. ...
  8. The menu command you select can be applied to any of the items in the details pane. When you run the task, you must select ...
  9. The message at which the cursor is currently pointing was removed from the queue by another process or by another call to ...
  10. The message could not be moved to deadletter queue %1. Deadletter queues should not require privacy of messages. The message ...
  11. The message could not be moved to deadletter queue %1. The deadletter queue is authenticated and the authenticity of the ...
  12. The message could not be moved to deadletter queue %1. The deadletter queue needs to be transactional. The message will be ...
  13. The message could not be moved to deadletter queue %3. Check that queue exists and users have permissions to send. The message ...
  14. The message has been sent, but the connected workstation has not received it. The workstation is running an unsupported version ...
  15. The message is currently being processed under a transaction. Till the transaction outcome is determined, the message cannot ...
  16. The message might have been one that required no action, such as a quick status notification. Windows will notify you if ...
  17. The message queue for the virtualization infrastructure driver has been closed. Restarting the virtual machine may fix the ...
  18. The message queue for the virtualization infrastructure driver is full and cannot accept new messages. Restarting the virtual ...
  19. The message queue is not empty. The logging data in the queue must be processed before the cryptographic mode can be updated. ...
  20. The Message Queuing directory service failed to update the directory service flag in Active Directory Domain Services at ...
  21. The Message Queuing directory service failed to update the directory service flag in Active Directory Domain Services during ...
  22. The Message Queuing directory service is not running as a local system. To get the directory service functionality, you need ...
  23. The Message Queuing DLL or the entry point in that DLL for the specified procedure cannot be found. You can turn on tracing ...
  24. The Message Queuing resource failed to come online. The Message Queuing resource depends on the network name resource with ...
  25. The Message Queuing Security page cannot be displayed. Message Queuing may not be properly installed. Please reinstall Message ...
  26. The Message Queuing serivce performance counter data are not available. The performance counter module failed to initialize. ...
  27. The Message Queuing server cannot determine if the local domain controller is trusted for delegation. This may indicate a ...
  28. The Message Queuing service cannot communicate with other computers, because the RPC interface cannot use the TCP/IP protocol. ...
  29. The Message Queuing service cannot communicate with other computers, because the select API for socket failed. Error %1: ...
  30. The Message Queuing service cannot join the '%1' Windows NT 4.0 domain. The Active Directory Domain Services Integration ...
  31. The Message Queuing service cannot start because a queue is in an inconsistent state. For more information, see Microsoft ...
  32. The Message Queuing service cannot start. A connection with the Distributed Transaction Coordinator cannot be established. ...
  33. The Message Queuing service cannot start. The Active Directory Domain Services interface cannot be initialized. Error %1: ...
  34. The Message Queuing service cannot start. The checkpoint files cannot be recovered. To start the Message Queuing service ...
  35. The Message Queuing service cannot start. The internal private queue '%3' cannot be initialized. If the problem persists, ...
  36. The Message Queuing service cannot start. The log file cannot be recovered. To start the Message Queuing service without ...
  37. The Message Queuing service cannot start. The registry value '\HKLM\SOFTWARE\Microsoft\MSMQ\Parameters\%3' cannot be retrieved ...
  38. The Message Queuing service cannot start. The registry value '\HKLM\SOFTWARE\Microsoft\MSMQ\Parameters\%3' cannot be written ...
  39. The Message Queuing service has to be restarted for the changes to take effect. Do you want to restart the Message Queuing ...
  40. The Message Queuing service has to be restarted for the changes to take effect. Do you want to restart the Message Queuing ...
  41. The Message Queuing service is not online with Active Directory Domain Services, since the service properties cannot be retrieved ...
  42. The Message Queuing service is not online with Active Directory Domain Services. The MSMQ Configuration object (msmq) ID ...
  43. The Message Queuing service on the computer hosting the queue may be offline, or a connection with Active Directory Domain ...
  44. The Message Queuing service on this computer is now represented by a new MSMQ-Configuration object. As a result, all transactional ...
  45. The Message Queuing service rejects incoming messages when it is unable to check whether the sender is allowed access to ...
  46. The Message Queuing service resource cannot bind to the cluster IP address. This prevents the Message Queuing resource from ...
  47. The Message Queuing service was unable to obtain the properties of the msmq (MSMQ Configuration) object from Active Directory ...
  48. The Message Queuing service will not join the %1 domain. An MSMQ Configuration (msmq) object exists in the new domain with ...
  49. The Message Queuing Triggers Configuration page cannot be displayed. Message Queuing Triggers may not be properly installed. ...
  50. The Messages Queue Length performance counter shows the number of new cluster update messages waiting to be sent over the ...
  51. The Messages Received/sec performance counter shows the number of new cluster messages received on the network per second. ...
  52. The metadata cleanup for the requested server should happen on an Active Directory Domain Controller (AD DC) in the same ...
  53. The metadata of element %1 is too large. The maximum allowed size is 2048 bytes. Reduce the size of the metadata of element ...
  54. The metadata of element %1 would cause the total published metadata to be more than 32k, which is the maximum allowable size ...
  55. The method failed because the session is changing its type. No IOPMVideoOutput methods can be called when a session is changing ...
  56. The metric indicates the cost of the route. In the case of RIP routes, the cost is determined by the number of routers to ...
  57. The Microsoft "Route through e-mail" method is still enabled for at least one device. Disable the method for all remaining ...
  58. The Microsoft .NET Framework 2.0, which is required for Windows PowerShell 2.0, is not installed. Install the .NET Framework ...
  59. The Microsoft Clearinghouse could not be contacted. Ensure that you have Internet connectivity from the computer running ...
  60. The Microsoft Clearinghouse could not be contacted. It does not appear as though a network card has been installed or configured ...
  61. The Microsoft Clearinghouse could not be contacted. The Internet connection has not been configured on this computer. Ensure ...
  62. The Microsoft Clearinghouse could not be contacted. The site may not be available or you may not have Internet access from ...
  63. The Microsoft Clearinghouse server is experiencing problems. Please try this transaction later. If the problem persists, ...
  64. The Microsoft Cluster Shared Volume file system driver (CsvFS.sys) startup type on node {0} is not set to the default and ...
  65. The Microsoft Cluster Shared Volume filter driver (CSVFilter.sys) startup type on node {0} is not set to the default and ...
  66. The Microsoft Cluster Shared Volume filter driver (CsvFlt.sys) startup type on node {0} is not set to the default and recommended ...
  67. The Microsoft Cluster Shared Volume namespace filter driver (CsvNSFlt.sys) startup type on node {0} is not set to the default ...
  68. The Microsoft Cluster Shared Volume pseudo volume bus driver (csvvbus.sys) startup type on node {0} is not set to the default ...
  69. The Microsoft Customer Support representative will provide you with a confirmation code. Type this confirmation code in the ...
  70. The Microsoft Customer Support representative will provide you with a license key pack ID. Type this ID in the following ...
  71. The Microsoft Customer Support representative will provide you with a license server ID. Type this ID in the following boxes. ...
  72. The Microsoft Customer Support representative will provide you with a new license server ID. Type this ID in the following ...
  73. The Microsoft DHCP Server service is not running on the server. Only the Microsoft DHCP Server service can be configured ...
  74. The Microsoft DHCP Server service was detected as installed but not running. If you enable the DHCP Server, please consult ...
  75. The Microsoft DHCP Server service was detected but it failed to start within the expected time period. The Windows Deployment ...