Resolve windows error Session Homegroup Log failed to start 0xC0000035

Manly Electronics homepage link logoManly Electronics

Why did this Windows error happen?

You probably attempted to disable Microsoft HomeGroup by changing 'Home network' to 'public network' in the 'Network and Sharing Center'. It is easy to assume that pressing 'Home network' under 'Connect or disconnect' will disconnect the HomeGroup. It will not. Changing 'Home network' to 'Public network' and does not disconnect or connect anything. It is just switching off/on Windows firewall rules for Microsoft HomeGroup.

Solution

Go to Control Panel - Network and Sharing Center.
Choose HomeGroup and sharing options and click 'Leave the HomeGroup'.

Other related errors - Microsoft-Windows-HomeGroup Control Panel/Operational Get Sharing Flags failed..

Resolving Common Windows Event Viewer Errors

Overview of Event Viewer

Event Viewer is a built-in Windows tool that logs system, application, and security events across Windows 7, 8, 10, and 11. Accessible by searching 'Event Viewer' in the Windows search bar, it organizes logs under categories such as Windows Logs (System, Application, Security) and Applications and Services Logs. Events are classified as:

  • Information: Routine operations, such as service startups.
  • Warning: Minor issues that typically do not require immediate action.
  • Error: Process or service failures, marked with a red cross in the interface.

A common error, “Session 'Homegroup Log' failed to start with error: 0xC0000035,” often appears in the System log. This error, tied to a STATUS_OBJECT_NAME_COLLISION, is typically benign but can concern end-users due to its visibility in Event Viewer.

Causes of Common Errors

Errors like 0xC0000035, particularly for sessions such as “Homegroup Log,” “PerfDiag Logger,” or “P2P Log,” stem from specific issues:

  1. Kernel Event Tracing (ETW) Conflicts: The 0xC0000035 error indicates a naming collision in ETW sessions, where a process attempts to initiate a logging session already in use byanother process.
  2. Homegroup Configuration: Homegroup, a file-sharing feature deprecated after Windows 10version 1803, often triggers errors due to outdated or misconfigured network settings.
  3. Network Issues: Outdated network drivers, corrupted DNS cache, or disabled IPv6 (required for Homegroup) can cause related errors.
  4. System File Corruption: Damaged system files or registry entries, often from improper shutdowns or failed updates, may lead to session failures.
  5. Third-Party Interference: Antivirus software or other applications may block ETW sessions, generating errors.

Impact Assessment

Many Event Viewer errors, including 0xC0000035, are informational and do not affect system performance.

Microsoft documentation and community forums confirm that errors like 'Homegroup Log' or 'PerfDiag Logger' failures can often be ignored unless accompanied by symptoms such as system crashes, network disruptions, or performance degradation. Errors involving critical components(e.g., disk or memory) require immediate attention.

Troubleshooting Steps for IT Support

IT professionals can use the following steps to resolve common Event Viewer errors for end-users,starting with low-risk solutions:

  1. Filter Logs for Analysis:
    • Open Event Viewer and navigate to Windows Logs > System.
    • Use Filter Current Log on the right panel, select “Error,” and enter keywords like “0xC0000035” or “Homegroup” to isolate relevant events.
    • Review event details for specific error codes and session names.
  2. Disable Homegroup:
    • For Windows 7/8 or misconfigured Windows 10/11 systems:
    • Go to Control Panel > Network and Sharing Center > Homegroup.
    • Select Leave the Homegroup if active.
    • Disable services: Run services.msc, locate HomeGroupListener and HomeGroupProvider, set Startup Type to Disabled.
    • Reboot and check Event Viewer.
  3. Reset Network Configurations:
    • Open Command Prompt as Administrator (search cmd, right-click, select Run as administrator).
    • Execute the following commands:
      ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock reset
    • Reboot and verify logs.
  4. Update Network Drivers:
    • Check for driver updates via Settings > Windows Update > View optional updates.
    • Alternatively, download the latest network drivers from the manufacturer’s website (e.g., Intel, Realtek).
    • Install updates and reboot.
  5. Repair System Files:
    • Open Command Prompt as Administrator.
    • Run:
      sfc /scannow
    • If issues are detected, run:
      DISM /Online /Cleanup-Image /RestoreHealth
    • Reboot and check logs.
  6. Perform Malware Scan:
    • Use Windows Defender or a trusted antivirus to run a full system scan.
    • Remove detected threats and reboot.
  7. Reset Network Settings (Windows 10/11):
    • Navigate to Settings > Network & Internet > Status > Network reset.
    • Click Reset now and reboot.

Escalation Criteria

Further investigation is warranted if:

  • Errors repeat frequently (e.g., every minute) and correlate with system instability.
  • Errors involve critical components, such as “Disk failure” or “Memory corruption.”
  • Basic troubleshooting fails to resolve the issue.

In such cases:

  • Run chkdsk C: /f /r to check disk integrity.
  • Consider a Windows reset via Settings > Update & Security > Recovery.
  • Refer to our help or follow enterprise escalation protocols.

Conclusion

Errors like “Session 'Homegroup Log' failed to start with error: 0xC0000035” in EventViewer are often benign, resulting from ETW conflicts, deprecated features, or minor network issues.

Additional Resources

For further assistance with Windows troubleshooting or to explore hardware and software solutions, contact ManlyElectronics

2011 - 2025