Here’s a detailed guide to understanding and resolving the error: “Session WindowsUpdateTraceLog failed to start with the following error 0xc0000035 repack”.
Change their values from 1 to 0. This prevents the system from attempting to start that specific trace session, which stops the error from logging in the Event Viewer. 4. Run System Repair Tools Here’s a detailed guide to understanding and resolving
C:\Windows\SoftwareDistribution and C:\Windows\System32\catroot2.The error code 0xc0000035 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]. Stop BITS, WUAUSERV, Cryptographic Services
The most immediate fix is to prevent the service from starting during the capture. Before starting your repackaging tool: dism /online /cleanup-image /restorehealth sfc /scannow
Navigate to C:\Windows\SoftwareDistribution and delete everything inside. Go back to Services and Start the "Windows Update" service. 4. Advanced Registry Fix
logman query