RemoveWindowsAI
RepositoryFreeForce Remove Copilot, Recall and More in Windows 11
Capabilities15 decomposed
privilege-escalated appx package removal with trustedinstaller bypass
Medium confidenceRemoves Windows AppX packages marked as NonRemovable by leveraging privilege escalation to TrustedInstaller context via the Run-Trusted function, which spawns a secondary PowerShell process with system-level permissions. This bypasses Windows Package Manager restrictions that normally prevent removal of built-in packages like Copilot and Recall. The implementation uses SYSTEM token impersonation to execute removal commands that would otherwise fail with access denied errors.
Uses Run-Trusted function to spawn secondary PowerShell process with SYSTEM token impersonation, enabling removal of NonRemovable packages that standard Windows APIs reject. This is more direct than registry-only approaches and handles the full package lifecycle including manifest cleanup.
More reliable than manual registry deletion because it removes packages through proper Windows servicing APIs rather than orphaning package metadata, reducing reinstallation risk.
component-based servicing (cbs) package manipulation with hidden component targeting
Medium confidenceIdentifies and removes hidden CBS packages that Windows Update uses to reinstall AI features by querying the Component-Based Servicing database and targeting specific component manifests. The implementation enumerates CBS packages via WMI or registry inspection, identifies AI-related components by manifest analysis, and removes them using DISM or direct CBS API calls. This prevents Windows Update from automatically restoring removed AppX packages during system updates.
Targets hidden CBS packages that exist in the Windows servicing database separately from AppX packages, using manifest-based component identification to prevent Windows Update from re-provisioning removed AI features. Most removal tools only handle AppX layer and miss the CBS persistence mechanism.
More comprehensive than AppX-only removal because it addresses the root cause of AI feature reinstallation — the CBS packages that Windows Update uses to restore components. Prevents the common scenario where Copilot returns after monthly updates.
execution mode selection with dry-run, removal, force, backup, and revert options
Medium confidenceProvides multiple execution modes that control how operations are applied: dry-run (preview without changes), removal (standard execution with safety checks), force (bypass safety checks), backup (create state snapshot before removal), and revert (restore from backup). The implementation uses a mode parameter to control operation behavior, with each mode having different safety guardrails and logging requirements. This enables users to choose the appropriate risk/safety tradeoff for their use case.
Implements five distinct execution modes (dry-run, removal, force, backup, revert) with mode-specific safety guardrails and logging. Force mode allows bypassing safety checks when needed, while backup/revert modes provide recovery capability.
More flexible than single-mode tools because it supports both safe testing (dry-run) and aggressive removal (force) with backup/restore for recovery. Enables users to choose appropriate risk level for their situation.
detailed operation logging and troubleshooting output
Medium confidenceGenerates comprehensive logs of all removal operations including timestamps, operation names, success/failure status, and error details when -EnableLogging flag is used. The implementation writes to log files in addition to console output, capturing both successful operations and failures with full error context. This enables troubleshooting of failed operations and provides audit trail of what was executed and when.
Implements optional detailed logging via -EnableLogging flag that captures operation timestamps, success/failure status, and error context. Logs are written to files in addition to console output for persistent audit trail.
More diagnostic-friendly than silent execution because it provides detailed logs for troubleshooting. Enables users to understand exactly what failed and why, rather than just seeing success/failure status.
windows service disablement for ai-related background services
Medium confidenceDisables Windows services associated with AI features by modifying service startup type to Disabled and stopping running service instances. The implementation enumerates Windows services, identifies AI-related services by name and description matching, and uses sc.exe or PowerShell Service cmdlets to disable them. This prevents AI services from starting automatically on system boot while allowing other services to function normally.
Identifies and disables AI-related Windows services by name and description matching, using sc.exe or PowerShell Service cmdlets to set startup type to Disabled. More targeted than disabling all services.
More reversible than service removal because disabled services can be re-enabled without reinstalling packages. Allows fine-grained control over which services are disabled.
settings app visibility hiding for ai feature ui elements
Medium confidenceHides AI feature UI elements from the Windows Settings app by modifying registry keys that control visibility of Copilot, Recall, and image generation settings pages. The implementation modifies HKCU registry keys that control Settings app page visibility, preventing users from accessing AI feature configuration options through the GUI. This is a UI-level hiding mechanism that does not remove packages but prevents user access to settings.
Modifies HKCU registry keys that control Settings app page visibility for AI features, hiding Copilot and Recall configuration options from the GUI. This is UI-level hiding rather than feature removal.
Less disruptive than package removal because it only hides UI elements while allowing packages to remain installed. Useful for organizations wanting to discourage AI feature use without breaking compatibility.
notepad rewrite feature disablement via registry and policy modification
Medium confidenceDisables the AI-powered Rewrite feature in Notepad by modifying registry keys and Group Policy settings that control Rewrite availability. The implementation targets registry keys that enable/disable the Rewrite button and policy settings that control AI feature availability in Notepad. This prevents users from accessing the Rewrite feature while keeping Notepad functional.
Targets Notepad-specific registry keys and policies that control the Rewrite feature, disabling AI text rewriting while keeping Notepad functional. Application-specific approach rather than system-wide AI removal.
More targeted than system-wide AI removal because it only affects Notepad Rewrite feature. Allows users to keep Notepad while disabling specific AI functionality.
registry and group policy modification for ai feature disablement
Medium confidenceDisables AI features by modifying Windows registry keys and Group Policy settings that control Copilot availability, voice effects, DLL contracts, and AI service activation. The implementation writes to HKLM and HKCU registry hives to set policies like DisableCopilot, modifies IntegratedServicesRegionPolicySet.json to restrict regional AI availability, and disables related Windows services. This approach disables features at the OS level without removing packages, allowing for reversible changes.
Modifies IntegratedServicesRegionPolicySet.json in addition to standard registry keys, targeting the policy file that controls regional AI feature availability. Combines HKLM/HKCU registry writes with service disablement for multi-layer policy enforcement.
More reversible than package removal and allows granular control over which AI features are disabled. Maintains Windows Update compatibility while still preventing AI feature activation, useful for organizations that cannot afford package removal risks.
scheduled task enumeration and removal for ai background processes
Medium confidenceIdentifies and removes Windows scheduled tasks associated with AI features (Copilot, Recall, image generation) by enumerating the Task Scheduler database and targeting tasks in Microsoft\Windows\AI, Microsoft\Windows\Recall, and related folders. The implementation queries task metadata to confirm AI association, then removes tasks using Task Scheduler APIs or PowerShell cmdlets. This prevents background AI processes from running even if packages remain installed.
Enumerates Task Scheduler database to identify AI-related tasks by folder path and metadata, then removes them via PowerShell Task Scheduler cmdlets. Targets specific task folders (Microsoft\Windows\AI, Microsoft\Windows\Recall) rather than generic task removal.
More targeted than disabling services because it removes only AI-specific tasks while preserving legitimate Windows maintenance tasks. Allows fine-grained control over which background processes are disabled.
windows update prevention through deployment package injection
Medium confidencePrevents Windows Update from reinstalling removed AI packages by injecting a custom deployment package into the Windows servicing stack that marks AI components as permanently removed. The implementation creates or modifies deployment package manifests that Windows Update consults during feature provisioning, effectively blocking the restoration of Copilot, Recall, and related packages. This uses the Windows Servicing Integration mechanism to persist removal decisions across updates.
Injects custom deployment packages into the Windows servicing stack to mark AI components as permanently removed, leveraging Windows Servicing Integration to persist removal decisions. This is more robust than registry-only approaches because it operates at the servicing layer that Windows Update consults.
More durable than registry policies because deployment packages are consulted by Windows Update itself during feature provisioning, ensuring removal persists across all update types. Registry policies can be overridden by updates, but servicing packages are part of the update mechanism itself.
file system cleanup for ai component binaries and libraries
Medium confidenceRemoves AI-related binary files, libraries, and configuration files from the Windows file system after AppX package removal, targeting directories like Program Files, System32, and AppData that contain Copilot, Recall, and image generation tool binaries. The implementation enumerates known AI component file paths, verifies they are not in use by other processes, and deletes them with appropriate privilege escalation. This ensures complete removal of AI executables and prevents orphaned files from consuming disk space or being exploited.
Targets specific AI component file paths in System32, Program Files, and AppData after AppX removal, using TrustedInstaller context to delete system-protected files. Includes process locking detection to prevent deletion of in-use files.
More thorough than AppX removal alone because it cleans up orphaned binaries and libraries that package removal may leave behind. Ensures no executable AI components remain on disk.
interactive ui-driven operation selection and dry-run preview
Medium confidenceProvides a PowerShell-based interactive menu interface that allows users to select individual removal operations (DisableRegKeys, RemoveAppxPackages, RemoveCBSPackages, etc.) before execution, with dry-run mode to preview changes without applying them. The implementation renders a menu using Write-Host and Read-Host, maps user selections to operation functions, and executes with -WhatIf equivalent behavior in dry-run mode. This enables safe exploration of removal options and verification of impact before committing changes.
Implements a PowerShell-native interactive menu that maps user selections to specific removal operations and provides dry-run preview without requiring external UI frameworks. Supports granular operation selection rather than all-or-nothing removal.
More user-friendly than command-line-only tools because it provides visual operation selection and dry-run preview. Safer for first-time users because changes can be previewed before application.
backup and restore functionality for removal reversibility
Medium confidenceCreates backup snapshots of system state before removal operations (registry keys, AppX packages, CBS packages, scheduled tasks) and provides restore functionality to revert changes. The implementation exports registry hives, captures AppX package manifests, and logs operation details to a backup directory, then provides a restore mode that reapplies backed-up state. This enables users to undo removal operations if they cause system issues or if AI features are needed again.
Implements multi-component backup covering registry keys, AppX packages, CBS packages, and scheduled tasks, with restore mode that reapplies backed-up state. Backup format includes metadata about what was removed and when, enabling audit trails.
More comprehensive than system restore points because it specifically captures AI removal state and provides targeted restore rather than full system rollback. Allows reverting only the removal operations without undoing other system changes.
non-interactive command-line execution with granular operation specification
Medium confidenceEnables automated, scriptable execution of removal operations via PowerShell command-line parameters (-Options, -AllOptions, -nonInteractive) without requiring user interaction or UI navigation. The implementation parses parameter arrays to identify which operations to execute, validates prerequisites, and runs operations in sequence with logging. This enables integration into deployment automation, CI/CD pipelines, and fleet management systems.
Supports both granular operation selection via -Options array and all-operations execution via -AllOptions flag, with automatic parameter validation and prerequisite checking. Enables integration into PowerShell-based deployment automation without requiring UI interaction.
More flexible than GUI-only tools because it supports both interactive and non-interactive modes, enabling use in automated deployments. Parameter-driven approach allows fine-grained control over which operations execute.
automatic privilege escalation and trustedinstaller context switching
Medium confidenceAutomatically detects if the script is running with administrator privileges and self-elevates if needed using UAC prompts, then switches to TrustedInstaller context for operations requiring system-level file and registry access. The implementation uses the Run-Trusted function to spawn a secondary PowerShell process with SYSTEM token impersonation, enabling operations that standard administrator context cannot perform. This abstracts privilege escalation complexity from users while maintaining security boundaries.
Implements Run-Trusted function that spawns secondary PowerShell process with SYSTEM token impersonation, enabling access to TrustedInstaller-protected resources without requiring manual elevation. Automatically detects privilege level and escalates if needed.
More user-friendly than manual elevation because it automatically escalates privileges and abstracts TrustedInstaller context switching. Safer than running entire script as SYSTEM because only specific operations use elevated context.
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with RemoveWindowsAI, ranked by overlap. Discovered automatically through the match graph.
StabilityMatrix
Multi-Platform Package Manager for Stable Diffusion
Icecream Apps Ltd
Versatile suite of user-friendly digital tools for everyday...
OpenAgentsControl
AI agent framework for plan-first development workflows with approval-based execution. Multi-language support (TypeScript, Python, Go, Rust) with automatic testing, code review, and validation built for OpenCode
lamda
The most powerful Android RPA agent framework, next generation mobile automation.
mcpb
Desktop Extensions: One-click local MCP server installation in desktop apps
Pixel Agents
Pixel art office where your Claude Code agents come to life as animated characters
Best For
- ✓Windows 11 administrators removing AI features from enterprise deployments
- ✓Privacy-focused users wanting complete Copilot/Recall removal
- ✓System administrators automating AI component stripping across fleets
- ✓System administrators deploying persistent AI removal across managed Windows 11 fleets
- ✓Users wanting permanent removal that survives Windows Update cycles
- ✓Organizations with strict privacy policies requiring complete AI feature elimination
- ✓Users wanting to test removal before committing
- ✓System administrators managing removal across multiple systems with different risk tolerances
Known Limitations
- ⚠Requires administrator privileges and cannot run in restricted execution contexts
- ⚠Windows Update may reinstall removed packages unless prevention mechanisms are also applied
- ⚠Only works on Windows 11 build 25H2 or later with AI features present
- ⚠Removal is permanent without backup/restore functionality — requires separate backup operation before execution
- ⚠CBS manipulation can affect Windows Update stability if incorrect packages are targeted
- ⚠Requires elevated privileges and may trigger Windows Defender alerts on some systems
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
Repository Details
Last commit: Apr 15, 2026
About
Force Remove Copilot, Recall and More in Windows 11
Categories
Alternatives to RemoveWindowsAI
Are you the builder of RemoveWindowsAI?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →