Windows 8

  1. Media Center Extender Setup cannot revert changes made to the Media Center Extender exception in the Public profile of the ...
  2. Media Center Extender Setup failed as the Extender was detected on the network but the UPnP search for the Extender failed ...
  3. Media Center Extender Setup has determined that the Windows Firewall is enabled in the Domain, Home and Public profiles. ...
  4. Media Foundation , which includes Windows Media Foundation, the Windows Media Format SDK, and a server subset of DirectShow, ...
  5. Media Foundation, which includes Windows Media Foundation, the Windows Media Format SDK, and a server subset of DirectShow, ...
  6. Media Only mode keeps Windows Media Center displayed in full screen. In this mode, the minimize and close buttons are hidden. ...
  7. Media player and imaging program compatibility layers were successfully registered for device %1. Layer bits %2 were requested, ...
  8. Media sharing is currently disabled, either because the sharing service is not running or your firewall settings have changed. ...
  9. Media usage rights have previously been backed up to this folder. Do you want to replace the older usage rights with the ...
  10. Medium - Safe browsing and still functional - Prompts before downloading potentially unsafe content - Unsigned ActiveX controls ...
  11. Medium-high - Appropriate for most websites - Prompts before downloading potentially unsafe content - Unsigned ActiveX controls ...
  12. Medium-low - Appropriate for websites on your local network (intranet) - Most content will be run without prompting you - ...
  13. Medium-low - Same as Medium without prompts - Most content will be run without prompts - Unsigned ActiveX controls will not ...
  14. Members of Address-Space-Management (ASM) Administrators group have IPAM Users privileges and can perform IPAM common management ...
  15. Members of Address-Space-Management (ASM) Administrators group have IPAM Users privileges and can perform IPAM common management ...
  16. Members of Multi-Server-Management (MSM) Administrators group have IPAM Users privileges and can perform IPAM common management ...
  17. Members of Multi-Server-Management (MSM) Administrators group have IPAM Users privileges and can perform IPAM common management ...
  18. Members of the IP Audit Administrators group have IPAM Users privileges and can perform IPAM common management tasks and ...
  19. Members of the IP Audit Administrators group have IPAM Users privileges and can perform IPAM common management tasks and ...
  20. Members of the super users group are granted owner use licenses when they request a use license from this AD RMS cluster. ...
  21. Members of the super users group are granted owner use licenses when they request a use license from this AD RMS cluster. ...
  22. Members of this group can access WMI resources over management protocols (such as WS-Management via the Windows Remote Management ...
  23. Members of this group can update user accounts in Active Directory with information about license issuance, for the purpose ...
  24. Members of this group can view all information in server inventory, IP address space, and the monitor and manage view of ...
  25. Members of this group can view all information in server inventory, IP address space, and the monitor and manage view of ...
  26. Members of this group may schedule logging of performance counters, enable trace providers, and collect event traces both ...
  27. Members of this role are allowed to examine the configuration of COM+ applications and view information related to active ...
  28. Membership cannot be deleted because it is published. Deleting it would leave the DFS namespace in an inconsistent state. ...
  29. Membership for ReplicatedFolder {0} and Member {1} is not being replicated because the member {1} is referencing an invalid ...
  30. Membership in Account Operators, Domain Admins, Enterprise Admins, or equivalent, is the minimum required to enable or disable ...
  31. Membership information for this object cannot be found in the global catalog. This might occur because the global catalog ...
  32. Membership {0} cannot be enabled because it is not specified as primary. A primary membership must exist within the replication ...
  33. Membership {0} is not listed because it has not yet replicated to the domain controller that was contacted for the list of ...
  34. MEMORY DIAGNOSTIC APPLICATION The following types apply only to entries for memory diagnostic application entries. For information ...
  35. Memory problems can cause your computer to lose information or stop working. To identify and repair the problem, contact ...
  36. Memory Stats: - Memory: Total Memory = %1!10lu! Alloc Count = %2!10lu! Free Count = %3!10lu! Standard Allocs: Used = %4!10lu! ...
  37. Memory usage of a cmdlet has exceeded a warning level. To avoid this situation, try one of the following: 1) Lower the rate ...
  38. Merges a child disk with its parents. Syntax: MERGE VDISK DEPTH= DEPTH= Indicates the number of parents to merge together. ...
  39. Merging profiles adds phone book information, such as access numbers or VPN host addresses, from one or more separate profiles ...
  40. Message Queue Triggers enables the invocation of a COM component or an executable depending on the filters that you define ...
  41. Message Queuing Activation supports process activation via Message Queuing. Applications that use Message Queuing Activation ...
  42. Message Queuing cannot bind to UDP port 3527. Message Queuing's internal ping mechanism uses this port to establish network ...
  43. Message Queuing cannot establish new connections to this computer because connection limit was reached. There are too many ...
  44. Message Queuing could not access Active Directory Domain Services and failed to compute routing path for messages sent to ...
  45. Message Queuing could not authenticate a message sent to queue %1. The message was rejected because the queue only accepts ...
  46. Message Queuing could not complete SSL negotiation with the remote computer. It is possible that the server certificate is ...
  47. Message Queuing could not establish connection to %1, because connection was refused by the recipient computer. It is possible ...
  48. Message Queuing could not establish connection to %1, because the connection limit for this computer was reached. There too ...
  49. Message Queuing could not establish SSL connection with the recipient computer because a trust chain from the server certificate ...
  50. Message Queuing could not establish SSL connection with the recipient computer because the computer name specified in the ...
  51. Message Queuing could not resolve the name '%1' to an IP address. Try to ping the recipient computer, and check this computer's ...
  52. Message Queuing could not validate server certificate in HTTPS scenario because the certificate was found in disallowed store. ...
  53. Message Queuing detected a problem with the local domain controller. Until the problem is resolved, Message Queuing will ...
  54. Message Queuing Down-level Client Support cannot operate in mixed mode. Mixed mode is a transient mode in which Message Queuing ...
  55. Message Queuing Down-level Client Support cannot start. This service can operate only on a domain controller. The service ...
  56. Message Queuing Down-level Client Support failed to create the MSMQ Configuration (msmq) object with a given GUID for computer ...
  57. Message Queuing enables distributed applications running at different times to communicate across heterogeneous networks ...
  58. Message Queuing failed to bind to port 1801. The port may already be bound to another process. Make sure that the port is ...
  59. Message Queuing failed to listen on the IPv4 protocol. Messages will not be accepted on IPv4. If you want Message Queuing ...
  60. Message Queuing failed to listen on the IPv6 protocol. Messages will not be accepted on IPv6. If you want Message Queuing ...
  61. Message Queuing failed to send a message due to low memory. Message Queuing will retry to send the message. This event is ...
  62. Message Queuing failed to verify digital signature of a message sent to queue %1. The message was rejected. A negative arrival ...
  63. Message Queuing found multiple IP addresses for the local computer. Message Queuing will use the default IP address determined ...
  64. Message Queuing information cannot be read from Active Directory Domain Services (Error: 1). This may be caused by replication ...
  65. Message Queuing is not able to resolve the address specified by the user. The address may be wrong or DNS look-up for address ...
  66. Message Queuing objects cannot be created in Active Directory Domain Services (Error: 1). Please verify your permissions ...
  67. Message Queuing objects cannot move automatically between domains (%1). You must either run the MoveTree utility or first ...
  68. Message Queuing provides guaranteed message delivery, efficient routing, security, and priority-based messaging between applications. ...
  69. Message Queuing provides guaranteed message delivery, efficient routing, security, and priority-based messaging between applications. ...
  70. Message Queuing registry values cannot be read. The registry may be corrupted (Error: 1). Please reinstall Message Queuing ...
  71. Message Queuing Server provides guaranteed message delivery, efficient routing, security, and priority-based messaging. It ...
  72. Message Queuing Server provides guaranteed message delivery, efficient routing, security, and priority-based messaging. It ...
  73. Message Queuing Service failed to listen on both IPv4 and IPv6 protocol. Messages will not be accepted from the network through ...
  74. Message Queuing Services provides guaranteed message delivery, efficient routing, security, and priority-based messaging ...
  75. Message Queuing Services provides guaranteed message delivery, efficient routing, security, and priority-based messaging ...