Windows 11 Insider Preview Adds One-Time Copilot Uninstall for Managed Devices

Microsoft has quietly given IT administrators a supported — but deliberately narrow — way to remove the consumer Microsoft Copilot app from managed Windows 11 devices, introducing a new Group Policy in the January Insider Preview that performs a one‑time uninstall only when a strict set of gating conditions are met. crosoft’s Copilot family now spans multiple products and delivery channels: a consumer‑facing Microsoft Copilot app that ships with many Windows 11 images, a subscription‑backed Microsoft 365 Copilot that is tenant‑managed, and a variety of shell and OS integrations (taskbar button, Copilot hardware key, Win+C shortcut, File Explorer entries, and protocol handlers). That multiplicity has created real operational and governance headaches for IT teams that need deterministic control over what runs on managed endpoints.
In response, Microsoft added a Group Policy named Rep to Windows 11 Insider Preview Build 26220.7535 (delivered as KB5072046). The setting is exposed in the Local Group Policy Editor under:
User Configuration → Administrative Templates → Windows AI → Remove Microsoft Copilot App. It’s currently targeted at managed SKUs — Windows 11 Pro, Enterprise, and Education — and surfaced in the Dev and Beta Insider channels.

---

What Microsoft shipped — the facts administrators need​

• Policy name: RemoveMicrosoftCopilotAWindows 11 Insider Preview Build 26220.7535 (packaged as KB5072046**) to Dev & Beta channels.
• Group figuration → Administrative Templates → Windows AI → Remove Microsoft Copilot App Windows 11 Pro, Enterprise, Education** (managed devices).
• Behavior: performs a one‑time uninstall of the consumer Copilot app for the targeted user only when all gating conditions are st** create a persistent ban.

These are the core, verifiable points administrators should validate in a test ring before any production rollout.

---

The gating conditions: why this isn’t a universal “kill switch”​

Microsoft intentionally built the policy as a surgical cleanup tool rather than a fleet‑wide disable. The uninstall will only run when all of the following conditions are true for the targeted user/device:

• Both Micront‑managed, paid) and the consumer Microsoft Copilot app are installed on the device. Microsoft added this guard to avoid removing the only Copilot experience a paid tenant might rely on.
• The consumer Microsoft Copilot app was not installed by the user — it must be OEM‑preinstalled, image‑provisioned, or pushed by tenant tooling. User‑installed copies are intentionally exempt.
• **The Copilot app has not been launched in the last enforces this inactivity window as a conservative safety gate so active users are not surprised by an automatic removal. Because Copilot often auto‑starts on login by default, meeting this condition typically requires additional configuration (disabling auto‑start or bloctechradar.

These three checks make the policy conservative by design: it’s aimed at cleaning up provisioned but unused consumer Copilot instances (classroom images, kiosk devices, mistpoints), not at being a permanent, irrevocable ban across a mixed estate.

---

Where to find it and how to enable it​

Quick visibility check​

• Confirm the device is en Insider Dev or Beta channel and has installed Build 26220.7535 (KB5072046) or later. Feature availability can be server‑gated, so installing the update may not show the policy immediately on every device.
• Run gpedit.al AD/Intune tooling) and navigate to:
  User Configuration → Administrative Templates → Windows AI → Remove Microsoft Copilot App.
• If you can’t see it locally, deploy the ADMX/ADML templates provided in the update or map the setting via Intune device configuration profiles. Server‑side gating can delay exposure, so validate in a controlled pilot ring first.

Enabling the policy (local test workflow)​

• Open Local Group Policy Edi Navigate to User Configuration → Administrative Templates → Windows AI → Remove Microsoft Copilot App.
• Set the policy to Enabled for your test user or OU.
• Wait for the policy to apply and for the 28‑day inactivity window to be satisfied (if applicable), then verify the consumer Copilot app is uninstalled for the targeted user account.

---

Operational playbook: preparing devices so the uninst the inactivity gate and provisioning checks are strict, administrators should follow a clear operational playbook.​

Inventory and classification​

• Audit which endpoints have the consumer Copind whether those same users also have Microsoft 365 Copilot*. The policy only runs when both* are present.
• Determine how Copilot was delivered: OEM preinstall, tenant push, image provisioning, or user installation. Only provisioned/OEM/tenanigible for the Group Policy uninstall.

Enforce the 28‑day inactivity window​

• Disable Copilot auto‑start for targeted users: Task Manager → Startup → disable Copilot, or configure a logon script. Many Copilot builds enable auto‑start by default, which will reset the 28‑day timer.
• Block launch paths during the grace period: remap or disable the Copilot hardware key, disable Win+C shortcut, removeucate end users in the pilot group not to open Copilot.
• Monitor endpoint telemetry to ensure the ap 28 consecutive days before applying the uninstall policy. Use event logs or MDM metrics to validate the inactivity window.

Apply the Group Policy​

• Deploy the ADMX/ADML templates to your central poa targeted GPO for affected OUs. Alternatively, map the ADMX setting into an Intune device configuration profile for MDM‑driven environments.
• Use a staged rollout: pilot on a small set of machines, verify the uninstall happened as expected, validate no tenant workflows relying on Microsoft 365 Copilot were broken, then widen the deployment.

---

Why this is limited — and what durable removal looks like​

The RemoveMicy is intentionally conservative. Microsoft’s goals are to protect tenant‑managed Copilot customers from accidental breakage, respect end‑user autonomy for installs they choose to perform, and avoid surprising active users. The result is a controlled, auditable, and limited remediation path — useful, but not comprehensive.
For organizations that must ensure Copilot never runs or is reinstalled, the new policy is only one tool in a layered strategy:

• AppLocker / WDAC: Block the Copilot package family by publisher (MICROSOFT CORPORATION) and package name (MICROSOFT.COPILOT). This prevents execution and reienforcement level but requires thorough testing to avoid collateral blocks.
• Tenant provisioning controls: Ensure Microsoft 365 tenant provisioning does not push Copilot to managed devices. Align Intune application deployment and proid unwanted installs.
• Image hygiene: Remove Copilot from base images and OEM provisioning used by device teams and hardware partners to prevent repeat provisioning.
• Registry/Group Policy (TurnOffWindowsCopilot): Existing disable policies can hide UI elements and neutralize some se with blocking rules for durable enforcement.

The policy’s design implies that Microsoft expects administrators to use multiple controls — the Group Policy removes one installed consumer front end under constrained conditions, while AppLocker/WDAC, provisioning hygiene, and tenant management do the heavy lifting for durable governance.

---

Technical verification and supported removal paths​

Microsoft’s documentation already describes supported ways to remove or prevent the Copilot app, including manual uninstallation via Settings and PowerShell, and AppLocker prevention techniques. The Microsoft Learn page outlines methods to:

• Uninstall the Copilot app through Settings > Apps > Installed apps or via PowerShell commands that query and remove the Copilot package.
• Use AppLocker policies tr Copilot package family from installing or launching, recommending adding the publisher CN=MICROSOFT CORPORATION and package name MICROSOFT.COPILOT with a wildcard package version to the policy.

These supported removal and prevention techary mechanisms for both consumer and managed environments, and the RemoveMicrosoftCopients them in certain managed scenarios.

---

Practical examples and admin checklist​

Example: Classroom image cleanup​

• Inventory classroom devices and confirm consumer Copilot is provisioned by the image and that Microsoft 365 Copilot is also installed for those tenant accounts.
• Dist on test machines and monitor for 28 days without launches. crosoftCopilotApp via Group Policy targeted at the classroom OU.umer Copilot app is uninstalled from targeted user profin is possible via Store or provisioning, add AppLocker rules to block the package family.

Admin checklist (short)​

• [ ] Confirm build & channel (Dev / Beta, Build 26220.7535+).
• [ ] Inventory Copilot installs and provisioning source.
• [ ] Disable auto‑start and block launch paths for 2 RemoveMicrosoftCopilotApp in a small OU.
• [ ] Apply AppLocker/WDAC or tenant provisioning blocks for durable enforcement.

---

Risks, trade‑offs and governance considerations​

• Not a permanent block: The uninstall is one‑time and reversible; users or provisioning flows can reinstall Copilot unless additional blocking layers (AppLocker/WDAC, tenant policy) are applied. Treat the policy as a remediation step, not a final state.
• 28‑day ially costly: Because Copilot often auto‑starts, the inactivity requirement can be hard to meet without precise controls. Missing this window will prevent the uninstall from ever triggering.
• Scope limited to managed SKUs: Windows 11 Home and unmanaged consumer devices are out of scope for this Group Policy. Enterprises must still combine MDM/Intune and AD approacestates.
• Potential for tenant impact: If misapplied, removing the consumer Copilot front end could disrupt workflows that expect its presence alongside Microsoft 365 Copilot; the dual‑install guard mitigates but does not eliminate this risk. Verify tenant dependencies before mass rollout.
• Server‑side gating and rollout variance: The feature is in Insider builds and subject to server‑side gating; admins should not assume immediate, uniform availability even after installing the KB. Validate in a pilot ring.

---

What this means for privtions and end users​

The arrival of a supported uninstall option — even a constrained one — is meaningful for enterprises and education customers that requested more predictable Copilot management. It gives IT teams an auditable, Microsoft‑supported step in remediation and image hygiene. But by design, Microsoft has not given administrators a blunt force “kill switch” for Copilot across all scenarios;operational continuity for paid tenant customers with administrative control.
Organizations with strict privacy, regulatory, or data‑sovereignty constraints will still need to combine:

• Provisioning hygiene (remove from images),
• Tenant controls (avoid pushing consumer apps), and
• Execution blocks (AppLocker/WDAC)

to reach the level of assurance required for compliance. The new Group Policy simplifies one piece of that journey but does not replace robust gonal assessment and recommendations
Microsoft’s RemoveMicrosoftCopilotApp is a pragmatic, narrowly scoped response to long‑standing admin pain points. It is valuable because it isable, but it is not a cure‑all.

• Administrators should treat the policy as a tool in a layered strategy: use it to clean up provisioned, unused copies, and pair it with sioning hygiene, and tenant configuration to prevent reappearance.
• Pilot thoroughly: validate feature visibility (Insider channel + build), confirm gating conditions, and test tenant workflows that may interact with both Copilot experiences.
• Operationalize verification: automate telemetry checks to confirm the 28‑day inactivity window, and include uninstall verification in your device remediation playbooks.
• For consumer users: the quickest, supported paths remain hiding the taskbar Copilot button, uninstalling via Settings when available, or using app‑level controls. Power users may rely on community tools for deeper removal, but those approaches are unsupported and carry update stability risks.

Microsoft’s measured approach reflects a tension in modern endpoint management: vendors must innovate and ship AI fises demand predictable control. The RemoveMicrosoftCopilotApp policy eases one operational friction point — especially for education and managed deployments — but it is not a blanket solution. Administrators who need Copilot entirely absent from fleet images will still need the discipline of layered controls, image hygiene, and tenant governance totcome.

---

Conclusion: the new Group Policy is an important addition to the enterprise toolkit — a supported, surgical instrument for cleaning up preinstalled Copilot instances — but achieving long‑term, fleet‑wide removal of Copilot still requires planning, additional enforcement controls, and careful testing across provisioning and tenant workflows.

---

Source: Qoo10.co.id https://www.qoo10.co.id/en/gadget/6...ndows-11-check-full-requirements-here/?amp=1]