Microsoft Removes Copilot From Core Windows 11 Apps

Microsoft has begun removing prominent Copilot integrations from several built-in Windows 11 apps, starting with Notepad and the Snipping Tool, and intends similar reductions in Photos and Widgets. The action follows an internal shift announced by Pavan Davuluri, President of Windows & Devices, who said Microsoft will be "more intentional" about AI placement and is "reducing unnecessary Copilot entry points."

Since Copilot’s introduction, Microsoft embedded the assistant into many OS-level surfaces to drive AI ubiquity and usage telemetry. That strategy raised UX, performance and user-consent complaints: users objected to visual clutter, default-on behaviors, and unpredictable AI suggestions inside lightweight utilities. The rollback does not remove Copilot from Windows wholesale; it narrows where AI entry points protrude into day-to-day workflows, focusing on scenarios that justify the overhead of context, latency and potential privacy implications.

Lifehacker cites Davuluri’s framing that Microsoft will "integrate AI where it's most meaningful, with craft and focus," explicitly naming Snipping Tool, Photos, Widgets and Notepad as initial targets for reduced Copilot presence. The Verge likewise summarized Microsoft’s statement about cutting "unnecessary" Copilot buttons. How-To Geek frames this as part of a broader responsiveness push: Microsoft is adjusting Windows 11 based on customer feedback and usability issues, not only changing Copilot placements but also addressing other resource and reliability concerns.

For product teams and ML engineers, this is a case study in deployment ergonomics: embedding models pervasively can amplify failure modes (UX friction, resource bloat, privacy questions) even when models technically work. The rollback emphasizes that model placement and default behavior matter as much as model capability. Engineers should expect tighter product-privacy tradeoffs, more conservative gating of system-level AI, and higher scrutiny of telemetry and opt-in defaults going forward.

Monitor Microsoft’s follow-through in Insider builds to see whether these changes remove UI affordances, disable background model calls, or simply hide buttons while continuing telemetry. Also watch developer guidance and SDKs: will Microsoft change APIs to make system-level AI opt-in for OEMs and ISVs?