So here’s the thing that got me: I disabled Copilot’s taskbar icon weeks ago, restarted my PC, and there it was again — running quietly in the background, eating a chunk of memory before I’d even opened a browser. Turns out hiding Copilot and stopping it from starting automatically are two completely different settings, and almost nobody mentions that distinction clearly. If you just want Microsoft Copilot to stop launching itself on every boot, here’s where to actually go.
Quick Answer: Stop Copilot Starting Automatically
- Open the Copilot app itself, go to Settings, and toggle off “Auto start on login”
- Check Task Manager’s Startup apps tab — Copilot may be listed there separately and re-enabled after an update
- For a system-wide block, use Group Policy (Pro/Enterprise) or the registry equivalent (Home)
- Uninstall the app entirely if you don’t want it at all, not just quieted down
Why Copilot Keeps Starting on Its Own
There are a few overlapping reasons this happens, and honestly the confusion is partly Microsoft’s fault — there isn’t one single “Copilot” anymore, there are several things wearing the same name.
The first reason is the most direct one: Copilot has its own dedicated auto-start setting baked into the app itself, separate from Windows’ general startup app list. This setting got added specifically because users kept asking for it, but it’s buried in a spot most people never open since they interact with Copilot from the taskbar, not the app’s own settings page.
Second, Windows updates have a habit of resetting toggles that aren’t enforced by policy. So you turn it off, a cumulative update lands, and Copilot quietly turns itself back on. This isn’t unique to Copilot, but it happens often enough with it that people assume they’re doing something wrong when they’re not.
Third — and this one catches a lot of people — there’s a difference between the Copilot app, Microsoft 365 Copilot, and the Copilot integration baked into things like Edge, Notepad, and Paint. Disabling autostart for one doesn’t touch the others. If you’ve got the 365 version installed too, that’s a separate uninstall and a separate set of toggles entirely.
The Two Settings People Mix Up
| What You Disabled | What Actually Happens | What It Doesn’t Do |
|---|---|---|
| Hide Copilot icon (taskbar settings) | Icon disappears from taskbar | Copilot can still run in the background |
| Auto start on login (in-app setting) | Copilot won’t launch at sign-in | Doesn’t remove the app or block Win+C |
| Group Policy / registry TurnOffWindowsCopilot | Blocks the taskbar entry and most launch paths | May not stop it being invoked via Start menu search on some builds |
| Uninstall via Settings or PowerShell | App is gone from that user account | Reinstalls if another user signs into the same PC |
Notice that last row. I’ve seen people uninstall Copilot, feel good about it, then have it pop back up because someone else logged into the machine. That’s not a bug exactly, it’s just how per-user app provisioning works on Windows 11 — annoying, but expected.
Step-by-Step: Disable Auto Start in the Copilot App
Step 1: Open the Copilot app
Click the Copilot icon (or search for it in the Start menu if the icon’s already hidden). Once it opens in full view, look at the sidebar.
Step 2: Go to Account settings
Click the Account button in the sidebar, then Settings.
Step 3: Find “Auto start on login” and turn it off
This setting only showed up in builds from version 1.25014.121.0 onward, so if you’re on an older build and don’t see it, that’s probably why — not because you’re missing a click somewhere.
Step 4: Restart and confirm
Reboot, then check Task Manager right after sign-in. If Copilot’s not in the process list, you’re done. If it is, move on to the next section — there’s a second setting hiding in Windows itself that can override this one.
Checking Task Manager’s Startup List
Open Task Manager (Ctrl+Shift+Esc), go to the Startup apps tab, and look for Copilot in the list separately from the in-app toggle. Right-click it and select Disable if it’s there and enabled.
This is the part that trips people up most, from what I’ve seen — the in-app toggle and the Task Manager entry don’t always sync with each other, especially right after a Windows update. So if you disabled it in one place and it’s still launching, check the other.
Going Deeper: Group Policy and Registry
If the app-level toggle keeps getting reset, or you want this enforced system-wide instead of per-user, the policy route is more durable.
On Windows 11 Pro or Enterprise:
- Search “gpedit” and open the Group Policy Editor
- Navigate to User Configuration (or Computer Configuration for all users) > Administrative Templates > Windows Components > Windows Copilot
- Open “Turn off Windows Copilot” and set it to Enabled
- Run gpupdate /force or restart
On Windows 11 Home (no Group Policy Editor):
- Open regedit
- Navigate to HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows
- Right-click Windows, select New > Key, name it WindowsCopilot
- Inside that key, create a new DWORD (32-bit) value named TurnOffWindowsCopilot, set it to 1
- For a machine-wide block instead of per-user, repeat under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows instead
Back up the registry or set a restore point first. I say this every time and people skip it anyway, but seriously — registry edits that go wrong can be a pain to untangle later.
What Actually Worked For Me
I tried the in-app toggle first, which felt like the “correct” fix since it’s literally labeled for this exact problem. Worked fine for about two weeks. Then a Windows update landed and Copilot was back in my startup list like nothing happened — not 100% sure why that specific update reset it, but it wasn’t an isolated case based on what I found searching around afterward.
That’s when I went to the registry route instead, mostly because gpedit isn’t available on the Home edition I was running at the time. Created the WindowsCopilot key, set TurnOffWindowsCopilot to 1, restarted. That one’s held for over a month now without reverting, which is the actual test that matters here — anything can look fixed for a day.
Worth saying: the registry method disables more than just autostart. It blocks the taskbar entry too, so if you specifically only wanted to stop the autostart and keep using Copilot manually, the in-app toggle is still the better first attempt. Just don’t be surprised if you need to redo it occasionally.
Edge Cases and Things People Get Wrong
Typing “copilot” into Start menu search can still launch it even after Group Policy or registry changes on some builds. This is a known gap — the policy blocks the standard launch paths but doesn’t always catch Search invocation, particularly on newer 24H2-era builds. If that matters for compliance reasons in a managed environment, AppLocker rules blocking the Copilot package by publisher are the more durable answer, though that’s really an IT-admin-level fix rather than something most people need.
Multiple Microsoft accounts on one PC will each need this handled separately if you’re using the per-user registry path. The machine-wide HKEY_LOCAL_MACHINE version avoids that, but needs admin rights to set.
And one thing that’s easy to overlook: Gaming Copilot is a separate app from the general Copilot assistant, with its own settings and its own autostart behavior. If you disabled the main Copilot app but it still seems to be running something Copilot-branded in the background, check whether Gaming Copilot is also installed — it often is by default and nobody remembers installing it.
Prevention Tips
- Check Task Manager startup apps after any major Windows feature update, not just after a fresh install
- If you’ve gone the registry route, periodically verify the key is still there after big updates rather than assuming it’s permanent
- Keep in mind Microsoft 365 Copilot, Gaming Copilot, and the consumer Copilot app are three separate things with three separate disable paths
- If managing multiple PCs, the Group Policy or MDM route saves a lot of repeated manual fixing compared to per-device registry edits
FAQ
Why does Copilot keep turning back on after I disable it?
Most commonly a Windows update reset the toggle, or the in-app setting and Task Manager’s startup list got out of sync. Check both.
Does hiding the taskbar icon stop Copilot from running in the background?
No. Hiding the icon and stopping autostart are different settings entirely — Copilot can still be running even with the icon hidden.
Is there one setting that disables Copilot everywhere, including Edge and Office apps?
Not really. Edge’s Copilot sidebar, the standalone app, and Microsoft 365 Copilot each have their own toggle. There isn’t a single master switch covering everything.
Will uninstalling Copilot break anything else in Windows?
Generally no for the standalone consumer app, but it can affect File Explorer’s right-click “Ask Copilot” entry since that’s tied to the same package.
Editor’s Opinion
the auto-start toggle inside the app is the right first move for most people, it’s just oddly hidden and resets more than it should. if you’ve already fought with it once and it came back, go straight to the registry/policy route and skip the back-and-forth — it’s more annoying to set up but it’s held for me a lot longer. also genuinely check for Gaming Copilot, that one’s easy to forget exists.
