Sometimes the error is not the session object, but the physical log file ( WindowsUpdateTraceLog.etl ) being locked.
In the context of the , the OS is attempting to start a diagnostic trace log to monitor Windows Update activities. Because a previous trace session failed to close properly, or a duplicate logging instance is already running, the system hits a naming collision and halts. Common Causes of the Error
One Tuesday, Alex saw a strange yellow warning:
$sessionName = "WindowsUpdateTraceLog" $sessions = logman query -ets | Select-String $sessionName -Context 0,2
Another Unit 035 was already sitting at the desk, coffee in hand, scribbling furiously.