COMMAND EVERYTHING.
Creates an Autologger session configuration in the registry.
Microsoft EventTracingManagement reference: Creates an Autologger session configuration in the registry. The syntax and selected example below are adapted from the pinned Windows Server 2025 reference. Module availability, target configuration and delegated permissions determine whether it can run in your environment. Documentation and parameter text: Microsoft, CC BY 4.0; formatting adapted by Cmdlet World. No execution testing is claimed.
Use an account with the target resource permissions documented for New-AutologgerConfig. Modifying administrative cmdlets may require elevation or delegated administration. This catalog does not assert that ordinary users can execute the command.
Windows / EventTracingManagement · Windows Server 2025 documentation; feature/module prerequisites apply
-AsJob- Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete. The cmdlet immediately returns an object that represents the job and then displays the command prompt. You can continue to work in the session while the job completes. To manage the job, use the *-Job cmdlets. To get the job results, use the Receive-Job cmdlet. For more information about Windows PowerShell background jobs, see about_Jobs.
-BufferSize- Specifies the ETW session buffer size, in kilobytes.
-CimSession- Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.
-ClockType- Specifies the type of timestamp that will be used for each event logged to this ETW session. This is an advanced session configuration option, and it is not recommended that this parameter be set. For more information, see the description of the ClientContext field in WNODE_HEADER structure for a description of clock types.
-Confirm- Prompts you for confirmation before running the cmdlet.
-DisableRealtimePersistence- Controls whether undelivered events from a real time session will be delivered or discarded when Windows next starts up. For more information, see Configuring and Starting an AutoLogger Session in MSDN.
-FileCount- Specifies the file count value.
-FileMax- Specifies the maximum number of log files an AutoLogger session can create.
-FlushTimer- When set, all active buffers in the session will be flushed at this interval, in seconds. This is an advanced session configuration option, and it is not recommended that this parameter be set. If it is not set, the ETW will select an appropriate default based on the *LogFileMode*.
-Guid- Specifies a unique GUID for this AutoLogger session.
-LocalFilePath- Specifies the full path to the file the ETW session should write to. For non-buffering mode sessions only. When creating a new-file file mode session, the file path must contain a %d in the file name. Do not use this parameter if the session is configured as a buffering mode session. Use Save-EtwTraceSession to save a buffering mode session to disk instead.
-LogFileMode- Specifies the ETW session logging mode. The value is a bitmask of the ETW logging mode constants. For more information, see Logging Mode Constants in MSDN.
-MaximumBuffers- Specifies the maximum number of buffers the ETW session should use. The ETW session will use a maximum of (*BufferSize* * *MaximumBuffers*) kilobytes of memory. Depending on the specified *LogFileMode*, this may be pageable or non-paged memory. If the session is losing events because the buffers cannot be flushed quick enough to keep up with the incoming event rate, try increasing this value. Configuring a session to use too many buffers may affect system performance.
-MaximumFileSize- Specifies the maximum file size for the output .etl file to grow to, in megabytes. The parameter must be set for a circular, new-file, or sequential file mode ETW session. For circular sessions, once the file reaches this size the oldest buffers will be overwritten by the new buffers. For new-file sessions, once the file reaches this size a new file will be created and all new events will be written to that file. For sequential file sessions, once the file reaches this size the session will stop.
-MinimumBuffers- Specifies the minimum number of buffers the ETW session should use. The ETW session will use a minimum of (*BufferSize* * *MinimumBuffers*) kilobytes of memory. Depending on the specified *LogFileMode*, this may be pageable or non-paged memory. If the session is losing events because the buffers cannot be flushed quick enough to keep up with the incoming event rate, try increasing this value. Configuring a session to use too many buffers may affect system performance.
-Name (required)- Specifies the name of the new AutoLogger session. This will be used as the name of the ETW session that gets created by this AutoLogger.
-Start- If set to Enabled, an ETW session for this AutoLogger will be created when Windows starts.
-ThrottleLimit- Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.
-WhatIf- Shows what would happen if the cmdlet runs. The cmdlet is not run.
Windows with the EventTracingManagement module and the Windows feature or management tools that provide it. Confirm target connectivity and version compatibility using the linked Microsoft reference.
This cmdlet changes system state. Review every target and parameter in the official reference, test outside production, and prepare an appropriate backup or rollback. Do not execute the example automatically.