Safe ways to remove Copilot from Windows applications

What you see

Copilot keeps coming back after updates, and the side panel, taskbar button, or Start menu entry stays stuck on Windows. I have removed Microsoft Copilot from a few machines, and the cleanest result comes from checking the policy layer first, then the registry, then the app package if it is still there.

Where it happens

The exact spot depends on the Windows build. On Windows 11 Pro and Enterprise, group policy is the cleanest control point. On Home, I use registry tweaks instead. If Copilot still shows as a pinned app or shell entry after that, it is usually a leftover app component or a feature flag that was not fully switched off.

The main mistake is attacking random bits of Windows bloat removal without checking what actually controls Copilot on that box. Remove the wrong thing and you get a mess, not a result.

Find the cause

I check three things.

First, see whether the Copilot policy exists. On Pro and Enterprise, open gpedit.msc and look under User Configuration, Administrative Templates, Windows Components, Windows Copilot. If the policy to turn it off is present, that is the first fix to try.

Second, check whether the setting is being forced by the registry. The common key is:

HKEY_CURRENT_USERSoftwarePoliciesMicrosoftWindowsWindowsCopilot

If the value TurnOffWindowsCopilot exists and is set to 1, the shell should stop showing Copilot for that user.

Third, check whether Copilot is still installed as an app package. If the policy is set but the icon still stays put, the package may still be present for the current profile or already staged from an update.

Fix

On Windows 11 Pro or Enterprise, set the policy first.

  1. Run gpedit.msc.
  2. Open User Configuration, Administrative Templates, Windows Components, Windows Copilot.
  3. Set Turn off Windows Copilot to Enabled.
  4. Sign out and sign back in.

If gpedit is missing, use the registry.

  1. Open Registry Editor.
  2. Go to HKEY_CURRENT_USERSoftwarePoliciesMicrosoftWindows.
  3. Create a key called WindowsCopilot if it does not exist.
  4. Create a DWORD value called TurnOffWindowsCopilot.
  5. Set it to 1.
  6. Sign out and sign back in.

If you want to block it at machine level for all local users, use:

HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftWindowsWindowsCopilot

Set TurnOffWindowsCopilot to 1 there as well.

If Copilot still shows after that, remove the app package for the current account. Open PowerShell as the user and check what is installed:

Get-AppxPackage *Copilot*

If it returns a package, remove it:

Get-AppxPackage *Copilot* | Remove-AppxPackage

If the package is provisioned for new profiles, check this too:

Get-AppxProvisionedPackage -Online | Where-Object DisplayName -like "*Copilot*"

If it appears there, remove that provisioned package with the matching package name. That stops Windows from putting it back for the next profile. This is the bit that usually saves a second round of swearing.

If you are locking down a box and want the change to stick, I also check Windows privacy settings while I am there. Copilot is not the only thing Windows likes to light up again after an update.

Check it is fixed

After the change, sign out and sign back in, then do a full reboot.

Check that:

  • the Copilot button is gone from the taskbar
  • Win + C no longer opens the Copilot pane
  • Get-AppxPackage *Copilot* returns nothing for the current user
  • the policy value still reads 1 after a reboot

If the button returns after Patch Tuesday, the policy did not land where Windows expects it. Check both the user policy path and the machine policy path. If the package comes back, remove the provisioned app again. Windows enjoys undoing tidy work.

Related posts

Weekly Tech Digest | 06 Jul 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.

wolfCOSE zero-allocation parsing in embedded C

wolfCOSE looks sensible only if you care about what your firmware actually has to carry. I like that, because on small targets the wrong crypto feature can cost more than the message itself, and there...

restic | v0.19.1

restic v0 19 1: safer FUSE mounts and mountpoint checks, robust backup source and exclude handling, clearer CLI JSON output, Windows SFTP deletion fixes