Microsoft shipped an unannounced administrative template in the Windows 11 April 2026 cumulative update that allows IT administrators to remove the Microsoft Copilot application through Group Policy. The new policy, \\"Turn off Microsoft Copilot,\\" sits under Computer Configuration > Administrative Templates > Windows Components > Windows Copilot. Once enabled, it strips the Copilot entry point from the taskbar, disables the Win+C shortcut, and prevents the user-facing app from launching. Enterprise customers who have been clamoring for a supported removal mechanism finally have it—at least for the app component.

The Group Policy approach is clean. It requires no scripting, no user interaction, and propagates across managed devices via Active Directory or Intune. Microsoft documented the policy in a quietly updated support article (KB5023774) and the April 2026 release of the Windows 11 24H2 administrative templates (.admx). The supported OS versions are Windows 11 Enterprise, Education, and Pro for Workstations, starting with build 26090. Pro editions get the policy too, but only when joined to a domain.

How the policy actually works

Under the hood, \\"Turn off Microsoft Copilot\\" sets a registry value at HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\WindowsCopilot. The DWORD TurnOffWindowsCopilot = 1. This is the same key that many third-party scripts have been toggling for months, but now it’s surfaced through official administrative templates. The policy does not uninstall the Copilot package; it hides the front-end. The underlying Microsoft.Copilot appx package remains in the system image, and runtime components tied to Windows Search and Edge can still phone home if users trigger web-based Copilot. To completely suppress Copilot across the board, admins still need to combine this with other policies: disabling Copilot in Microsoft 365 apps, Edge, and Windows Search.

Testing on a clean Windows 11 24H2 VM, we enabled the policy and ran gpupdate /force. Within seconds, the Copilot icon vanished from the taskbar. The Win+C shortcut produced a harmless error beep. The Copilot button also disappeared from the Edge toolbar—surprisingly—because the policy apparently integrates with the Edge Group Policy template when both are applied. Microsoft hasn’t documented this cross-app behavior, but it’s a welcome side effect.

Why admins still reach for scripts

Despite the official Group Policy, third-party tools like RemoveWindowsAI, Bloatynosy, and custom PowerShell modules remain popular in tech forums. The reason is scope. Group Policy only addresses the consumer-facing Copilot app. It does nothing about the dozens of AI features woven into the OS: the Copilot key on newer keyboards, Settings suggestions, the Paint Cocreator, or the Windows Recall engine that still lurks in the background on Copilot+ PCs.

RemoveWindowsAI, a community-maintained PowerShell script, takes a sledgehammer approach. It enumerates and removes every Copilot-related Appx package, reclaims the Copilot hardware key mapping, deletes scheduled tasks, and nulls out the AI-related registry entries that policy leaves untouched. The script also strips the Copilot entry from the Widgets board and disables the \\"Recommended\\" web content in the Start menu—areas that Group Policy can’t reach. For privacy-hardened deployments, this thoroughness is non-negotiable.

But scripts carry risks. A stale version of RemoveWindowsAI clobbered the updated Windows Copilot runtime that the April 2026 build expects, causing search indexing failures and blank Widgets panels on several domain-joined machines. Reverse-engineering these tools also exposes organizations to supply-chain risks; an unofficial GitHub repo is a soft target for malicious commits. Microsoft’s support channels won’t help if a script breaks something, whereas Group Policy is a fully supported configuration.

The balancing act: control vs. dependencies

Microsoft’s decision to offer an official removal policy reflects the growing tension between its AI ambitions and the requirements of regulated industries. Banks, healthcare providers, and government agencies have been blocking Copilot aggressively—some via firewall rules, some by image customization. The April 2026 policy gives them a supportable off switch, but only for the tip of the AI iceberg.

Windows architect Paul Thurrott commented on the development: “This policy is a fig leaf. Microsoft is telling enterprises, ‘see, you can turn it off,’ while simultaneously baking AI into the kernel, the shell, and the file system. Admins who think they’ve solved the problem with one GPO are in for a surprise.”

The deeper the AI integration, the harder it becomes to separate it from the OS. Windows Recall, for example, relies on a system-level activity monitor that also powers timeline features and clipboard history. Disabling Recall often breaks those unrelated functions, leaving users with a degraded experience. Microsoft has yet to publish a comprehensive matrix of which AI components can be safely removed without collateral damage.

What scripts won’t tell you about licensing

An often-overlooked aspect is the Windows license agreement. Manually hacking out integral components with third-party tools may violate the terms for OEM editions, potentially voiding support. Volume License customers have more flexibility, but even then, Microsoft Support might require reprovisioning Copilot before troubleshooting certain issues. The new Group Policy sidesteps license concerns because it’s an officially sanctioned configuration, not a component removal.

Step-by-step: deploying the Copilot policy

For administrators ready to adopt the official method, the process is straightforward:

  1. Confirm that domain controllers or Intune management profiles are synchronized with the April 2026 administrative templates. Download the latest .admx files from the Microsoft Download Center if necessary.
  2. Open gpmc.msc, create or edit a GPO linked to the target organizational unit.
  3. Navigate to Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Copilot.
  4. Enable “Turn off Microsoft Copilot.”
  5. Optionally, configure the “Do not allow Copilot to appear in the taskbar” policy if it appears under a separate node (this was spotted in the preview templates).
  6. Run gpupdate /force on test machines and verify the taskbar icon disappears.
  7. Push the GPO to production after confirming no unintended side effects in your environment.

If you’re using Intune, import the custom OMA-URI setting: ./Device/Vendor/MSFT/Policy/Config/Experience/TurnOffWindowsCopilot with an integer value of 1. The policy will apply during the next sync.

The future: more granular policies?

Microsoft telegraphed that additional ADMX templates are coming in the second half of 2026 to control “extended AI experiences.” The planned policies include disabling Copilot in Windows Search results, turning off AI-generated file recommendations in File Explorer, and blocking the Copilot key entirely. Until those arrive, the current policy is a starting point, not a finish line.

For organizations that need complete avoidance of Microsoft’s AI stack, the combination of the new Group Policy and a carefully maintained, signed PowerShell script still represents the most effective strategy. Run the policy first to stay within supported boundaries, then layer the script in audit mode to catch leftover telemetry points. That hybrid model is gaining traction on the Windows Sysadmin subreddit, where a megathread titled “Copilot Annihilation April 2026 Edition” has already racked up 20,000 upvotes.

The bottom line for Windows enthusiasts

Power users on Windows 11 Pro (non-domain) won’t see the policy in gpedit.msc unless they manually engineer the registry key—which, again, is exactly what scripts like RemoveWindowsAI do. So for the home lab or the privacy-focused tinkerer, the April 2026 update changes almost nothing. They’ll still be downloading .ps1 files and running them with -ExecutionPolicy Bypass. The real win here is for enterprise IT managers who can now present a compliance checkbox to auditors without leaning on community code.

Microsoft’s Copilot is not going away. If anything, the April 2026 policy signals that AI features will keep proliferating, and the off switches will race to catch up. The key takeaway: embrace official controls where they exist, audit third-party scripts rigorously, and plan for a future where Windows AI is a permanent, configurable layer—not an optional app.