Fix Windows 11 Copilot & Recall RAM Drain

When I opened Task Manager on my main desktop a few weeks ago just to see why a video export was crawling, I wasn't expecting to find the culprit sitting quietly under the "Background processes" list. Copilot. Just sitting there, chewing through close to 1.5GB of RAM, on a machine where I had already turned the Copilot toggle off in Settings months earlier. I hadn't opened Copilot once that day. I hadn't pressed Win+C. It was just... running.

That sent me down a two-week rabbit hole of testing every "fix" I could find, and here's the frustrating part: almost every guide I read told me to do the exact same useless thing — right-click the taskbar, hide the icon, call it a day. That doesn't kill anything. It just hides the button. If you searched for a way to completely disable Windows 11 Copilot and you're still watching RAM disappear, you're dealing with the same gap I was: the difference between a UI toggle and an actual background OS service.

This guide skips the surface-level advice entirely. I'm going to walk you through the exact Group Policy and Registry Editor method I used to kill Copilot at the OS level, plus the separate (and honestly more important, if you own newer hardware) fix for Microsoft Recall, which raises privacy concerns most users don't even realize apply to them.

Why Is Copilot Still Running After You "Turned It Off"?

This is the part almost nobody explains properly, so let's get it straight first.

When you go to Settings > Personalization > Taskbar and flip the Copilot toggle off, or right-click the taskbar and uncheck it, you're not disabling Copilot. You're telling Windows Explorer to stop showing a shortcut icon. That's it. The underlying app package, the background triggers tied to your search box, the Win+C keyboard shortcut, the dedicated Copilot key on newer keyboards, and the sidebar integration in Edge are all still fully installed and still allowed to launch whenever something on your system calls them.

Think of it like unplugging a lamp but leaving the wiring live behind the wall. The visible switch is gone, but the circuit is still hot, and anything else connected to that circuit can still trigger it. That's exactly why people report Copilot showing up in Task Manager's memory list days after they "disabled" it — a background trigger (an app integration, a scheduled task, an update re-provisioning the package) fired it back up, and there was no policy actually blocking it from running.

To genuinely stop the RAM drain, you have to disable Copilot at the policy or registry level, which is the layer that controls whether the app is allowed to execute at all — not just whether its icon is visible.

Copilot vs. Recall vs. Click to Do: You're Probably Only Fighting One of Them

Before you start editing anything, it's worth knowing which of these features your PC can actually run, because most articles on this topic lump them together and it leads to a lot of wasted time.

• Windows Copilot is the chat-based AI assistant. It runs on every Windows 11 PC, regardless of hardware, and it's the one most commonly responsible for the background RAM usage people report.
• Microsoft Recall is a completely different feature that takes periodic screenshots of your screen and makes them searchable locally. It is not available on most Windows 11 PCs. Recall only runs on Copilot+ PCs — machines with an NPU rated at 40+ TOPS, 16GB of RAM, and 256GB of storage, the kind shipping with Snapdragon X, Intel Core Ultra 200V, or AMD Ryzen AI 300-series chips. If your PC was built before mid-2024, or it doesn't have one of those NPUs, Recall physically isn't on your device — no setting will "turn it off" because it was never running in the first place.
• Click to Do is a smaller, NPU-dependent feature that also only exists on Copilot+ hardware.

So if you checked Task Manager and saw memory usage tied to "Copilot," that's almost certainly the Copilot app itself, not Recall. If you own one of the newer Copilot+ laptops, though, you'll want to work through both sections below, because Recall carries its own separate privacy and storage cost on top of the RAM Copilot uses.

Before You Touch the Registry: Do This First

I'm not going to pretend registry edits are risk-free, because they're not. A wrong value in the wrong key can cause real problems. Here's what I did before making any changes, and what you should do too:

• Create a System Restore point. Search "Create a restore point" in Start, click Create, and give it a name you'll recognize. This is your undo button if anything goes sideways.
• Back up the specific registry key you're editing. Once you're inside Registry Editor at the path below, right-click the key and choose Export before you change anything, so you can double-click the file to restore it instantly if needed.
• Only edit the exact keys listed below. Don't go poking around neighboring keys "just in case" — stick to the path.

With that out of the way, here's the actual fix.

The Complete Fix: How to Completely Disable Windows 11 Copilot

Method 1: Group Policy Editor (Windows 11 Pro, Enterprise, Education)

If you're on Pro or a business edition, this is the cleanest way to do it, because it's the officially supported policy Microsoft built for exactly this purpose.

1. Press Win + R, type gpedit.msc, and hit Enter
2. Navigate to User Configuration > Administrative Templates > Windows Components > Windows Copilot
3. Double-click "Turn off Windows Copilot"
4. Select Enabled, then click Apply and OK
5. Open Command Prompt as admin and run gpupdate /force
6. Restart your PC

This blocks Copilot from launching through any entry point — the taskbar, Win+C, the search box, and the dedicated Copilot key. One thing worth flagging honestly: some of Microsoft's documentation has started marking this specific policy as a legacy control that may eventually be replaced with newer AI-management policies in future builds. It works reliably on current 2026 builds, but it's exactly why I'd pair it with the registry method below rather than relying on GPO alone.

Method 2: Registry Editor (Works on Windows 11 Home Too)

Windows 11 Home doesn't ship with gpedit.msc, but the Group Policy setting above is really just writing a value into the registry behind the scenes — so you can set that same value directly, and it works identically.

1. Press Win + R, type regedit, and hit Enter (click Yes on the UAC prompt)
2. Navigate to: HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows
3. Right-click the Windows folder → New > Key, and name it WindowsCopilot
4. Click the new WindowsCopilot key, then right-click the empty space on the right → New > DWORD (32-bit) Value
5. Name it TurnOffWindowsCopilot and set its value data to 1
6. Close Registry Editor and restart your PC

If you'd rather not click through the GUI, here's the same change as a .reg file you can save and double-click (back up first, as noted above):

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\WindowsCopilot]
"TurnOffWindowsCopilot"=dword:00000001

To reverse either method, just change that value back to 0, or delete the WindowsCopilot key entirely, then reboot.

Bonus: Actually Remove the Copilot App (Not Just Block It)

The steps above stop Copilot from launching, but the app package technically stays installed. On most current builds, you can remove it outright the same way you'd uninstall any other app:

1. Go to Settings > Apps > Installed apps
2. Search for Copilot
3. Click the three-dot menu next to it and select Uninstall

If that option is greyed out on your build, the PowerShell equivalent (run as administrator) is:

Get-AppxPackage -allusers *Microsoft.Copilot* | Remove-AppxPackage

Keep in mind a future feature update can silently reinstall it — this is a known behavior with tightly-integrated Windows apps, so it's worth re-checking after any major Windows update rather than assuming it's gone for good.

How to Turn Off Microsoft Recall (Save Storage and Protect Your Privacy)

If you confirmed above that your PC is actually a Copilot+ device, here's how to shut Recall down properly — not just pause it.

Step 1: Confirm You're Actually Dealing With Recall

Go to Settings > System > About and check your processor. If it's not a Snapdragon X, Intel Core Ultra 200V-series or newer, or AMD Ryzen AI 300-series chip with an NPU, Recall isn't installed on your device, and the Copilot fix above already covers your RAM issue.

Step 2: Turn Off Snapshot Saving From Settings

This is the fastest way to stop new data collection immediately:

1. Open Settings > Privacy & security > Recall & snapshots
2. Toggle Save snapshots to Off
3. Scroll down and select Delete snapshots > Delete all to wipe anything already captured

This step alone stops new snapshots and clears the old ones, but the setting is just a toggle — anyone with access to the PC (or a Windows update that resets preferences) could flip it back on. For anything you actually care about keeping private, go a step further.

Step 3: Lock It Down With Group Policy or the Registry

Group Policy (Pro/Enterprise/Education):

1. Open gpedit.msc
2. Go to User Configuration > Administrative Templates > Windows Components > Windows AI
3. Double-click "Turn off saving snapshots for use with Recall"
4. Set it to Enabled, click Apply, then OK, and restart

Registry equivalent (works on Home too):

Navigate to HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\WindowsAI (create the WindowsAI key if it doesn't exist) and add a DWORD named DisableAIDataAnalysis set to 1. As a .reg file:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\WindowsAI]
"DisableAIDataAnalysis"=dword:00000001

This is the same policy value Microsoft documents for IT administrators managing Recall across fleets of devices, so it's a legitimate, supported control — not a hack.

Step 4: Remove Recall as a Feature Entirely (The Nuclear Option)

If you want it completely gone rather than just switched off, you can remove it as a Windows feature:

1. Search "Turn Windows features on or off" in Start and open it
2. Find and uncheck Recall
3. Restart your PC

This uninstalls the feature outright and deletes any remaining snapshot data with it. If you prefer PowerShell (run as administrator):

Disable-WindowsOptionalFeature -Online -FeatureName "Recall" -Remove

For the full breakdown of every privacy control Microsoft offers around snapshot filtering and sensitive-content detection, Microsoft's official Recall privacy page covers it directly.

How I Verified It Actually Worked

Don't just trust the toggle — check it the same way I did:

• Open Task Manager > Details tab, sort by Memory, and confirm nothing Copilot-related shows up after a fresh reboot
• Press Win + C and confirm nothing launches
• Type a query into the taskbar search box and confirm no Copilot answer card appears
• If you also disabled Recall, check Settings > Privacy & security > Recall & snapshots and confirm the option is greyed out or shows as managed by policy

On my desktop, RAM usage dropped noticeably within a few minutes of the reboot, and Copilot hasn't reappeared through any update since.

My Honest Take

I don't think Copilot or Recall are inherently bad features — Recall in particular is genuinely well-engineered from a technical standpoint, with on-device processing and Windows Hello gating built in. My issue isn't with the technology; it's that neither one should cost you RAM or screen-recording by default without a clear, permanent off-switch that actually sticks. The Settings toggles Microsoft ships are reversible by design, which works fine for casual users but isn't good enough if you actually want these features gone.

The policy method above is the real fix, and it's the same control Microsoft gives its own IT administrators to manage this across entire companies — you're just applying it to one PC. The one thing I'd genuinely recommend: bookmark this page and re-check your settings after any major feature update (24H2, 25H2, and whatever comes after). Deep OS integrations like this are exactly the kind of setting that can get quietly reset when Microsoft ships a big update.

Frequently Asked Questions

Why is Copilot still running in the background after I hid the icon from the taskbar?

Hiding the icon from the taskbar only removes the shortcut button — it's a UI-layer change, not a system-level one. The Copilot app package and its background triggers (search box integration, the Win+C shortcut, the Copilot key) stay fully active and installed, so the process can still launch and consume RAM even though you can't see a button for it anymore. You have to disable it through Group Policy or the registry to actually stop it from launching.

How do I completely remove Windows 11 Copilot?

Use the Group Policy Editor: go to User Configuration > Administrative Templates > Windows Components > Windows Copilot, enable "Turn off Windows Copilot," run gpupdate /force, and restart. On Windows 11 Home, where Group Policy isn't available, set the same value directly through the registry at HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\WindowsCopilot with a TurnOffWindowsCopilot DWORD set to 1. For a full uninstall of the app itself, remove it from Settings > Apps > Installed apps, or via PowerShell.

How do I turn off Microsoft Recall to save storage and privacy?

First confirm your PC is actually a Copilot+ device with an NPU — if it isn't, Recall was never installed on it. If it is, go to Settings > Privacy & security > Recall & snapshots, turn Save snapshots off, and delete any existing snapshots. For a permanent lock, enable "Turn off saving snapshots for use with Recall" in Group Policy, or set the DisableAIDataAnalysis registry value to 1 under HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\WindowsAI. To remove the feature completely, uninstall it through "Turn Windows features on or off."

Will this fix survive a Windows Update?

In most cases, yes — because you're setting a policy value rather than just toggling a preference, it's far more resistant to being reset than the Settings-app toggles are. That said, deep AI integrations are an area Microsoft actively keeps changing, so it's genuinely worth spending thirty seconds checking Task Manager after any major feature update just to confirm nothing got silently re-enabled.

---

If you're also dealing with a background AI feature quietly draining your battery or RAM on the mobile side, my Android System Intelligence battery drain fix walks through a very similar situation — a background AI process that Google doesn't make easy to actually shut off either.