The hex code 0xc0000035 translates natively to . This happens due to a few specific infrastructure bugs within Windows:
Delete all files and folders inside this directory. (This will not delete your personal data; it only clears temporary update files). Return to your command prompt and restart the services: net start wuauserv net start bits net start cryptsvc Use code with caution. Method 2: Modify the Autologger Registry Settings
If the error persists, you can manually disable or reconfigure the specific autologger session via the Windows Registry Editor. Press Windows Key + R , type regedit , and press Enter .
Open .
Press the , type cmd , right-click Command Prompt , and choose Run as administrator . Execute this command to fix local file damage: sfc /scannow Use code with caution. Once completed, run the deployment image cleanup tool: DISM /Online /Cleanup-Image /RestoreHealth Use code with caution. Restart your computer and check if the error loops stop. 2. Modify the Autologger Value via Registry Editor
Type the following commands one by one, pressing after each to stop the update services: net stop wuauserv net stop bits net stop cryptsvc
To resolve the issue, it helps to understand what each part of the error message means: The hex code 0xc0000035 translates natively to
In the Windows subsystem, the error code translates to STATUS_OBJECT_NAME_COLLISION .
This article covers a common Windows Event Viewer error, often seen in customized or "repacked" Windows installations, specifically: .
Are you experiencing any , or is this just an isolated error log? Return to your command prompt and restart the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\b675ec37-bdb6-4648-bc92-f3fdc74d3ca2 EnableProperty DWORD values to Restart your computer. 4. Hardware and Driver Checks
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old Restart the services: net start wuauserv net start bits net start cryptSvc Microsoft Learn 3. Adjust Registry (For Persistent Log Flooding)
The following fixes range from simple checks to more advanced repairs. Start with the easiest, safest options and proceed to more involved ones only if the issue persists. It is always recommended to before making any significant system changes. One Tuesday morning
One Tuesday morning, at exactly 10:00:00 AM, the System Kernel sent a lightning-fast telegram: "START THE TRACELOG SESSION IMMEDIATELY."
Many experts describe this error as "benign" because the system simply fails to log diagnostic information but continues to function normally.
