Microsoft-Windows-WMS

304 events across 4 channels

Event ID	Title	Channel
0		Operational
0		Trace
1		Operational
1		Trace
2		Operational
2		Trace
3		Operational
3		Trace
4		Operational
4		Trace
5		Operational
5		Trace
100		Operational
100	Error: Task %1 failed.	ConfigurationTasks
102		Operational
102	Web.	Application
103		Operational
103	Unknown Error happened to Setup component.	Application
104		Operational
104	ArgumentOutOfRange error happened to Setup component.	Application
105		Operational
105	RDS role is not enabled in this machine to activatelicense server.	Application
106		Operational
106	Remote Desktop Licence Server may be activated already.	Application
107		Operational
107	User name or password is invalid.	Application
108		Operational
108	User name does not exist in the machine.	Application
109		Operational
109	Group name does not exist in the machine.	Application
110		Operational
110	User name does exist in the machine already.	Application
111		Operational
111	User name does not exist in the group.	Application
112		Operational
112	User name does exist in the group already.	Application
113		Operational
113	%1 not allowed for loopbacks, WMI will cause error 70 (bad format): %2.	Application
114		Operational
114	Loopback object name %1 does not match adapter %2 used in single adapter mode: …	Application
115		Operational
115	WMI Error - %1: %2.	Application
116		Operational
116	IP %1 is already in use by network adapter %2: %3.	Application
117		Operational
117	Device Installer Setup API returned error %1: %2.	Application
118		Operational
118	%1 is not a loopback adapter: %2.	Application
119		Operational
119	ERROR_IN_WOW64: Installing a loopback by a 32bit app running in a 64bit …	Application
120		Operational
120	ERROR_IN_WOW64: Deleting a loopback by a 32bit app running in a 64bit …	Application
121		Operational
121	The machine OS is wrong.	Application
122		Operational
122	The machine needs installation of %1.	Application
123		Operational
123	The machine RDS needs installation of %1.	Application
124		Operational
124	LoopbackCollection must be in %1 mode to call this method: %2.	Application
125		Operational
125	Can not find device instance id %1: %2.	Application
126		Operational
126	Can not find driver info for id %1, guid %2: %3.	Application
127		Operational
127	Can not create loopback adapter creation thread.	Application
128		Operational
128	Loopback adapter creation failed with exception.	Application
129		Operational
129	Loopback adapter %1 of %2 failed with exception (%3), aborting creation thread: …	Application
130		Operational
130	Loopback adapter %1 of %2 failed with exception (%3), aborting deletion thread: …	Application
131		Operational
131	Loopback adapter recreation failed with exception.	Application
132		Operational
132	Run command failed with exception.	Application
133		Operational
133	%1 Failed to remove scheduled tasks: %2.	Application
134		Operational
134	%1 Failed to unregister DLLs with exception: %2.	Application
135		Operational
135	%1 Failed to delete file %2 with exception: %3.	Application
136		Operational
136	%1 Failed to delete directory %2 with exception: %3.	Application
137		Operational
137	Failed to copy registry subkey %1 from %2 to %3 with exception: %4.	Application
138		Operational
138	%1 Failed to migrate the auto map plugin from %2 to %3 with exception: %4.	Application
139		Operational
139	%1 Failed to delete registry subkey %2 or its child subkeys with exception: %3.	Application
140		Operational
140	%1 Failed to remove MSI with exception: %2.	Application
141		Operational
141	%1 Wait %2 milliseconds for the loopback adapters change to be reflected in WMI.	Application
142		Operational
142	%1 Waited for %2 seconds but failed to see %3 loopback adapters in the Terminal …	Application
143		Operational
143	%1: Failed to set MTU for connection %2.	Application
144		Operational
144	%1: Failed to rename connection %2.	Application
145		Operational
145	%1: Failed to initialize ITfLangBarMgr interface.	Application
146		Operational
146	%1: Failed to create instance inheriting ITfLangBarMgr interface.	Application
147		Operational
147	%1: GetShowFloatingStatus() failed with error %2.	Application
148		Operational
148	%1: ShowFloating() failed with error %2.	Application
149		Operational
149	Updating service start type.	ConfigurationTasks
150		Operational
150	Adding firewall rules	ConfigurationTasks
151		Operational
151	Configuring user settings (WAU, WER, CEIP and computer name).	ConfigurationTasks
152		Operational
152	Creating the WmsReserved account and enabling PowerShell remoting.	ConfigurationTasks
153		Operational
153	Creating the WMS RDS listener.	ConfigurationTasks
154		Operational
154	Creating the MultiPoint accounts.	ConfigurationTasks
155		Operational
155	Creating the %1 account and enabling Autologon.	ConfigurationTasks
156		Operational
156	Enabling the WMS RDS listener.	ConfigurationTasks
157		Operational
157	Enabling tracing.	ConfigurationTasks
158		Operational
158	Installing drivers.	ConfigurationTasks
159		Operational
159	Reset the password for both the WmsControl and WmsReserved accounts.	ConfigurationTasks
160		Operational
160	Setting shell policies.	ConfigurationTasks
162		Operational
162	Beginning Disk Protection update	ConfigurationTasks
163		Operational
163	Completing Disk Protection update	ConfigurationTasks
164		Operational
164	Updating the system policies.	ConfigurationTasks
165		Operational
165	Setting user policies.	ConfigurationTasks
166		Operational
166	Updating the previous RAM amount.	ConfigurationTasks
167		Operational
167	Updating the hibernate file.	ConfigurationTasks
168		Operational
168	Removing old dmp files.	ConfigurationTasks
169		Operational
169	Setting %1 shell registry value to %2.	ConfigurationTasks
170		Operational
170	Configured USB Redirection policy.	ConfigurationTasks
171		Operational
171	Created tool shortcuts.	ConfigurationTasks
172		Operational
172	Updated MS OOBE registry settings.	ConfigurationTasks
173		Operational
173	Removed Force AutoLogon.	ConfigurationTasks
174		Operational
174	Switched to multiple station mode.	ConfigurationTasks
175		Operational
175	Removed corrupt SSL certificates.	ConfigurationTasks
201		Operational
201	%1 failed with hr = %2.	Application
202		Operational
202	%1 successfully finished.	Application
300		Operational
300		Trace
401		Operational
401	%1 An error occurred while reading the registry key required for Auto Logon of …	Application
402		Operational
402	%1 Exception is %2 .	Application
403		Operational
403	%1 An error occurred while enumerating stations.	Application
404		Operational
404	%1 An error occurred while saving the user.	Application
405		Operational
405	%1 An error occurred while terminating the session (Session Id - %3).	Application
406		Operational
406	%1 An error occurred while disconnecting the session (Session Id - %3).	Application
407		Operational
407	%1 An error occurred while installing the Retail Purchase License Key Pack.	Application
408		Operational
408	%1 An error occurred while installing the Agreement License Key Pack.	Application
409		Operational
409	%1 An error occurred while installing the Volume License Key Pack.	Application
410		Operational
410	%1 An error occurred while determining System Mode Text.	Application
411		Operational
411	%1 An error occurred while rebooting the System.	Application
412		Operational
412	%1 An error occurred while loading OEM Branding Image.	Application
413		Operational
413	%1 An error occurred while shutting down the System.	Application
414		Operational
414	%1 An error occurred while determining User Type Text.	Application
415		Operational
415	%1 An error occurred while creating the user.	Application
416		Operational
416	%1 An unexpected error occurred.	Application
501		Operational
501	%1 An error occurred while creating DHCP Adapters.	Application
502		Operational
502	%1 An error occurred while configuring Multiple Station settings.	Application
503		Operational
503	%1 An error occurred while writing to Registry.	Application
504		Operational
504	%1 An error occurred while creating RDP Listener.	Application
505		Operational
505	%1 An error occurred while logging Off.	Application
506		Operational
506	%1 An error occurred while aborting DHCP Adapter creation.	Application
507		Operational
507	%1 An error occurred while shutting down.	Application
508		Operational
508	%1 An error occurred while loading OEM Branding Image.	Application
509		Operational
509	%1 An error occurred while reading from Registry.	Application
510		Operational
510	%1 An error occurred while cleaning up Registry.	Application
511		Operational
511	%1 An error occurred while creating a user.	Application
512		Operational
512	%1 Some of the pre requisites required for installing Windows Multipoint Server …	Application
513		Operational
513	%1 An error occurred while printing EULA.	Application
514		Operational
514	%1 An error occurred while loading EULA.	Application
515		Operational
515	%1 An unexpected error occurred.	Application
516		Operational
516	%1 An error occurred when installing drivers.	Application
517		Operational
517	%1 An error occurred when uninstalling drivers.	Application
518		Operational
518	%1 An error occurred when configuring services.	Application
519		Operational
519	%1 An error occurred when adding Everyone to Remote Desktop Users group.	Application
520		Operational
520	%1 An error occurred when enabling ETW tracing.	Application
521		Operational
521	%1 An error occurred when trying to delete then recreate loopback adapters.	Application
522		Operational
522	%1 An error occurred in the threads that delete then recreate loopback adapters.	Application
523		Operational
523	%1 will be changing the computer name from %2 to %3.	Application
524		Operational
524	%1 An error occurred when trying to change the computer name.	Application
525		Operational
525	%1 An error occurred when trying to get the computer join status.	Application
526		Operational
526	%1 An error occurred when updating firewall rules to allow %2 as an exception.	Application
527		Operational
527	%1 An error occurred when installing WmsSvc.	Application
528		Operational
528	%1 An error occurred when enabling or disabling Windows Error Reporting.	Application
529		Operational
529	%1 An error occurred when enabling or disabling Windows Automatic Update.	Application
530		Operational
530	%1 An error occurred when enabling or disabling SQM.	Application
531		Operational
531	%1 An error occurred when registering WMS DLLs.	Application
532		Operational
532	%1 An error occurred when upgrading from v1 to v2.	Application
533		Operational
533	%1 An error occurred when enabling local machine remoting.	Application
534		Operational
534	%1 An error occurred when update default registry hive for start menu options.	Application
535		Operational
535	%1 An error occurred when disabling APIPA for the loopback adapter.	Application
536		Operational
536	%1 An error occurred when enabling Multiple Station Mode.	Application
538		Operational
538	%1 An error occurred when setting MTU for loopback adapter connections.	Application
539		Operational
539	%1 An error occurred when renaming loopback adapter connections.	Application
1106		Operational
1106	Failed to retrieve user SID.	Application
1400		Operational
1400	Starting user-provided software update program %1.	Application
1401		Operational
1401	User-provided software update program %1 finished.	Application
1402		Operational
1402	Failed to execute custom script %1, error code = %2.	Application
1403		Operational
1403	User-provided software udpate program %1 timed out after %2 minutes and was …	Application
1404		Operational
1404	User-provided software update program %1 was not executed because the file …	Application
1405		Operational
1405	Starting Windows Update.	Application
1406		Operational
1406	Windows Update finished.	Application
1407		Operational
1407	Windows Update did not complete successfully.	Application
1408		Operational
1408	Disk Protection installed.	Application
1409		Operational
1409	Disk Protection uninstalled.	Application
1410		Operational
1410	Disk Protection enabled.	Application
1411		Operational
1411	Disk Protection disabled.	Application
1412		Operational
1412	Disk Protection detected a problem with the cache file.	Application
1413		Operational
1413	User %1 was logged off automatically because the system was installing scheduled …	Application

Event ID 0 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 0 —

Provider: Microsoft-Windows-WMS
Channel: Trace

Message

%1

Fields

Name	Description
`UnicodeString1`	—

Event ID 1 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 1 —

Provider: Microsoft-Windows-WMS
Channel: Trace

Message

%1

Fields

Name	Description
`UnicodeString1`	—

Event ID 2 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 2 —

Provider: Microsoft-Windows-WMS
Channel: Trace

Message

%1

Fields

Name	Description
`UnicodeString1`	—

Event ID 3 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 3 —

Provider: Microsoft-Windows-WMS
Channel: Trace

Message

%1

Fields

Name	Description
`UnicodeString1`	—

Event ID 4 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 4 —

Provider: Microsoft-Windows-WMS
Channel: Trace

Message

%1

Fields

Name	Description
`UnicodeString1`	—

Event ID 5 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 5 —

Provider: Microsoft-Windows-WMS
Channel: Trace

Message

%1

Fields

Name	Description
`UnicodeString1`	—

Event ID 100 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 100 — Error: Task %1 failed.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Error: Task %1 failed. For more information, review the MultiPoint Trace logs. [HR=%2]

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 102 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 102 — Web.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Web.config file is invalid. InnerException: %1.

Fields

Name	Description
`UnicodeString1`	—

Event ID 103 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 103 — Unknown Error happened to Setup component.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Unknown Error happened to Setup component: %1. %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 104 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 104 — ArgumentOutOfRange error happened to Setup component.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

ArgumentOutOfRange error happened to Setup component: %1. %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 105 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 105 — RDS role is not enabled in this machine to activatelicense server.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

RDS role is not enabled in this machine to activatelicense server: %1. %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 106 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 106 — Remote Desktop Licence Server may be activated already.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Remote Desktop Licence Server may be activated already: %1. %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 107 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 107 — User name or password is invalid.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

User name or password is invalid. %1. %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 108 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 108 — User name does not exist in the machine.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

User name does not exist in the machine. %1.

Fields

Name	Description
`UnicodeString1`	—

Event ID 109 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 109 — Group name does not exist in the machine.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Group name does not exist in the machine. %1.

Fields

Name	Description
`UnicodeString1`	—

Event ID 110 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 110 — User name does exist in the machine already.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

User name does exist in the machine already. %1.

Fields

Name	Description
`UnicodeString1`	—

Event ID 111 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 111 — User name does not exist in the group.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

User name does not exist in the group. %1.

Fields

Name	Description
`UnicodeString1`	—

Event ID 112 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 112 — User name does exist in the group already.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

User name does exist in the group already. %1.

Fields

Name	Description
`UnicodeString1`	—

Event ID 113 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 113 — %1 not allowed for loopbacks, WMI will cause error 70 (bad format): %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 not allowed for loopbacks, WMI will cause error 70 (bad format): %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 114 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 114 — Loopback object name %1 does not match adapter %2 used in single adapter mode: %3.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Loopback object name %1 does not match adapter %2 used in single adapter mode: %3

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 115 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 115 — WMI Error - %1: %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

WMI Error - %1: %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 116 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 116 — IP %1 is already in use by network adapter %2: %3.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

IP %1 is already in use by network adapter %2: %3

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 117 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 117 — Device Installer Setup API returned error %1: %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Device Installer Setup API returned error %1: %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 118 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 118 — %1 is not a loopback adapter: %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 is not a loopback adapter: %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 119 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 119 — ERROR_IN_WOW64: Installing a loopback by a 32bit app running in a 64bit environment is not allowed.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

ERROR_IN_WOW64: Installing a loopback by a 32bit app running in a 64bit environment is not allowed: %1

Fields

Name	Description
`UnicodeString1`	—

Event ID 120 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 120 — ERROR_IN_WOW64: Deleting a loopback by a 32bit app running in a 64bit environment is not allowed.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

ERROR_IN_WOW64: Deleting a loopback by a 32bit app running in a 64bit environment is not allowed: %1

Fields

Name	Description
`UnicodeString1`	—

Event ID 121 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 121 — The machine OS is wrong.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

The machine OS is wrong. Please install %1.

Fields

Name	Description
`UnicodeString1`	—

Event ID 122 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 122 — The machine needs installation of %1.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

The machine needs installation of %1.

Fields

Name	Description
`UnicodeString1`	—

Event ID 123 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 123 — The machine RDS needs installation of %1.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

The machine RDS needs installation of %1. All others in RDS must not be installed.

Fields

Name	Description
`UnicodeString1`	—

Event ID 124 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 124 — LoopbackCollection must be in %1 mode to call this method: %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

LoopbackCollection must be in %1 mode to call this method: %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 125 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 125 — Can not find device instance id %1: %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Can not find device instance id %1: %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 126 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 126 — Can not find driver info for id %1, guid %2: %3.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Can not find driver info for id %1, guid %2: %3

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 127 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 127 — Can not create loopback adapter creation thread.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Can not create loopback adapter creation thread: %1

Fields

Name	Description
`UnicodeString1`	—

Event ID 128 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 128 — Loopback adapter creation failed with exception.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Loopback adapter creation failed with exception (%1) : %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 129 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—
`UnicodeString4`	—

Event ID 129 — Loopback adapter %1 of %2 failed with exception (%3), aborting creation thread: %4.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Loopback adapter %1 of %2 failed with exception (%3), aborting creation thread: %4

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—
`UnicodeString4`	—

Event ID 130 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—
`UnicodeString4`	—

Event ID 130 — Loopback adapter %1 of %2 failed with exception (%3), aborting deletion thread: %4.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Loopback adapter %1 of %2 failed with exception (%3), aborting deletion thread: %4

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—
`UnicodeString4`	—

Event ID 131 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 131 — Loopback adapter recreation failed with exception.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Loopback adapter recreation failed with exception (%1) : %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 132 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 132 — Run command failed with exception.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Run command failed with exception (%1) : %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 133 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 133 — %1 Failed to remove scheduled tasks: %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 Failed to remove scheduled tasks: %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 134 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 134 — %1 Failed to unregister DLLs with exception: %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 Failed to unregister DLLs with exception: %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 135 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 135 — %1 Failed to delete file %2 with exception: %3.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 Failed to delete file %2 with exception: %3.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 136 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 136 — %1 Failed to delete directory %2 with exception: %3.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 Failed to delete directory %2 with exception: %3.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 137 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—
`UnicodeString4`	—

Event ID 137 — Failed to copy registry subkey %1 from %2 to %3 with exception: %4.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Failed to copy registry subkey %1 from %2 to %3 with exception: %4

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—
`UnicodeString4`	—

Event ID 138 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—
`UnicodeString4`	—

Event ID 138 — %1 Failed to migrate the auto map plugin from %2 to %3 with exception: %4.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 Failed to migrate the auto map plugin from %2 to %3 with exception: %4.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—
`UnicodeString4`	—

Event ID 139 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 139 — %1 Failed to delete registry subkey %2 or its child subkeys with exception: %3.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 Failed to delete registry subkey %2 or its child subkeys with exception: %3.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 140 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 140 — %1 Failed to remove MSI with exception: %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 Failed to remove MSI with exception: %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 141 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 141 — %1 Wait %2 milliseconds for the loopback adapters change to be reflected in WMI.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 Wait %2 milliseconds for the loopback adapters change to be reflected in WMI.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 142 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 142 — %1 Waited for %2 seconds but failed to see %3 loopback adapters in the Terminal Service Setting.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 Waited for %2 seconds but failed to see %3 loopback adapters in the Terminal Service Setting.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 143 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 143 — %1: Failed to set MTU for connection %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1: Failed to set MTU for connection %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 144 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 144 — %1: Failed to rename connection %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1: Failed to rename connection %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 145 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 145 — %1: Failed to initialize ITfLangBarMgr interface.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1: Failed to initialize ITfLangBarMgr interface

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 146 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 146 — %1: Failed to create instance inheriting ITfLangBarMgr interface.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1: Failed to create instance inheriting ITfLangBarMgr interface

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 147 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 147 — %1: GetShowFloatingStatus() failed with error %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1: GetShowFloatingStatus() failed with error %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 148 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 148 — %1: ShowFloating() failed with error %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1: ShowFloating() failed with error %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 149 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 149 — Updating service start type.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Updating service start type.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 150 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 150 — Adding firewall rules

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Adding firewall rules

Event ID 151 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 151 — Configuring user settings (WAU, WER, CEIP and computer name).

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Configuring user settings (WAU, WER, CEIP and computer name).

Event ID 152 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 152 — Creating the WmsReserved account and enabling PowerShell remoting.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Creating the WmsReserved account and enabling PowerShell remoting.

Event ID 153 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 153 — Creating the WMS RDS listener.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Creating the WMS RDS listener.

Event ID 154 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 154 — Creating the MultiPoint accounts.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Creating the MultiPoint accounts.

Event ID 155 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 155 — Creating the %1 account and enabling Autologon.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Creating the %1 account and enabling Autologon.

Fields

Name	Description
`UnicodeString1`	—

Event ID 156 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 156 — Enabling the WMS RDS listener.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Enabling the WMS RDS listener.

Event ID 157 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 157 — Enabling tracing.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Enabling tracing.

Event ID 158 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 158 — Installing drivers.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Installing drivers.

Event ID 159 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 159 — Reset the password for both the WmsControl and WmsReserved accounts.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Reset the password for both the WmsControl and WmsReserved accounts.

Event ID 160 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 160 — Setting shell policies.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Setting shell policies.

Event ID 162 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 162 — Beginning Disk Protection update

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Beginning Disk Protection update

Event ID 163 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 163 — Completing Disk Protection update

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Completing Disk Protection update

Event ID 164 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 164 — Updating the system policies.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Updating the system policies.

Event ID 165 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 165 — Setting user policies.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Setting user policies.

Event ID 166 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 166 — Updating the previous RAM amount.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Updating the previous RAM amount.

Event ID 167 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 167 — Updating the hibernate file.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Updating the hibernate file.

Event ID 168 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 168 — Removing old dmp files.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Removing old dmp files.

Event ID 169 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 169 — Setting %1 shell registry value to %2.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Setting %1 shell registry value to %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 170 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 170 — Configured USB Redirection policy.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Configured USB Redirection policy.

Event ID 171 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 171 — Created tool shortcuts.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Created tool shortcuts.

Event ID 172 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 172 — Updated MS OOBE registry settings.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Updated MS OOBE registry settings.

Event ID 173 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 173 — Removed Force AutoLogon.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Removed Force AutoLogon.

Event ID 174 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 174 — Switched to multiple station mode.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Switched to multiple station mode.

Event ID 175 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 175 — Removed corrupt SSL certificates.

Provider: Microsoft-Windows-WMS
Channel: ConfigurationTasks

Message

Removed corrupt SSL certificates.

Event ID 201 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 201 — %1 failed with hr = %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 failed with hr = %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 202 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 202 — %1 successfully finished.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 successfully finished

Fields

Name	Description
`UnicodeString1`	—

Event ID 300 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 300 —

Provider: Microsoft-Windows-WMS
Channel: Trace

Message

%1

Fields

Name	Description
`UnicodeString1`	—

Event ID 401 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 401 — %1 An error occurred while reading the registry key required for Auto Logon of SRC Shell User.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while reading the registry key required for Auto Logon of SRC Shell User. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 402 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 402 — %1 Exception is %2 .

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 Exception is %2 . The number of Licenses is zero. Please register Client Access Licenses.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 403 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 403 — %1 An error occurred while enumerating stations.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while enumerating stations. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 404 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 404 — %1 An error occurred while saving the user.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while saving the user. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 405 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 405 — %1 An error occurred while terminating the session (Session Id - %3).

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while terminating the session (Session Id - %3). The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 406 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 406 — %1 An error occurred while disconnecting the session (Session Id - %3).

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while disconnecting the session (Session Id - %3). The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 407 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 407 — %1 An error occurred while installing the Retail Purchase License Key Pack.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while installing the Retail Purchase License Key Pack. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 408 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 408 — %1 An error occurred while installing the Agreement License Key Pack.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while installing the Agreement License Key Pack. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 409 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 409 — %1 An error occurred while installing the Volume License Key Pack.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while installing the Volume License Key Pack. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 410 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 410 — %1 An error occurred while determining System Mode Text.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while determining System Mode Text. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 411 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 411 — %1 An error occurred while rebooting the System.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while rebooting the System. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 412 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 412 — %1 An error occurred while loading OEM Branding Image.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while loading OEM Branding Image. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 413 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 413 — %1 An error occurred while shutting down the System.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while shutting down the System. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 414 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 414 — %1 An error occurred while determining User Type Text.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while determining User Type Text. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 415 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 415 — %1 An error occurred while creating the user.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while creating the user. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 416 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 416 — %1 An unexpected error occurred.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An unexpected error occurred. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 501 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 501 — %1 An error occurred while creating DHCP Adapters.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while creating DHCP Adapters. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 502 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 502 — %1 An error occurred while configuring Multiple Station settings.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while configuring Multiple Station settings. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 503 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 503 — %1 An error occurred while writing to Registry.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while writing to Registry. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 504 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 504 — %1 An error occurred while creating RDP Listener.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while creating RDP Listener. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 505 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 505 — %1 An error occurred while logging Off.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while logging Off. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 506 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 506 — %1 An error occurred while aborting DHCP Adapter creation.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while aborting DHCP Adapter creation. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 507 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 507 — %1 An error occurred while shutting down.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while shutting down. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 508 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 508 — %1 An error occurred while loading OEM Branding Image.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while loading OEM Branding Image. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 509 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 509 — %1 An error occurred while reading from Registry.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while reading from Registry. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 510 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 510 — %1 An error occurred while cleaning up Registry.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while cleaning up Registry. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 511 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 511 — %1 An error occurred while creating a user.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while creating a user. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 512 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 512 — %1 Some of the pre requisites required for installing Windows Multipoint Server could not be found.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 Some of the pre requisites required for installing Windows Multipoint Server could not be found. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 513 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 513 — %1 An error occurred while printing EULA.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while printing EULA. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 514 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 514 — %1 An error occurred while loading EULA.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred while loading EULA. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 515 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 515 — %1 An unexpected error occurred.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An unexpected error occurred. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 516 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 516 — %1 An error occurred when installing drivers.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when installing drivers. The Win32 error code is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 517 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 517 — %1 An error occurred when uninstalling drivers.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when uninstalling drivers. The Win32 error code is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 518 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 518 — %1 An error occurred when configuring services.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when configuring services. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 519 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 519 — %1 An error occurred when adding Everyone to Remote Desktop Users group.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when adding Everyone to Remote Desktop Users group. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 520 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 520 — %1 An error occurred when enabling ETW tracing.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when enabling ETW tracing. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 521 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 521 — %1 An error occurred when trying to delete then recreate loopback adapters.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when trying to delete then recreate loopback adapters. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 522 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 522 — %1 An error occurred in the threads that delete then recreate loopback adapters.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred in the threads that delete then recreate loopback adapters.

Fields

Name	Description
`UnicodeString1`	—

Event ID 523 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—
`UnicodeString4`	—

Event ID 523 — %1 will be changing the computer name from %2 to %3.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 will be changing the computer name from %2 to %3. It is %4 that the requested computer name is already in use on the network.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—
`UnicodeString4`	—

Event ID 524 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 524 — %1 An error occurred when trying to change the computer name.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when trying to change the computer name. The Windows error code is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 525 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 525 — %1 An error occurred when trying to get the computer join status.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when trying to get the computer join status. The Windows error code is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 526 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 526 — %1 An error occurred when updating firewall rules to allow %2 as an exception.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when updating firewall rules to allow %2 as an exception. The exception is %3.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—
`UnicodeString3`	—

Event ID 527 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 527 — %1 An error occurred when installing WmsSvc.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when installing WmsSvc.exe. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 528 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 528 — %1 An error occurred when enabling or disabling Windows Error Reporting.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when enabling or disabling Windows Error Reporting. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 529 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 529 — %1 An error occurred when enabling or disabling Windows Automatic Update.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when enabling or disabling Windows Automatic Update. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 530 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 530 — %1 An error occurred when enabling or disabling SQM.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when enabling or disabling SQM. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 531 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 531 — %1 An error occurred when registering WMS DLLs.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when registering WMS DLLs. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 532 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 532 — %1 An error occurred when upgrading from v1 to v2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when upgrading from v1 to v2. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 533 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 533 — %1 An error occurred when enabling local machine remoting.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when enabling local machine remoting. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 534 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 534 — %1 An error occurred when update default registry hive for start menu options.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when update default registry hive for start menu options. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 535 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 535 — %1 An error occurred when disabling APIPA for the loopback adapter.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when disabling APIPA for the loopback adapter. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 536 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 536 — %1 An error occurred when enabling Multiple Station Mode.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when enabling Multiple Station Mode. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 538 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 538 — %1 An error occurred when setting MTU for loopback adapter connections.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when setting MTU for loopback adapter connections. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 539 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 539 — %1 An error occurred when renaming loopback adapter connections.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

%1 An error occurred when renaming loopback adapter connections. The exception is %2.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 1106 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 1106 — Failed to retrieve user SID.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Failed to retrieve user SID. Error '%1'

Fields

Name	Description
`UnicodeString1`	—

Event ID 1400 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 1400 — Starting user-provided software update program %1.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Starting user-provided software update program %1.

Fields

Name	Description
`UnicodeString1`	—

Event ID 1401 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 1401 — User-provided software update program %1 finished.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

User-provided software update program %1 finished. exit code = %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 1402 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 1402 — Failed to execute custom script %1, error code = %2.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Failed to execute custom script %1, error code = %2

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 1403 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 1403 — User-provided software udpate program %1 timed out after %2 minutes and was terminated.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

User-provided software udpate program %1 timed out after %2 minutes and was terminated.

Fields

Name	Description
`UnicodeString1`	—
`UnicodeString2`	—

Event ID 1404 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 1404 — User-provided software update program %1 was not executed because the file permisions allow modification by Users, Everyone, Interactive Users, or ...

Provider: Microsoft-Windows-WMS
Channel: Application

Message

User-provided software update program %1 was not executed because the file permisions allow modification by Users, Everyone, Interactive Users, or Authenticated Users.

Fields

Name	Description
`UnicodeString1`	—

Event ID 1405 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 1405 — Starting Windows Update.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Starting Windows Update.

Event ID 1406 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 1406 — Windows Update finished.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Windows Update finished.

Event ID 1407 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 1407 — Windows Update did not complete successfully.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Windows Update did not complete successfully.  View the Windows Update history in the Control Panel for details.

Event ID 1408 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 1408 — Disk Protection installed.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Disk Protection installed.

Event ID 1409 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 1409 — Disk Protection uninstalled.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Disk Protection uninstalled.

Event ID 1410 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 1410 — Disk Protection enabled.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Disk Protection enabled.

Event ID 1411 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 1411 — Disk Protection disabled.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Disk Protection disabled.

Event ID 1412 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Event ID 1412 — Disk Protection detected a problem with the cache file.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

Disk Protection detected a problem with the cache file.  The cache file was rebuilt and the system was restarted.

Event ID 1413 —

Provider: Microsoft-Windows-WMS
Channel: Operational

Fields

Name	Description
`UnicodeString1`	—

Event ID 1413 — User %1 was logged off automatically because the system was installing scheduled software updates.

Provider: Microsoft-Windows-WMS
Channel: Application

Message

User %1 was logged off automatically because the system was installing scheduled software updates.

Fields

Name	Description
`UnicodeString1`	—