One PC gets a settings toggle. A hundred PCs need a policy. The Turn off Windows Copilot policy is Microsoft's supported fleet switch - here is exactly what it does, what it misses, and how to roll it out without surprises.
Settings and uninstalls are per-person, per-PC decisions that evaporate the moment a feature update or a curious user walks past. Policy is different: it is a rule the machine itself enforces, for every user, across reboots and most updates. Microsoft ships exactly one policy for this job - Turn off Windows Copilot - and this page sets it three ways (Group Policy, registry for Home edition, and fleet deployment), then grades honestly what it blocks and the one thing it does not do: it does not uninstall the app by itself.
The Local Group Policy Editor (gpedit.msc) ships with Windows 11 Pro, Enterprise and Education. Home edition does not include it, and no download from the internet should ever be trusted to "add" it - those installers are a known malware costume. Home users are not locked out of the result, though: this policy is stored as a registry value, and card four sets exactly that value by hand. If you manage a domain, the same policy exists in your central Group Policy Management console and everything in this page scales up unchanged.
Press Windows + R, type gpedit.msc and press Enter. Navigate to User Configuration > Administrative Templates > Windows Components > Windows Copilot and double-click Turn off Windows Copilot. Choose Enabled - the confusing but universal Group Policy convention: enabling the policy enables the turn-off - then click Apply and OK. Run gpupdate /force in a terminal (or restart) and try launching Copilot: the entry points stop working. Because this is a user-configuration policy, it follows the user account; a computer-configuration twin exists in domain templates where you need it per-machine.
With the policy set, Windows Copilot cannot be launched from the taskbar, the keyboard shortcut or Start, and the integration is hidden for that user. What the policy does not do is delete the Copilot app package from the disk, block Edge's separate Copilot sidebar, or touch Microsoft 365 Copilot - each of those has its own control. Newer Windows builds also add a Remove Microsoft Copilot app policy under the Windows AI policies, which targets the app itself under specific conditions; treat it as a companion to set alongside, not a replacement. Honest grading for the classic policy: blocks the experience, leaves the files - which for compliance and for users is what actually matters.
Group Policy is, underneath, a managed way of writing registry values - so Home users can write this one directly. In Registry Editor, go to HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows, create a key named WindowsCopilot if it is absent, and inside it create a DWORD (32-bit) value named TurnOffWindowsCopilot set to 1. Restart or sign out and back in. You have now set the identical policy the editor would have set. Two honest cautions: back up the key before editing (File > Export), and know that anything you can set by hand, a user with admin rights can unset - on a family PC that is fine; in an office it is why domains exist.
On an Active Directory domain, create or edit a GPO in the Group Policy Management console, set the same Turn off Windows Copilot policy, and link it to the OU holding your user accounts. Pilot it on one small OU first, confirm Copilot is blocked and nothing else broke, then link wider. In Microsoft Intune shops, the Settings Catalog carries the same setting as Turn off Copilot in Windows (User) in a configuration profile - assign it to a test group before the whole tenant. The pattern is identical either way: one policy object, one pilot group, one verification, then the fleet. Your helpdesk will thank you for the pilot step the first time any policy anywhere behaves unexpectedly.
Do not trust the editor's Enabled tick alone; verify as the user. Sign in as a normal user, try the taskbar button, the Copilot key and Start search - all should fail to launch Copilot. On a domain PC, gpresult /r shows whether the policy object actually applied. Then note the durability honestly: policy is the layer feature updates respect most, because updating Windows does not rewrite policy stores - which is precisely why this route, and not a pile of uninstalls, is the professional answer for machines you manage for other people.
Every step shown live on a real Windows 11 PC - which AI features go, which stay, and the honest limits of removing them.
▶️ Watch Full VideoNo. The policy prevents Copilot from launching and hides its entry points for the user, but the app package can still be present on the disk. That is usually enough - an app that cannot run is not a daily problem. Newer builds add a companion Remove Microsoft Copilot app policy aimed at the package itself under certain conditions; many admins set both.
A standard user cannot - policy settings are enforced by the system and the user-facing toggles go quiet. A user with local administrator rights can change almost anything on a standalone PC, which is why offices deliver policy from a domain or Intune, where the setting is reapplied centrally at every refresh even if someone tampers locally.
No. The policy is stored as the registry value TurnOffWindowsCopilot under the WindowsCopilot policy key, and setting it by hand on Home gives the same result as the Group Policy editor on Pro. What Home lacks is the central management - each Home PC is a one-by-one job, which is worth knowing when you buy the next batch of machines.