Disable Diagnostics Hub log collection

Overview

About this script

This script improves your privacy on Windows.

These changes use Windows system commands to update your settings.

This script disables log collection by the Diagnostics Hub in Visual Studio.

The Diagnostics Hub is a feature that allows running multiple performance analysis tools simultaneously 1. This feature collects extensive data including CPU usage, user interface responsiveness, and energy consumption. 1. It presents data from multiple tools on a shared timeline, showing relationships between different performance metrics 1.

The Diagnostics Hub collects additional logs 2 3. Microsoft recommends stopping this collection after necessary logs are collected 2 3 4 5 6. It logs to a specified directory when enabled 2 4 5 6.

Disabling this log collection improves privacy by reducing the amount of data collected about your system and activities. It also enhances security by limiting data accessible to attackers and reducing the attack surface, given past vulnerabilities in this logging 7. Additionally, it can improve system performance, as Microsoft warns that this logging is resource-intensive 2.

This script deletes the LogLevel registry key at HKLM\Software\Microsoft\VisualStudio\DiagnosticsHub 2 3 4 5 6 8. Removing the LogLevel key effectively disables the Diagnostics Hub logging functionality 3 4 5 6 8. In Visual Studio 2022 and later versions, these registry keys are not set by default after installation.

Caution

Disabling this feature may impact the use of certain performance analysis tools in Visual Studio. Enable logging only when necessary if you need these tools for development.

This script uses Batch (batchfile) scripting language.

Safe for General Use

This script is recommended for all users. It helps to improve privacy without affecting stability.

Implementation Details

• Language: batch

• Required Privileges: Administrator rights

• Compatibility: Windows only

• Reversibility: Can be undone using provided revert script

Explore Categories

Disable Visual Studio data collection

This action belongs to Disable Visual Studio data collection category. These scripts disable future local and cloud data collection by Visual Studio about you and your behavior. These do not clean existing data collected about you locally or on cloud servers. Read more on category page ▶

Configure programs

This action belongs to Configure programs category. This category configures Windows using 111 scripts. These scripts are organized in 22 categories. The category includes 5 subscripts and 9 subcategories that include more scripts and categories. Read more on category page ▶

Apply now

Choose one of three ways to apply:

1. Automatically via privacy.sexy: The easiest and safest option.
2. Manually by downloading: Requires downloading a file.
3. Manually by copying: Advanced flexibility.

Alternative 1. Apply with Privacy.sexy

privacy.sexy is free and open-source application that lets securely apply this action easily.

Open privacy.sexy

You can fully restore this action (revert back to the original behavior) using the application.

privacy.sexy instructions

1. Open or download the desktop application
2. Search for the script name: Disable Diagnostics Hub log collection.
3. Check the script by clicking on the checkbox.
4. Click on Run button at the bottom of the page.

Alternative 2. Download

Irreversible Changes

This script is irreversible, meaning there is no straightforward method to restore changes once applied. Exercise caution before running, restoring it may not be possible.

1. Download the script file by clicking on the button below:

   Download script

2. Run the script file by clicking on it.

Download revert script

This file restores your system to its original state, before this script is applied.

Download restore script

Alternative 3. Copy

This is for advanced users. Consider automatically applying or downloading the script for simpler way.

1. Open Command Prompt as administrator.

HELP: Step-by-step guide

1. Click on Start menu

   Windows 11

   

   Windows 10

   

2. Type cmd

   Windows 11

   

   Windows 10

   

3. Right click on Command Prompt select Run as administrator

   Windows 11

   

   Windows 10

   

4. Click on Yes to run Command Prompt

   Windows 11

   

   Windows 10

   

---

Windows 11

Windows 10

2. Copy the following code:

Code to apply changes

:: Delete the registry value "LogLevel" from the key "HKLM\Software\Microsoft\VisualStudio\DiagnosticsHub" 
PowerShell -ExecutionPolicy Unrestricted -Command "$keyName = 'HKLM\Software\Microsoft\VisualStudio\DiagnosticsHub'; $valueName = 'LogLevel'; $hive = $keyName.Split('\')[0]; $path = "^""$($hive):$($keyName.Substring($hive.Length))"^""; Write-Host "^""Removing the registry value '$valueName' from '$path'."^""; if (-Not (Test-Path -LiteralPath $path)) { Write-Host 'Skipping, no action needed, registry key does not exist.'; Exit 0; }; $existingValueNames = (Get-ItemProperty -LiteralPath $path).PSObject.Properties.Name; if (-Not ($existingValueNames -Contains $valueName)) { Write-Host 'Skipping, no action needed, registry value does not exist.'; Exit 0; }; try { if ($valueName -ieq '(default)') { Write-Host 'Removing the default value.'; $(Get-Item -LiteralPath $path).OpenSubKey('', $true).DeleteValue(''); } else { Remove-ItemProperty -LiteralPath $path -Name $valueName -Force -ErrorAction Stop; }; Write-Host 'Successfully removed the registry value.'; } catch { Write-Error "^""Failed to remove the registry value: $($_.Exception.Message)"^""; }"

3. Right click on command prompt to paste it.
4. Press Enter to apply remaining code.

Copy restore code

Copy and run the following code to restore changes:

Revert code

:: Remove the registry value "LogLevel" from key "HKLM\Software\Microsoft\VisualStudio\DiagnosticsHub" to restore its original state 
PowerShell -ExecutionPolicy Unrestricted -Command "$keyName = 'HKLM\Software\Microsoft\VisualStudio\DiagnosticsHub'; $valueName = 'LogLevel'; $hive = $keyName.Split('\')[0]; $path = "^""$($hive):$($keyName.Substring($hive.Length))"^""; Write-Host "^""Removing the registry value '$valueName' from '$path'."^""; if (-Not (Test-Path -LiteralPath $path)) { Write-Host 'Skipping, no action needed, registry key does not exist.'; Exit 0; }; $existingValueNames = (Get-ItemProperty -LiteralPath $path).PSObject.Properties.Name; if (-Not ($existingValueNames -Contains $valueName)) { Write-Host 'Skipping, no action needed, registry value does not exist.'; Exit 0; }; try { if ($valueName -ieq '(default)') { Write-Host 'Removing the default value.'; $(Get-Item -LiteralPath $path).OpenSubKey('', $true).DeleteValue(''); } else { Remove-ItemProperty -LiteralPath $path -Name $valueName -Force -ErrorAction Stop; }; Write-Host 'Successfully removed the registry value.'; } catch { Write-Error "^""Failed to remove the registry value: $($_.Exception.Message)"^""; }"

Support

This website relies on your support.

Support now

Your donation helps keep the project alive and improves its content ❤️.

Share this page:

EmailLinkedInXRedditFacebookPinterestWhatsAppTelegramWeiboVK