Windows 10

  1. A member was added to a basic application group. Subject: Security ID: %6 Account Name: %7 Account Domain: %8 Logon ID: %9 ...
  2. A member was added to a security-disabled global group. Subject: Security ID: %6 Account Name: %7 Account Domain: %8 Logon ...
  3. A member was added to a security-disabled local group. Subject: Security ID: %6 Account Name: %7 Account Domain: %8 Logon ...
  4. A member was added to a security-disabled universal group. Subject: Security ID: %6 Account Name: %7 Account Domain: %8 Logon ...
  5. A member was added to a security-enabled global group. Subject: Security ID: %6 Account Name: %7 Account Domain: %8 Logon ...
  6. A member was added to a security-enabled local group. Subject: Security ID: %6 Account Name: %7 Account Domain: %8 Logon ...
  7. A member was added to a security-enabled universal group. Subject: Security ID: %6 Account Name: %7 Account Domain: %8 Logon ...
  8. A member was removed from a basic application group. Subject: Security ID: %6 Account Name: %7 Account Domain: %8 Logon ID: ...
  9. A member was removed from a security-disabled global group. Subject: Security ID: %6 Account Name: %7 Account Domain: %8 ...
  10. A member was removed from a security-disabled local group. Subject: Security ID: %6 Account Name: %7 Account Domain: %8 Logon ...
  11. A member was removed from a security-disabled universal group. Subject: Security ID: %6 Account Name: %7 Account Domain: ...
  12. A member was removed from a security-enabled global group. Subject: Security ID: %6 Account Name: %7 Account Domain: %8 Logon ...
  13. A member was removed from a security-enabled local group. Subject: Security ID: %6 Account Name: %7 Account Domain: %8 Logon ...
  14. A member was removed from a security-enabled universal group. Subject: Security ID: %6 Account Name: %7 Account Domain: %8 ...
  15. A memory corruption was detected and handled. Memory diagnostics should be run on this machine and, if necessary, memory ...
  16. A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer ...
  17. A message was received on interface %1 from an unknown neighbor, while the previously-detected neighbor is still active. ...
  18. A message was received whose formatting was in error. Either the version was invalid, or one of the reserved fields contained ...
  19. A method call to an object in a COM+ application was rejected because the caller is not properly authorized to make this ...
  20. A method call to an object in a COM+ application was rejected because the caller is not properly authorized to make this ...
  21. A mirrored volume duplicates your data on two dynamic disks. Create a mirrored volume if you want to keep two separate copies ...
  22. A mode parameter is bad, such as capArea or subCapArea for TPM_GetCapability, phsicalPresence parameter for TPM_PhysicalPresence, ...
  23. A module was restarted due to excessive processing time of a file. Check the application event log for more information. ...
  24. A monitor returned a DDC/CI capabilities string which did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision ...
  25. A monitored security event pattern has occurred. Subject: Security ID: %3 Account Name: %4 Account Domain: %5 Logon ID: %6 ...
  26. A more restrictive Windows Filtering Platform filter has blocked a packet. Application Information: Process ID: %1 Application ...
  27. A more restrictive Windows Filtering Platform filter has blocked a packet. Network Information: Direction: %1 Source Address: ...
  28. A more restrictive Windows Filtering Platform filter has blocked a packet. Network Information: Direction: %1 Source Address: ...
  29. A more restrictive Windows Filtering Platform filter has blocked the packet.: Application: %1 Direction: %2 Source Address: ...
  30. A mutually authenticated connection could not be established to the following server. This connection will be retried at ...
  31. A mutually authenticated connection could not be established to the following server. This connection will be retried at ...
  32. A name conflict was detected while replicating the following directory partition object. Directory partition object: %1 Object ...
  33. A name not found error was returned for the name %1. Check to ensure that the name is correct. The response was sent by the ...
  34. A namespace collision was detected. Target Type: %1 Target Name: %2 Forest Root: %3 Top Level Name: %4 DNS Name: %5 NetBIOS ...
  35. A network adapter requires drivers that are installed when you install integration services in the guest operating system. ...
  36. A network bandwidth of %1 kilobits per second has been detected. Minimum bandwidth to synchronize a roaming profile is set ...
  37. A network connection between your computer and the VPN server was started, but the VPN connection was not completed. This ...
  38. A network connection was disconnected. Server name: %4 Server address: %6 Connection type: %7 Guidance: This indicates that ...
  39. A network control block (NCB) session open was rejected. No LISTEN is outstanding on the remote computer. The NCB is the ...
  40. A network error occurred in connecting to Windows Management Instrumentation. Ensure that your network connection is functioning ...
  41. A network error occurred while sending data to another node in the cluster. The number of bytes transmitted was less than ...
  42. A network latency of %1 milliseconds has been detected. Maximum latency to synchronize a roaming profile is set at %2 milliseconds. ...
  43. A network location identifies the type of network that a computer is connected to and automatically sets the appropriate ...
  44. A network monitoring program has set the wireless connectivity on this network adaptor to monitor mode. While monitoring ...
  45. A network monitoring program has set the wireless network adapter on this computer to monitor mode While monitoring wireless ...
  46. A network share object was accessed. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Network Information: ...
  47. A network share object was accessed. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Network Information: ...
  48. A network share object was added. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Share Information: ...
  49. A network share object was checked to see whether client can be granted desired access. Subject: Security ID: %1 Account ...
  50. A network share object was deleted. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Share Information: ...
  51. A network share object was modified. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Share Information: ...
  52. A new BITS job could not be created. The current job count for the user %1 (%2) is equal to or greater than the job limit ...
  53. A new BITS job could not be created. The current job count for this computer (%2) is equal to or greater than the per-computer ...
  54. A new connection has been created to address local bridgehead connectivity issues. Although one or more connections exist ...
  55. A new connection has been created to address site connectivity issues. One or more sites are unreachable in the topology. ...
  56. A new CRM log file was created. This CRM log file is not secure because the application Identity is Interactive User or the ...
  57. A new edition of Windows is available. Restart your PC to complete the upgrade. Your PC will restart automatically in 2 hours. ...
  58. A new external device was recognized by the system. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: ...
  59. A new LDAP connection was closed by the directory service because the maximum number of connections has been reached. Maximum ...
  60. A new media server could not be initialized because required DRM components cannot run while a debugger is attached. Detach ...
  61. A new media server was not initialized because CoCreateInstance(CLSID_UPnPRegistrar) encountered error '%1'. Verify that ...
  62. A new media server was not initialized because device document generation encountered error '%1'. Restart your computer, ...
  63. A new media server was not initialized because GetFriendlyName() encountered error '%1'. In Windows Media Player, turn off ...
  64. A new media server was not initialized because GetSerialNumber() encountered error '%1'. In Windows Media Player, turn off ...
  65. A new media server was not initialized because QueryInterface(IUPnPReregistrar) encountered error '%1'. Verify that the UPnPHost ...
  66. A new media server was not initialized because RegisterRunningDevice() encountered error '%1'. Restart your computer, and ...
  67. A new media server was not initialized because the model name could not be retrieved due to error '%1'. Delete the value ...
  68. A new media server was not initialized because the registry key 'HKLM\SOFTWARE\Microsoft\Windows Media Player NSS\3.0\Media ...
  69. A new media server was not initialized because the Windows Media Delivery Engine did not initialize due to error '%1'. Restart ...
  70. A new media server was not initialized because WMCreateDeviceRegistration() encountered error '%1'. The Windows Media DRM ...
  71. A new media server was not initialized due to error '%1'. Restart your computer, and then restart the WMPNetworkSvc service. ...
  72. A new media server was not initialized due to out-of-memory error '%1'. Close other programs or restart your computer and ...
  73. A new process has been created. Creator Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Target ...
  74. A new process has been created. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Process Information: ...
  75. A new process has been created. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Process Information: ...