Second attempt at fixing < escaping

We want to have a final string like "\<something". None of these render
properly:
* "\&lt;" renders as "\lt&;"
* "\\&lt;" renders "\lt&;"
* "\<!--no-escape-->&lt;" renders as "<!--no-escape><"

Try "\\<!--no-escape-->&lt;".

Author: chwarr

desktop-src/ETW/configuring-and-starting-an-autologger-session.md

@@ -75,8 +75,8 @@ The following table describes the values that you can define for each AutoLogger
 | <strong>ClockType</strong> | <strong>REG_DWORD</strong> | The timer to use when logging the time stamp for each event.<ul><li>1 = Performance counter value (high resolution)</li><li>2 = System timer</li><li>3 = CPU cycle counter</li></ul>For a description of each clock type, see the <strong>ClientContext</strong> member of <a href="wnode-header.md"><strong>WNODE_HEADER</strong></a>.<br /> The default value is 1 (performance counter value) on Windows Vista and later. Prior to Windows Vista, the default value is 2 (system timer).<br /> | 
 | <strong>DisableRealtimePersistence</strong> | <strong>REG_DWORD</strong> | To disable real time persistence, set this value to 1. The default is 0 (enabled) for real time sessions.<br /> If real time persistence is enabled, real-time events that were not delivered by the time the computer was shutdown will be persisted. The events will then be delivered to the consumer the next time the consumer connects to the session. <br /> | 
 | <strong>FileCounter</strong> | <strong>REG_DWORD</strong> | Do not set or modify this value. This value is the serial number used to increment the log file name if <strong>FileMax</strong> is specified. If the value is not valid, 1 will be assumed.<br /> | 
-| <strong>FileName</strong> | <strong>REG_SZ</strong> | The fully qualified path of the log file. The path to this file must exist. The log file is a sequential log file. The path is limited to 1024 characters.<br /> If <strong>FileName</strong> is not specified, events are written to %SystemRoot%\System32\LogFiles\WMI\\&lt;sessionname&gt;.etl. <br /> | 
-| <strong>FileMax</strong> | <strong>REG_DWORD</strong> | The maximum number of instances of the log file that ETW creates. If the log file specified in <strong>FileName</strong> exists, ETW appends the <strong>FileCounter</strong> value to the file name. For example, if the default log file name is used, the form is %SystemRoot%\System32\LogFiles\WMI\\&lt;sessionname&gt;.etl.NNNN. <br /> The first time the computer is started, the file name is &lt;sessionname&gt;.etl.0001, the second time the file name is &lt;sessionname&gt;.etl.0002, and so on. If <strong>FileMax</strong> is 3, on the fourth restart of the computer, ETW resets the counter to 1 and overwrites &lt;sessionname&gt;.etl.0001, if it exists.<br /> The maximum number of instances of the log file that are supported is 16.<br /> Do not use this feature with the <a href="logging-mode-constants.md">EVENT_TRACE_FILE_MODE_NEWFILE</a> log file mode.<br /> | 
+| <strong>FileName</strong> | <strong>REG_SZ</strong> | The fully qualified path of the log file. The path to this file must exist. The log file is a sequential log file. The path is limited to 1024 characters.<br /> If <strong>FileName</strong> is not specified, events are written to %SystemRoot%\System32\LogFiles\WMI\\<!--no-escape-->&lt;sessionname&gt;.etl. <br /> | 
+| <strong>FileMax</strong> | <strong>REG_DWORD</strong> | The maximum number of instances of the log file that ETW creates. If the log file specified in <strong>FileName</strong> exists, ETW appends the <strong>FileCounter</strong> value to the file name. For example, if the default log file name is used, the form is %SystemRoot%\System32\LogFiles\WMI\\<!--no-escape-->&lt;sessionname&gt;.etl.NNNN. <br /> The first time the computer is started, the file name is &lt;sessionname&gt;.etl.0001, the second time the file name is &lt;sessionname&gt;.etl.0002, and so on. If <strong>FileMax</strong> is 3, on the fourth restart of the computer, ETW resets the counter to 1 and overwrites &lt;sessionname&gt;.etl.0001, if it exists.<br /> The maximum number of instances of the log file that are supported is 16.<br /> Do not use this feature with the <a href="logging-mode-constants.md">EVENT_TRACE_FILE_MODE_NEWFILE</a> log file mode.<br /> | 
 | <strong>FlushTimer</strong> | <strong>REG_DWORD</strong> | How often, in seconds, the trace buffers are forcibly flushed. The minimum flush time is 1 second. This forced flush is in addition to the automatic flush that occurs when a buffer is full and when the trace session stops. <br /> For the case of a real-time logger, a value of zero (the default value) means that the flush time will be set to 1 second. A real-time logger is when <strong>LogFileMode</strong> is set to <strong>EVENT_TRACE_REAL_TIME_MODE</strong>.<br /> The default value is 0. By default, buffers are flushed only when they are full. <br /> | 
 | <strong>Guid</strong> | <strong>REG_SZ</strong> | A string that contains a GUID that uniquely identifies the session. This value is required. | 
 | <strong>LogFileMode</strong> | <strong>REG_DWORD</strong> | Specify one or more log modes. For possible values, see <a href="logging-mode-constants.md">Logging Mode Constants</a>. The default is <strong>EVENT_TRACE_FILE_MODE_SEQUENTIAL</strong>. Instead of writing to a log file, you can specify either <strong>EVENT_TRACE_BUFFERING_MODE</strong> or <strong>EVENT_TRACE_REAL_TIME_MODE</strong>.<br /> Specifying <strong>EVENT_TRACE_BUFFERING_MODE</strong> avoids the cost of flushing the contents of the session to disk when the file system becomes available. <br /> Note that using <strong>EVENT_TRACE_BUFFERING_MODE</strong> will cause the system to ignore the <strong>MaximumBuffers</strong> value, as the buffer size is instead the product of <strong>MinimumBuffers</strong> and <strong>BufferSize</strong>.<br /> AutoLogger sessions do not support the <strong>EVENT_TRACE_FILE_MODE_NEWFILE</strong> logging mode.<br /> If <strong>EVENT_TRACE_FILE_MODE_APPEND</strong> is specified, <strong>BufferSize</strong> must be explicitly provided and must be the same in both the logger and the file being appended.<br /> |