Microsoft has shipped an official policy that removes the consumer Microsoft Copilot app from Windows 11, but it won’t pull the trigger until the app has sat unused for 28 days. The new “Remove Microsoft Copilot app” setting—available through Group Policy, the registry, or mobile device management—marks the first time Windows itself can fully uninstall the package, rather than just hide an icon. For anyone who wants Copilot gone today, you’ll need a different approach.

What the New Policy Actually Does

Flip the “Remove Microsoft Copilot app” policy to Enabled, and Windows will eventually uninstall the Microsoft.Copilot package. That’s a genuine removal—not a taskbar tweak or a block that leaves binaries behind. The policy appeared in Windows 11 version 24H2 and lives under User Configuration > Administrative Templates > Windows Components > Windows AI. The equivalent registry value sits at HKEY_CURRENT_USER\\Software\\Policies\\Microsoft\\Windows\\WindowsAI\\RemoveMicrosoftCopilotApp with a DWORD of 1.

But the policy’s name overpromises. Uninstallation only happens when several conditions are met:

  • The Microsoft Copilot app must be installed as a provisioned package—not manually from the Microsoft Store.
  • The app must not have been launched in the preceding 28 days.
  • Microsoft 365 Copilot (the paid workplace experience) must also be installed on the device. The policy is designed to clean up the consumer app when a business version already exists.
  • The device must run a supported Windows 11 release, and the policy must actually apply on that edition (Pro and Home nuances ahead).

In other words, the setting targets an app that is already dormant and was pushed by Microsoft or a system image—not one that a user actively chose. If a user opens Copilot even once, the countdown resets.

The 28‑Day Waiting Period: Why Your Copilot Won’t Disappear Overnight

The 28-day inactivity window is the standout restriction. It means the policy is not an emergency “off” switch. If your compliance team wants Copilot absent by end of quarter, you need to stop using it a month ahead—or supplement the policy with an immediate removal action.

The rationale is clear: Microsoft doesn’t want to silently yank an app that someone might rely on. But for enterprise environments that need deterministic baselines, or for home users who simply want a clean system, the delay undercuts the setting’s usefulness. Pairing the policy with a one‑time PowerShell uninstall is the practical workaround (see below).

Removing Copilot Right Now: Three Methods

1. Uninstall from Windows Settings

For a single unmanaged PC, the fastest path is Settings > Apps > Installed apps. Search for “Copilot,” select the three‑dot menu, and choose Uninstall. If the option is present, this is the safest and most transparent method. It doesn’t require administrative templates, registry edits, or a delay. However, if the app was provisioned or the uninstall button is grayed out, you’ll need one of the approaches below.

2. PowerShell for Instant Removal

When you need Copilot gone now—and you don’t want to wait for Group Policy evaluation—PowerShell is the answer. Open Windows Terminal (as administrator) and run:

$copilot = Get-AppxPackage -Name \"Microsoft.Copilot\"
if ($copilot) {
    Remove-AppxPackage -Package $copilot.PackageFullName
}

This targets only the consumer Microsoft.Copilot package for the current user. It’s quick, leaves no trace, and respects package identity. Avoid sloppy wildcards that could hit other Copilot‑branded components (e.g., Microsoft 365).

Combine with the policy: After removal, set the registry value or Group Policy to signal your preference. The policy won’t re‑trigger removal immediately, but it records your intent for future app evaluations. If Copilot sneaks back through a feature update or Store sync, Windows will eventually clean it up again—after another 28 idle days.

3. Group Policy and Registry: The Long Game

If you manage many devices or want a set‑and‑forget configuration, use the Group Policy path. On a supported edition of Windows 11:

  1. Press Win + R, type gpedit.msc, and hit Enter.
  2. Navigate to User Configuration > Administrative Templates > Windows Components > Windows AI.
  3. Double‑click Remove Microsoft Copilot app.
  4. Select Enabled, then Apply and OK.
  5. Refresh policy with gpupdate /force (or sign out and back in).

For Windows 11 Home—which lacks the Local Group Policy Editor—the registry method is your route. Navigate to HKEY_CURRENT_USER\\Software\\Policies\\Microsoft\\Windows, create a new key called WindowsAI, then inside it create a DWORD (32‑bit) Value named RemoveMicrosoftCopilotApp and set it to 1. Restart or sign out.

Both methods will not cause an immediate uninstall. They merely enable the policy logic. After 28 days of inactivity (and if the other conditions hold), the app will be removed.

How We Got Here: Copilot’s Evolution on Windows

Copilot’s journey on Windows 11 explains why you can’t just rely on old “Turn off” switches. The original Copilot was a web‑backed sidebar integrated into the shell. Microsoft then shifted to a separately serviced packaged app—the Microsoft.Copilot package. Meanwhile, the brand exploded across Microsoft 365, Edge, and dedicated Copilot+ PCs.

Today, a Windows user can encounter at least five distinct Copilot flavors: the consumer chat app, Microsoft 365 Copilot (licensed, work‑oriented), Copilot Chat inside Microsoft 365, individual app integrations (Word, Excel, etc.), and device‑level Copilot+ features. Removing the consumer app doesn’t touch any of the others.

Earlier administrative controls, like the “Turn off Windows Copilot” policy at HKEY_CURRENT_USER\\Software\\Policies\\Microsoft\\Windows\\WindowsCopilot, only hid the sidebar or blocked access. Those settings are now considered legacy and do nothing to uninstall the packaged app. The new policy is Microsoft’s acknowledgment that some users and organizations want the consumer app completely absent—not just invisible.

What to Do After Removal: Preventing Copilot’s Return

The removal policy is not a deny rule. Users can reinstall Copilot from the Microsoft Store, and a feature update or provisioning mechanism could redeploy it. If you need durable prevention, you must go beyond the policy.

For IT administrators, Microsoft recommends AppLocker. A packaged‑app deny rule can block the Microsoft.Copilot package publisher. This controls both installation and execution:

  • Gather the package identity from an authentic installed copy.
  • Create a deny rule using the Microsoft publisher and the MICROSOFT.COPILOT package name.
  • Deploy in audit mode first, review AppLocker event logs, then enforce.

But AppLocker misconfigurations can silence other Store apps if scoped too broadly. Test carefully. For enterprises, also review every deployment channel: Intune, Configuration Manager, scripts, Store for Business, and Windows Update. A script that uninstalls while another tool provisions the same app creates a wasteful loop.

For home users, the simplest prevention is the policy + uninstall combo, plus regular checks. There’s no built‑in block on Home, so you’re dependent on the Store re‑install trigger. If you see Copilot reappear, remove it again and ensure the registry value is still in place.

Verification: Did It Work?

After taking action, confirm Copilot is really gone:

  • Go to Settings > Apps > Installed apps and search for Copilot.
  • Run Get-AppxPackage -AllUsers -Name \"Microsoft.Copilot\" in PowerShell. An empty result means the consumer package is not registered on the system.
  • For policy‑based attempts, run gpresult /h report.html (for Group Policy) or check the registry value with reg query HKCU\\Software\\Policies\\Microsoft\\Windows\\WindowsAI /v RemoveMicrosoftCopilotApp. A 0x1 value means the policy is set, but remember it only triggers removal after the conditions are met, so you may still see the package installed.

Important: Absence of the consumer app does not mean “all AI is off.” Copilot still lives at copilot.microsoft.com, inside Edge, in Office apps, and on the taskbar if Windows decides to pin a web link. Blocking those requires separate browser, identity, and network controls.

Outlook: More Controls on the Horizon

Microsoft’s Windows AI policies are in flux. The legacy “Turn off Windows Copilot” setting is deprecated, and the new package‑based policy is a first iteration. Behind the scenes, Windows now has broader frameworks to remove designated inbox and packaged apps on Managed Enterprise and Education editions—frameworks that can act at sign‑in and persist. Those may eventually replace the Copilot‑specific 28‑day rule for organizations that need absolute control.

For now, the “Remove Microsoft Copilot app” policy is a meaningful upgrade over cosmetic tweaks, but it’s best understood as a deferred cleanup tool. Admins and power users should combine it with immediate PowerShell removal, verify the result, and layer AppLocker or other prevention if re‑installation must be blocked. As Microsoft continues to refine Copilot’s many incarnations, expect management controls to keep shifting—and a pure “off” button to remain a multi‑step process.