Format:
Style:

Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 _hot_ [ REAL • Bundle ]

Execute the Deployment Image Servicing and Management (DISM) tool first: DISM.exe /Online /Cleanup-image /Restorehealth Use code with caution.

The error 0xc0000035 appears in the under Microsoft-Windows-Kernel-EventTracing/Admin with Event ID 2 . The message indicates that the system's Windows Update event-tracing session failed to initialize properly. The error can involve several session names, including "WindowsUpdate_trace_log," "Microsoft.Windows.WindowsUpdate.RUXIMLog," "Circular Kernel Context Logger," and "Microsoft.Windows.Remediation".

Resetting SoftwareDistribution removes any orphaned lock files that may be holding onto the ETW session reference. After running this, immediately attempt the logman stop command again. Execute the Deployment Image Servicing and Management (DISM)

Execute the Deployment Image Servicing and Management tool first: DISM.exe /Online /Cleanup-image /Restorehealth Use code with caution. Once finished, run the System File Checker: sfc /scannow Use code with caution.

logman stop "UpdateSessionOrchestration" -ets logman stop "WindowsUpdate" -ets The error can involve several session names, including

Type the following commands one by one, hitting Enter after each: net stop wuauserv net stop bits Wait a few seconds, then restart them: net start wuauserv net start bits 4. Check for Circular Logging Conflicts If you are tech-savvy, you can manage the session directly:

Note: Back up your registry ( File > Export ) before making edits. Press Windows Key + R , type regedit , and press . Navigate to the following directory: Execute the Deployment Image Servicing and Management tool

Wiping the temporary update files can resolve persistent name collisions. Open and stop these services: net stop wuauserv net stop bits

If your system is running fine and updates are installing correctly, you can safely stop the error from being logged. This doesn't fix the underlying cause but prevents it from cluttering your Event Viewer.

Execute the Deployment Image Servicing and Management (DISM) tool first: DISM.exe /Online /Cleanup-image /Restorehealth Use code with caution.

The error 0xc0000035 appears in the under Microsoft-Windows-Kernel-EventTracing/Admin with Event ID 2 . The message indicates that the system's Windows Update event-tracing session failed to initialize properly. The error can involve several session names, including "WindowsUpdate_trace_log," "Microsoft.Windows.WindowsUpdate.RUXIMLog," "Circular Kernel Context Logger," and "Microsoft.Windows.Remediation".

Resetting SoftwareDistribution removes any orphaned lock files that may be holding onto the ETW session reference. After running this, immediately attempt the logman stop command again.

Execute the Deployment Image Servicing and Management tool first: DISM.exe /Online /Cleanup-image /Restorehealth Use code with caution. Once finished, run the System File Checker: sfc /scannow Use code with caution.

logman stop "UpdateSessionOrchestration" -ets logman stop "WindowsUpdate" -ets

Type the following commands one by one, hitting Enter after each: net stop wuauserv net stop bits Wait a few seconds, then restart them: net start wuauserv net start bits 4. Check for Circular Logging Conflicts If you are tech-savvy, you can manage the session directly:

Note: Back up your registry ( File > Export ) before making edits. Press Windows Key + R , type regedit , and press . Navigate to the following directory:

Wiping the temporary update files can resolve persistent name collisions. Open and stop these services: net stop wuauserv net stop bits

If your system is running fine and updates are installing correctly, you can safely stop the error from being logged. This doesn't fix the underlying cause but prevents it from cluttering your Event Viewer.