: Critical update or logging components are damaged.
Search for in the Start menu and open it. Expand Data Collector Sets on the left. Click on Startup Event Trace Sessions . Locate WindowsUpdateTracelog in the list. Right-click it and select Properties .
HKLM\SYSTEM\CurrentControlSet\Control\WMI\AutoLogger\WindowsUpdateTraceLog
For persistent cases, use a tool like or Sysinternals WinObj to inspect the \KernelObjects\ namespace for a stale WindowsUpdateTraceLog event handle. No public tool directly deletes these; a reboot is the cleanest solution. : Critical update or logging components are damaged
net start wuauserv net start cryptSvc net start bits net start msiserver net start EventLog
Determined to get to the bottom of the issue, John started digging deeper. He checked the Windows Update settings, ran a few troubleshooting tools, and even attempted to manually update the system. But no matter what he tried, the error persisted.
The error typically translates to a "Status Object Name Collision," which essentially means a system log or process tried to start while another with the same name was already running. In most cases, if your computer is otherwise performing well and receiving updates, this error is benign and can be safely ignored. Click on Startup Event Trace Sessions
The error code translates directly to STATUS_OBJECT_NAME_COLLISION . While this error looks alarming, it rarely causes system crashes or stops Windows Update from working. However, it can clutter your Event Viewer and indicate minor sync issues within the Windows Management Instrumentation (WMI) or Event Trace Log (ETL) subsystems. What Causes Error 0xc0000035?
Inside this folder, you may see a subkey with a GUID name like b675ec37-bdb6-4648-bc92-f3fdc74d3ca2 .
For Windows users and IT administrators, encountering cryptic error messages in the Event Viewer can be an unsettling experience. One such error——appears with growing frequency, particularly after recent Windows updates. While this error may initially seem alarming, understanding its root causes and available solutions can help you determine whether to take action or simply ignore it. it causes naming collisions.
Because this is an object name collision error, forcing Windows to recreate the logging session parameters in the registry usually fixes the issue permanently.
Stop the core update services by typing the following commands one by one, pressing after each: net stop wuauserv net stop bits net stop cryptsvc Use code with caution.
The localized cache where Windows Update indexes current transactional updates has become desynchronized.
| Field | Value | |-------|-------| | Severity | Status (non-critical) | | Facility Code | 0x0 (System) | | Error Code | 0x0035 (53 decimal) | | Underlying Issue | Object name collision in kernel object namespace |
The Windows Management Instrumentation repository contains data that controls these traces; if corrupted, it causes naming collisions.