en-US chrome computer user

Restrict CPU core sharing for renderer process

Verified with Google Chrome — updated on July 10, 2026 Supported on: Microsoft Windows 7 or later

Google Chrome

Path in the GPO console

Computer Configuration\Administrative Templates\Google\Google Chrome

Registry

HKLM Software\Policies\Google\Chrome
HKCU Software\Policies\Google\Chrome
Value name:
RestrictCoreSharingOnRenderer REG_DWORD
Enabled:
1
Disabled:
0

Other deployment channels

Intune (ADMX ingestion)
./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Miscellaneous/RestrictCoreSharingOnRenderer

OMA-URI published by Google. It requires the Chrome ADMX templates (chrome.admx, google.admx) to be imported in Intune first.

Supported platforms
  • Google Chrome (Windows) — since version 140

Source: official Chrome policy list, version 157.0.8103.79 Chrome Enterprise policy page

Description

This policy mitigates side-channel cross process memory attacks by isolating the renderer process on the CPU core and preventing other processes from sharing the same core. The mitigation is supported on Microsoft® Windows® 11 24H2 and above. If the OS does not have the required scheduling support, this policy will have no effect. This policy may slow down performance in some demanding scenarios similar to disabling hyperthreading. For more information refer https://learn.microsoft.com/en-us/windows/win32/api/winnt/ns-winnt-process_mitigation_side_channel_isolation_policy If this policy is enabled, all other processes will not be scheduled on the same CPU core when the renderer process is running. If this policy is disabled, all other processes can be scheduled on the same CPU core if a renderer process is running on it. If this policy is not set, all other processes can be scheduled on the same CPU core if a renderer process is running on the core. This may vary depending on Google Chrome release, currently running field trials, and platform.

Export Builder

BETA

Configure 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. ⓘ

Scope

.reg file

Windows Registry Editor Version 5.00

; Exported from gporais.com
; Policy: Restrict CPU core sharing for renderer process
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Windows 7 or later

[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome]
"RestrictCoreSharingOnRenderer"=dword:00000001
More formats (PowerShell, Intune, SCCM)

PowerShell

# Exported from gporais.com
# Policy: Restrict CPU core sharing for renderer process
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later

$path = 'HKLM:\Software\Policies\Google\Chrome'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'RestrictCoreSharingOnRenderer' -Value 1 -Type DWord

Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.

Open the Builder

Embed this policy on your site

What to embed
Theme

Adds one script line: the theme follows your site’s appearance and the height fits the content. If your site blocks scripts, the embed follows the visitor’s system theme.

Preview