Repack installations can sometimes alter system dependencies or corrupt core system images. Running internal recovery tools restores missing Microsoft signatures. Startup Error in Event Viewer - Microsoft Q&A
When a repack attempts to run a scheduled task associated with WindowsUpdateTraceLog , but the underlying logging folders, system services, or registry keys have been deleted or corrupted, the system encounters a hard collision or conflict. Is This Error Dangerous?
Stop the event trace session by typing the following command and pressing Enter: logman stop WindowsUpdateTracelog -et Use code with caution. Is This Error Dangerous
Then rebuild the ETW manifest:
While the core issue is always a name collision, several underlying factors can trigger this specific event: Once completed, run the system file integrity checker:
Session "WindowsUpdate_trace_log" failed to start with the following error: 0xC0000035
Troubleshooting Session "WindowsUpdateTraceLog" Failed to Start (0xc0000035) but the underlying logging folders
Run the deployment imaging tool first to repair component store corruption: DISM.exe /Online /Cleanup-image /Restorehealth Use code with caution. Once completed, run the system file integrity checker: sfc /scannow Use code with caution.
Have you recently run any ? Share public link