How can I disable Copilot in Windows 11 Pro (2025)?

Question

I've applied a group policy from my DC, I've gone on the workstation and enabled 'Turn off Windows Copilot', and the registry setting reflects that. However, I can simply type 'copilot' in the menu search field, and Copilot starts right up. I need this disabled for a STIG. What am I missing?

I turned it off in the taskbar settings as described here (https://www.tomsguide.com/computing/software/how-disable-copilot-in-windows-11 ) but that didn't make a difference either.

Answer 1

Hi,

That really clears things up for a lot of stuff. Now, if you are:

On Windows 11 Pro 24H2 or newer

The TurnOffWindowsCopilot Group Policy is applied (also present in the Registry)

You don't find Copilot.Exe or the SystemApps\MicrosoftWindows.Client.* folder expected. But still, typing "copilot" in the Start menu launches something Copilot-ish...

Then most likely:

Web-based Copilot Integration is launched (not local app)

In newer builds, particularly in 24H2/26100+ onward, the integration with Copilot is essentially being made a web experience within Edge (Bing Chat or Copilot for Microsoft 365). The "Copilot" entry in the Start menu is just a shortcut linking to a web instance through Edge sidebar or ms-edge:// URI.

Thus, there is no local Copilot.Exe, but the system catches "Copilot" and routes it to Edge, usually through:

Edge Sidebar (Copilot integration)

Webview2

Start menu deep link (ms-copilot:, ms-edge-copilot:)

Here's How to Actually Block This Type of Copilot

1. Disable Microsoft Edge Sidebar Copilot

Even with the local app gone, Edge has now included a Copilot in the sidebar.

Disable from the Group Policy:

GPO path:

Computer Configuration > Administrative Templates > Microsoft Edge > Sidebar

Configure the following settings:

Show or hide side panel: Enabled then set to Disabled

Allow Microsoft Edge Sidebar: Disabled

Allow Copilot in Microsoft Edge: Disabled

Configure Copilot in Microsoft Edge: Disabled

Registry equivalents (for reference):

reg

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge]

"EdgeSidebarEnabled"=dword:00000000

"ShowHubsSidebar"=dword:00000000

"AllowCopilot"=dword:00000000

"ConfigureCopilot"=dword:00000000

2. Block ms-copilot: or ms-edge-copilot: URI Handlers (Advanced)

These are system URI handlers that launch Copilot. You can remove or disable their registry entries.

Search for:

Computer\HKEY_CLASSES_ROOT\ms-copilot

Computer\HKEY_CLASSES_ROOT\ms-edge-copilot

Delete or restrict those keys via GPO/script to prevent routing those calls to Edge.

3. Block Copilot via Firewall or Host Redirection (for web versions)

In case STIG required complete shutdown:

Block network access to:

bash

copilot.microsoft.com

bing.com/search?q=Copilot

or to add it into C:\Windows\System32\drivers\etc\hosts:

hosts

127.0.0.1 copilot.microsoft.com

127.0.0.1 www.bing.com

Could you please try out these steps and let me know if it works out? And, in case that any other error arises, I would love to have more information it.

Best regards,

Tin

Answer 2

Thanks for the suggestions, but I can't complete the first step. I don't have a directory like C:\Windows\SystemApps\MicrosoftWindows.Client% so I searched for Copilot.exe using the powershell command below, and it didn't return anything. It appears I don't have a Copilot executable on my machine.

PS C:> Get-ChildItem -Path C:\Windows -Recurse -Filter "Copilot.ext" -ErrorAction SilentlyContinue

Answer 3

Hello! Thank you for reaching out. I am Tin, an independent advisor, and glad to assist you today with this issue. You are not alone, as Microsoft basically redesigned Copilot integration in Windows 11 (especially in the 24H2 / 2025 builds), and group policy/registry settings are less and less sufficient. Here is a list of what's happening and how to fully disable Copilot in Windows 11 Pro 2025:

Group Policy Sets:

Computer Configuration > Administrative Templates > Windows Components > Windows Copilot > Turn off Windows Copilot adds a Registry Key:

ini

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsCopilot]

"TurnOffWindowsCopilot"=dword:00000001

Only the taskbar button is disabled, though, not the Copilot app or its availability through Search. Users can still invoke it by:

Typing "Copilot" in Start Menu or Search

ms-copilot:

Solution: Disable Copilot Everywhere

For STIG/hardening, you need to block actual access to the Copilot app, not just hide the button. Here's how:

1: Block Copilot via AppLocker or Software Restriction Policies (SRP)

Target: Block Copilot.exe or the URI protocol ms-copilot:

Locate the app executable — for Windows 11 24H2, the Copilot is a Windows component, not a normal app. It usually resides here:

arduino

C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\

AppLocker Rule (Recommended for Domain Environments)

Create an Executable Ruleset to deny Copilot:

Path Rule:

C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\Copilot.exe

(Use wildcard if version may vary)

URI Rule (if AppLocker supports it): Block ms-copilot: protocol.

Software Restriction Policy (SRP) — If not using AppLocker:

Create a new rule to disallow Copilot.exe path

You may need to use wildcards or exact folder path.

2: Block via Explorer Policy

Disable URI activation via the Explorer shell:

Set this registry value:

reg

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer]

"DisableCopilot"=dword:00000001

Note: As of recent builds (May/June 2025), this policy is ignored unless on Enterprise/Education SKUs. For Pro, Microsoft may not respect this in the latest 24H2 build.

3: Remove Microsoft Copilot via PowerShell (Experimental)

You can try to delete the package entirely:

powershell

Get-AppxPackage *Windows.Copilot* | Remove-AppxPackage -AllUsers

But:

This may not work for the latest builds (24H2), where Copilot is deeply integrated.

Removal may be once again triggered by the cumulative updates.

A more civilized solution is to block it than to remove it.

Could you please attempt these steps and tell me how it goes? Should any other errors arise, I would love all the information about these things.

Best regards,

Tin