Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 Repack !!hot!!

In the Windows subsystem, the hex code 0xc0000035 explicitly translates to STATUS_OBJECT_NAME_COLLISION . This means that an Event Tracing for Windows (ETW) session tried to initialize using a specific internal name or tracking block, but another service or thread was already using that exact resource.

Alex took a deep breath and followed three simple steps: In the Windows subsystem, the hex code 0xc0000035

When you are "repacking" (using tools like Microsoft App-V, VMware ThinApp, AdminStudio, or creating WIM images), the tool attempts to monitor system changes. If the Windows Update service attempts to start its diagnostic logging simultaneously—perhaps triggered by a background task or the startup of the Windows Update Agent—the repackaging tool detects a collision. The system cannot start a second instance of a trace session with the same name. If the Windows Update service attempts to start

wevtutil im C:\Windows\System32\winevt\Logs\Microsoft-Windows-WindowsUpdateClient%4Operational.man In the Windows subsystem