In Visual Studio: Debug → Options → Enable Diagnostic Tools while debugging (uncheck). If the problem disappears, a specific tool (e.g., CPU Usage) is misconfigured. 7. Code Example (Illustrative) You would not typically catch this exception in production code. However, a diagnostic extension or custom profiler host might handle it like this:

1. Overview & Context The exception microsoft.diagnosticshub.diagnostics.collectionstartfailedhubexception is a specific, platform-level error originating from Microsoft’s Diagnostic Hub —a component primarily used within Visual Studio and other Microsoft developer tools (like Performance Profiler, CPU Usage tool, Memory Usage tool, and IntelliTrace).

Shut down other profilers, performance monitors, or secondary Visual Studio instances debugging the same process.

From the Visual Studio Installer → select More → Repair . This restores missing or corrupted Diagnostic Hub components.

Delete temporary diagnostic files: %TEMP%\Microsoft Diagnostics Hub\ %LOCALAPPDATA%\Microsoft\VisualStudio\<version>\DiagnosticsHub\

catch (DiagnosticsCollectionStartFailedHubException ex)

await diagnosticHubSession.StartCollectionAsync(targetProcessId);