Troubleshooting: Allow users to access recommended troubleshooting for known problems
Verified with Windows 11 25H2 — updated on July 30, 2026
Supported on: At least Windows Server 2016, Windows 10 Version 1903
Path in the GPO console
Computer Configuration\Administrative Templates\System\Troubleshooting and Diagnostics\Microsoft Support Diagnostic Tool Description
This policy setting configures how troubleshooting for known problems can be applied on the device and lets administrators configure how it's applied to their domains/IT environments. Not configuring this policy setting will allow the user to configure how troubleshooting is applied. Enabling this policy allows you to configure how troubleshooting is applied on the user's device. You can select from one of the following values: 0 = Do not allow users, system features, or Microsoft to apply troubleshooting. 1 = Only automatically apply troubleshooting for critical problems by system features and Microsoft. 2 = Automatically apply troubleshooting for critical problems by system features and Microsoft. Notify users when troubleshooting for other problems is available and allow users to choose to apply or ignore. 3 = Automatically apply troubleshooting for critical and other problems by system features and Microsoft. Notify users when troubleshooting has solved a problem. 4 = Automatically apply troubleshooting for critical and other problems by system features and Microsoft. Do not notify users when troubleshooting has solved a problem. 5 = Allow the user to choose their own troubleshooting settings. After setting this policy, you can use the following instructions to check devices in your domain for available troubleshooting from Microsoft: 1. Create a bat script with the following contents: rem The following batch script triggers Recommended Troubleshooting schtasks /run /TN "\Microsoft\Windows\Diagnosis\RecommendedTroubleshootingScanner" 2. To create a new immediate task, navigate to the Group Policy Management Editor > Computer Configuration > Preferences and select Control Panel Settings. 3. Under Control Panel settings, right-click on Scheduled Tasks and select New. Select Immediate Task (At least Windows 7). 4. Provide name and description as appropriate, then under Security Options set the user account to System and select the Run with highest privileges checkbox. 5. In the Actions tab, create a new action, select Start a Program as its type, then enter the file created in step 1. 6. Configure the task to deploy to your domain.
Registry
Software\Policies\Microsoft\Windows\Troubleshooting\AllowRecommendations Value name: TroubleshootingAllowRecommendations
MDM / Intune (CSP)
./Device/Vendor/MSFT/Policy/Config/Troubleshooting/AllowRecommendations Microsoft Learn documentation Mapping data: Microsoft Learn (CC BY 4.0)
CSP values
-
0- Off - Don't allow users, system features, or Microsoft to apply troubleshooting. -
1 (Default)- Critical - Automatically apply troubleshooting for critical problems detected by system features and Microsoft. Don't notify users when troubleshooting has solved a problem. -
2- Prompt - Automatically apply troubleshooting for critical problems detected by system features and Microsoft. Prompt users when troubleshooting for other problems is available and allow the user to choose to apply or ignore. -
3- Notify - Automatically apply troubleshooting for critical and other problems detected by system features and Microsoft. Notify users when troubleshooting has solved a problem. -
4- Silent - Automatically apply troubleshooting for critical and other problems detected by system features and Microsoft. Don't notify users when troubleshooting has solved a problem. -
5- Configurable - Allow the user to choose their own troubleshooting settings.
Export Builder
BETAConfigure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.
These exports write the registry — this is not a managed GPO. ⓘ
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: Troubleshooting: Allow users to access recommended troubleshooting for known problems
; State: Enabled
; Supported on: At least Windows Server 2016, Windows 10 Version 1903
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Troubleshooting\AllowRecommendations]
"TroubleshootingAllowRecommendations"=dword:00000001
"TroubleshootingAllowRecommendations"=dword:00000000More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Troubleshooting: Allow users to access recommended troubleshooting for known problems
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10 Version 1903
$path = 'HKLM:\Software\Policies\Microsoft\Windows\Troubleshooting\AllowRecommendations'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'TroubleshootingAllowRecommendations' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'TroubleshootingAllowRecommendations' -Value 0 -Type DWordIntune XML
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Troubleshooting/AllowRecommendations
Data type: String
Value:
<enabled/>
<data id="TroubleshootingAllowRecommendations_Dropdown" value="0"/>Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: Troubleshooting: Allow users to access recommended troubleshooting for known problems
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10 Version 1903
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Windows\Troubleshooting\AllowRecommendations' -Name 'TroubleshootingAllowRecommendations' -Expected 1 -Kind DWord)
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Windows\Troubleshooting\AllowRecommendations' -Name 'TroubleshootingAllowRecommendations' -Expected 0 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Troubleshooting: Allow users to access recommended troubleshooting for known problems
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10 Version 1903
$path = 'HKLM:\Software\Policies\Microsoft\Windows\Troubleshooting\AllowRecommendations'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'TroubleshootingAllowRecommendations' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'TroubleshootingAllowRecommendations' -Value 0 -Type DWordSCCM scripts
# Exported from gporais.com
# Policy: Troubleshooting: Allow users to access recommended troubleshooting for known problems
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10 Version 1903
# SCCM Configuration Item guidance:
# Create a Configuration Item of type "Setting: Script".
# Discovery script: use the Detection script below.
# Remediation script: use the Remediation script below.
# Compliance rule: the Discovery script output equals 'Compliant'.
# === Detection script ===
# Exported from gporais.com
# Policy: Troubleshooting: Allow users to access recommended troubleshooting for known problems
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10 Version 1903
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Windows\Troubleshooting\AllowRecommendations' -Name 'TroubleshootingAllowRecommendations' -Expected 1 -Kind DWord)
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Windows\Troubleshooting\AllowRecommendations' -Name 'TroubleshootingAllowRecommendations' -Expected 0 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Troubleshooting: Allow users to access recommended troubleshooting for known problems
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10 Version 1903
$path = 'HKLM:\Software\Policies\Microsoft\Windows\Troubleshooting\AllowRecommendations'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'TroubleshootingAllowRecommendations' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'TroubleshootingAllowRecommendations' -Value 0 -Type DWordBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.