Open in the explorer

Turn off Windows Key hotkeys

Désactiver les touches de raccourci Windows

Type
User
GPO path
User Configuration › Policies › Administrative Templates › Windows Components › File Explorer FR: Configuration utilisateur › Stratégies › Modèles d'administration › Composants Windows › Explorateur de fichiers
Supported on
At least Windows Server 2003 FR: Au minimum Windows Server 2003
ADMX file
WindowsExplorer.admx
Internal name
WindowsExplorer/NoWindowsHotKeys

Explanation

Turn off Windows Key hotkeys.

Keyboards with a Windows key provide users with shortcuts to common shell features. For example, pressing the keyboard sequence Windows+R opens the Run dialog box; pressing Windows+E starts File Explorer. By using this setting, you can disable these Windows Key hotkeys.

If you enable this setting, the Windows Key hotkeys are unavailable.

If you disable or do not configure this setting, the Windows Key hotkeys are available.

French text from Windows 11 26H2

Désactive les touches de raccourci Windows+X.

Les claviers disposant d’une touche Windows fournissent aux utilisateurs des raccourcis vers les fonctionnalités d’environnement courantes. Par exemple, si vous appuyez sur la combinaison de touches Windows+R, la boîte de dialogue Exécuter s’ouvre ; si vous appuyez sur la combinaison de touches Windows+E, l’Explorateur de fichiers démarre. L’utilisation de ce paramètre permet de désactiver les touches de raccourci Windows.

Si vous activez ce paramètre, les touches de raccourci Windows ne seront pas disponibles.

Si vous désactivez ce paramètre ou si vous ne le configurez pas, les touches de raccourci Windows seront disponibles.

Registry

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer
Value name
NoWinKeys
StateValue written
Enablednot defined in the ADMX
Disablednot defined in the ADMX

PowerShell

PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.

The ADMX does not specify the value written when enabled; the GPO editor usually writes REG_DWORD 1 (enabled) / 0 (disabled). The commands below use 1/0 as an assumption.

Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.

Enable

# Enable: WindowsExplorer/NoWindowsHotKeys
$k = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# The ADMX does not specify the value written; the GPO editor usually writes REG_DWORD 1 (enabled) / 0 (disabled)
Set-ItemProperty -Path $k -Name 'NoWinKeys' -Value 1 -Type DWord  # assumed value (not defined in the ADMX)

Disable

# Disable: WindowsExplorer/NoWindowsHotKeys
$k = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# The ADMX does not specify the value written; the GPO editor usually writes REG_DWORD 1 (enabled) / 0 (disabled)
Set-ItemProperty -Path $k -Name 'NoWinKeys' -Value 0 -Type DWord  # assumed value (not defined in the ADMX)

Revert to "Not configured"

# Revert to "Not configured": WindowsExplorer/NoWindowsHotKeys
$k = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer'
Remove-ItemProperty -Path $k -Name 'NoWinKeys' -ErrorAction SilentlyContinue

Availability