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

Stop the core update services by executing these commands sequentially:

Save the file with a .reg extension, for example, fix-windows-update.reg .

The error "Session WindowsUpdateTraceLog failed to start with the following error 0xc0000035" indicates a Windows scheduled task or service (related to Windows Update tracing) could not start because an object with the same name already exists (STATUS_OBJECT_NAME_COLLISION). This typically points to a corrupted or duplicate trace session, leftover ETW (Event Tracing for Windows) registration, or conflicting tracing state.

logman query

To prevent this error from appearing in future repackaging workflows:

If the troubleshooting steps above do not resolve the issue, you may need to repack the Windows Update component. Repacking involves re-registering the Windows Update DLL files and resetting the Windows Update service.

You are checking the Event Viewer (Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational) or running a system scan, and you see this error: Stop the core update services by executing these

Run the following command to stop the service: logman delete "WindowsUpdateTraceLog" -ets

The error code is the digital equivalent of trying to open a door that’s already been thrown wide open. In Windows-speak, it means STATUS_OBJECT_NAME_COLLISION —basically, the system tried to start the WindowsUpdateTraceLog session, but it realized a session with that exact name was already running in the background [1, 3].

The core of the issue lies in the hexadecimal status code: 0xc0000035 . In the Windows NT status code hierarchy, this specific code translates to STATUS_OBJECT_NAME_COLLISION . In plain terms, this error indicates that the operating system attempted to create or access a named object (in this case, a kernel session or a file mapping) that already exists. logman query To prevent this error from appearing

: In most cases, if your computer is receiving and installing updates normally, this error in the Event Viewer can be safely ignored as it is a logging-related conflict rather than a system failure. Microsoft Learn Recommended Troubleshooting Steps

Is this a or a standard installation? Have you used any privacy/debloating tools recently? Share public link

Think of it like trying to park two cars in the same reserved spot – the second car gets the error, not the parking lot. not the parking lot.