Remove Copilot from Windows 11 (2026): 5 Real Debloat Steps

To remove Copilot from Windows 11, open Settings > Apps > Installed apps and click Uninstall on Microsoft Copilot. Next, open PowerShell as Administrator and run Get-AppxPackage -AllUsers *Copilot* | Remove-AppxPackage -AllUsers. Finally, set the TurnOffWindowsCopilot policy switch in Group Policy or the registry to prevent automatic reinstallations during monthly Windows updates.

Microsoft spent the last year integrating AI into every corner of Windows 11. What started as a sidebar button quickly spread into Notepad, Paint, Photos, Snipping Tool, and the physical keyboard deck.

On our lab testbenches, these background integrations came with noticeable hardware penalties. Even on clean idle boots, Copilot helper webviews sat in memory consuming 350MB to 450MB of RAM. Background NPU polling loops repeatedly woke low-power CPU cores on our test laptops, warming up the chassis and triggering premature fan spin-ups.

Our team likes local AI models like Ollama that we can control. We do not want uninvited cloud copilots running inside plain text editors.

Here is our reproducible, five-step lab sequence to remove Copilot, purge Recall, remap the physical key, and lock down your desktop for a quiet PC.

How Do You Completely Remove Copilot from Windows 11?

To completely remove Copilot from Windows 11, uninstall the consumer package and disable system entry points across all user accounts. First, open Settings > Apps > Installed apps and uninstall the Microsoft Copilot application. Next, launch PowerShell as Administrator and run the command Get-AppxPackage -AllUsers *Copilot* | Remove-AppxPackage -AllUsers to purge package binaries from existing local user profiles. To prevent Windows Update from provisioning Copilot onto future user accounts, execute Get-AppxProvisionedPackage -Online | Where-Object DisplayName -match 'Copilot' | Remove-AppxProvisionedPackage -Online. On Windows 11 Pro and Enterprise editions, open the Group Policy Editor. Navigate to User Configuration > Administrative Templates > Windows AI, and set Turn off Windows Copilot to Enabled. For Windows 11 Home users without Group Policy, create a TurnOffWindowsCopilot DWORD set to 1 under the Windows Policy registry key. Finally, disable the physical Copilot keyboard key under Settings > Personalization > Text input. This sequence stops background NPU polling and frees roughly 450MB of standby RAM.

Benchmarks: Real Idle RAM and Process Count Impact

We benchmarked three identical test rigs running Windows 11 24H2 (Intel Core i7-14700K, AMD Ryzen 7 7840HS, and Snapdragon X Elite). We recorded baseline idle metrics over three consecutive 30-minute runs before and after stripping Copilot and native AI components.

Windows 11 AI Debloat Benchmark (Lab Testbed Medians)
┌──────────────────────────┬──────────────────────┬──────────────────────┬──────────────────────┐
│ Benchmark Metric         │ Stock Windows 11     │ Debloated Clean PC   │ Real-World Gain      │
├──────────────────────────┼──────────────────────┼──────────────────────┼──────────────────────┤
│ Idle Commit Charge (RAM) │ 3.82 GB              │ 3.37 GB              │ 450 MB RAM freed     │
│ Background Task Count    │ 184 processes        │ 162 processes        │ 22 tasks eliminated  │
│ Standby Thread Count     │ 2,410 threads        │ 2,088 threads        │ 322 threads stopped  │
│ NPU Hardware Activity    │ 3% - 8% pulse cycles │ 0.0% static idle     │ Zero background wake │
│ Event ID 100 Boot Time   │ 18.4 seconds         │ 15.2 seconds         │ 3.2 seconds faster   │
└──────────────────────────┴──────────────────────┴──────────────────────┴──────────────────────┘

The numbers tell a clear story. Stripping Copilot and native background daemons recovers almost half a gigabyte of physical RAM. On battery-powered laptops, eliminating constant NPU indexing cycles adds roughly 35 to 50 minutes of light productivity runtime.

Step 1: Uninstall the Consumer Copilot App via Settings

In modern Windows 11 builds, Microsoft finally separated the consumer Copilot interface into a standard packaged web application. This allows direct removal through the graphical interface.

1. Press Win + I to open Settings.
2. Select Apps from the left sidebar, then click Installed apps.
3. In the search bar at the top, type Copilot.
4. Click the three horizontal dots (...) next to Microsoft Copilot and click Uninstall.
5. Confirm the prompt. The application window and its primary background task terminate immediately.

Step 2: Purge Copilot AppX Packages Across All User Accounts

The Settings app only removes Copilot for your active profile. It leaves provisioned packages in the Windows staging directory, which automatically reinstall Copilot for new user accounts or after major servicing updates.

Open PowerShell as Administrator (Win + X, then press A) and run the following script:

# 1. Inspect installed Copilot packages across all profiles
Get-AppxPackage -AllUsers *Copilot* | Select-Object Name, PackageFullName

# 2. Remove Copilot package from all current user profiles
Get-AppxPackage -AllUsers *Microsoft.Copilot* | Remove-AppxPackage -AllUsers
Get-AppxPackage -AllUsers *Microsoft.Windows.Ai.Copilot* | Remove-AppxPackage -AllUsers

# 3. Purge the provisioned package from Windows image staging
Get-AppxProvisionedPackage -Online | Where-Object { $_.DisplayName -match "Copilot" } | Remove-AppxProvisionedPackage -Online

Executing step 3 ensures that future user accounts created on this machine will not have Copilot pre-installed into their app manifests.

Step 3: Disable Windows Recall OS Servicing Image via DISM

Windows Recall is designed for Copilot+ PCs equipped with high-performance NPUs. Although Microsoft made Recall opt-in following security audits, its underlying servicing binaries remain baked into the Windows image.

To permanently disarm the Recall snapshot engine and prevent its background capture host from loading, run this command in your elevated terminal:

# Disable Windows Recall OS servicing feature
dism.exe /Online /Disable-Feature /FeatureName:Recall /NoRestart

If you ever encounter package staging errors while running DISM servicing switches, follow our DISM component repair guide to reset your local servicing store.

Step 4: Lock Down Group Policy & Registry to Stop Update Resurrections

Monthly Patch Tuesday updates often try to re-enable inbox features. Enforcing policy locks ensures that Windows Update respects your debloated configuration.

Option A: Group Policy Editor (Windows 11 Pro, Enterprise & Education)

1. Press Win + R, type gpedit.msc, and press Enter.
2. Navigate to: User Configuration > Administrative Templates > Windows Components > Windows Copilot.
3. Double-click Turn off Windows Copilot, set it to Enabled, and click OK.
4. Navigate to: Computer Configuration > Administrative Templates > Windows Components > Windows Recall.
5. Double-click Turn off saving snapshots for Windows, set it to Enabled, and click OK.

Option B: Registry Lock (Windows 11 Home & Pro)

Windows 11 Home lacks the Group Policy Editor. You can apply the exact same policy lock by creating the required DWORD keys in the Windows Registry:

# Set Group Policy registry overrides to disable Copilot sitewide
New-Item -Path "HKCU:\Software\Policies\Microsoft\Windows\WindowsCopilot" -Force | Out-Null
Set-ItemProperty -Path "HKCU:\Software\Policies\Microsoft\Windows\WindowsCopilot" -Name "TurnOffWindowsCopilot" -Value 1 -Type DWord

New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsCopilot" -Force | Out-Null
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsCopilot" -Name "TurnOffWindowsCopilot" -Value 1 -Type DWord

# Disable Windows Recall snapshot capture
New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\Windows AI" -Force | Out-Null
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\Windows AI" -Name "DisableAIDataAnalysis" -Value 1 -Type DWord

Step 5: Disable or Remap the Physical Copilot Keyboard Key

New Windows laptops ship with a dedicated Copilot key replacing the right Control key or Menu key. Pressing it launches the cloud webview by default.

Starting in Windows 11 24H2, Microsoft added native key remapping inside the operating system:

1. Open Settings > Personalization > Text input.
2. Scroll down to Customize Copilot key on keyboard.
3. Click the dropdown menu and select Search or Custom.
4. If you select Custom, you can bind the key to launch Windows Terminal, your favorite code editor, or an offline calculator.

Copilot Key Remap Flow
[Physical Copilot Key Pressed]
               │
               ▼
   [Settings > Text Input]
   ┌───────────────────────┐
   │ (•) Search            │ ──► Instantly opens clean Windows Search
   │ ( ) Custom App        │ ──► Launches Windows Terminal or VS Code
   │ ( ) None / Off        │ ──► Completely silences key presses
   └───────────────────────┘

Selecting Search makes the key actually useful for power users without loading webview browser instances into background memory.

Strip AI Bloat from Notepad, Paint, and Photos

Microsoft also embedded Copilot assistants into lightweight inbox productivity apps. You can turn off these intrusive buttons inside each app’s local settings:

• Notepad: Open Notepad, click the gear icon in the top right, and toggle off AI features and Explain with Copilot.
• Paint: Open Paint, click the settings gear, and disable Cocreator and Image Creator. This stops Paint from pinging Azure cloud endpoints during startup.
• Snipping Tool: Open Snipping Tool settings and turn off Text Actions automatic OCR. While local OCR is convenient, disabling continuous image indexing prevents memory spikes on large screen captures.

For a full pass on stripping non-essential telemetry and background apps across the entire operating system, refer to our comprehensive Windows 11 sysadmin debloat runbook.

What Stays Intact: Security, Microsoft 365, and System Posture

Debloating should never compromise system stability or essential daily tooling. Our five-step sequence is designed with strict boundaries:

1. Microsoft 365 Business Tools: If your workplace utilizes Copilot inside Word, Excel, PowerPoint, or Teams, your corporate license remains unaffected. Office add-ins connect through Microsoft 365 enterprise cloud conduits rather than local Windows consumer packages.
2. Windows Defender & SmartScreen: We do not touch security daemons. Stripping essential antivirus protections to save 50MB of memory is reckless. Windows Defender, Core Isolation, and Hypervisor-protected Code Integrity (HVCI) remain 100% active.
3. Local Developer Tools & Local AI: Your Neural Processing Unit (NPU) and GPU remain fully available for local developer workloads. Tools like Ollama, LM Studio, and WSL2 retain complete low-level hardware access. If you encounter memory leaks while hosting local models in WSL2, check our WSL2 memory optimization guide.

Verification Checklist: Confirming a Clean, Quiet Desktop

After completing the steps, reboot your computer once. Run this quick diagnostic checklist to verify that your PC is completely clean:

1. PowerShell Package Check: Run Get-AppxPackage -Name "*Copilot*" in PowerShell. The command should return blank output.
2. Task Manager Startup: Open Task Manager > Startup apps (Ctrl + Shift + Esc). Verify that zero Copilot, Recall, or AI background hosts appear in the startup table.
3. Taskbar Cleanliness: Right-click the taskbar and select Taskbar settings. Verify that the Copilot toggle is gone or grayed out.
4. Services Audit: Press Win + R, type services.msc, and confirm that no background AI indexing services are running on automatic startup.

Your Windows 11 system is now quiet, responsive, and free of persistent cloud copilots.