Admins and users remove Microsoft Copilot features amid Copilot Vision privacy reports

Microsoft’s AI push in Windows just ran into the oldest enterprise rule in the book — if people don’t trust a feature, they remove it. That is what happened this week around Copilot Vision, the screen-aware part of Copilot, and around other Microsoft AI hooks that users say are too sticky, too hidden, or too eager to take credit. The immediate news is not one giant Microsoft announcement. It’s a cluster of reactions: a how-to guide for fully deleting Vision, a new NTLite release for stripping AI from Windows 11 25H2 images, and a VS Code fix after Copilot started showing up in commit authorship by default. (tomsguide.com) ### What is Copilot Vision, exactly? Copilot Vision is the part of Microsoft Copilot that can look at what you choose to share — an app window, a browser window, or a phone camera feed — and then talk you through what it sees. Microsoft says it is opt-in, asks for a privacy acknowledgment the first time, and does not click or type on your behalf. But the key emotional point is simpler than the pr(tomsguide.com)and a lot of them want a big off switch. (support.microsoft.com) ### Why did this flare up now? Because Vision is no longer a vague future feature. It is showing up in real Windows workflows, and people are discovering it through tutorials that frame it as something to control or remove, not just try. Tom’s Guide’s piece was basically a consumer version of the same instinct IT admins have had for months — find the setting, disable the feature, and if possible uninstall the app entirely. (tomsguide.com) ### What are admins doing differently? Admins are moving one layer deeper than toggles. NTLite’s new v2026.04.10936 release lets people remove AI components like Copilot and Windows Recall from Windows 11 25H2 installation images before deployment. That matters because preinstall removal is very different from hiding a button after setup. It means organizations can build Windows images where the (tomsguide.com) place. (ghacks.net) ### Why does preinstall removal matter so much? Because “just turn it off” is not the same as “it is gone.” IT teams care about image size, policy drift, support burden, and surprise re-enablement after updates. A feature that can be disabled by one menu but resurfaced by another update is annoying (ghacks.net) guests. (ghacks.net) ### What happened in VS Code? Microsoft also had to reverse a change in VS Code’s Git extension after developers complained that commits were getting a “Co-authored-by: Copilot” trailer by default. The backlash was not just about wording. It was about provenance and consent — developers said the edi(ghacks.net)o opt-in for the upcoming 1.119 release. (theregister.com) ### Why are these separate stories connected? Because they all hit the same nerve. Screen-aware AI, preloaded AI components, and automatic AI attribution sound like different product issues, but users read them as one pattern — AI arriving first, and clear control arriving later. Once that pattern sets in, every new feature gets interpreted through distrust. (support.microsoft.com) ### So what’s the real stakes here? This is becoming a procurement and platform-trust issue, not just a privacy debate. Microsoft says Vision is user-initiated, temporary, and not used to train models, and for some people that will be enough. But enterprises buy predictability as much as features(support.microsoft.com), Microsoft’s AI rollout starts to look less like assistance and more like overhead. (support.microsoft.com) ### Bottom line? The backlash is not really “people hate AI.” It is narrower, and more damaging than that. People hate AI they did not explicitly ask for, cannot easily remove, or cannot fully audit after the fact. Microsoft can still win this fight — but only if control stops feeling like an afterthought.