Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 Online
It was a typical Monday morning for John, a IT specialist at a large corporation. He arrived at his desk, sipped his coffee, and began to tackle the day's tasks. One of his colleagues had reported an issue with the Windows Update service on one of the company's laptops, and John had volunteered to take a look.
- Press Windows Key + R, type
msconfig, and press Enter. - Go to the Services tab.
- Check Hide all Microsoft services.
- Click Disable all.
- Go to the Startup tab and click Open Task Manager. Disable all startup items.
- Restart and see if the error is gone. If it is, a third-party app (likely an antivirus or system cleaner) was the culprit.
Look for "WindowsUpdateTracelog" or "Circular Kernel Context Logger." It was a typical Monday morning for John,
Note: You may need to take ownership of this folder to delete files inside it. Press Windows Key + R , type msconfig , and press Enter
If the error is accompanied by failed updates, clearing the cache can resolve conflicts with corrupted log files. Open Command Prompt as an Administrator. Press Windows Key + R
The Scenario
Here is what typically happens in the background:
By using the logman tool to manually stop the duplicated ETW session, you can resolve the collision in under 30 seconds. Windows Update will immediately regain its ability to download and install updates.
4.4. Examine Detailed ETW Error Logs
In Event Viewer, navigate to:
Applications and Services Logs → Microsoft → Windows → EventTracing → Operational
Look for Event ID 100 (Session initialization failure) with error code 0xc0000035.