RemoveWindowsAI: One‑shot removal of all Windows 11 AI components
A PowerShell-based cleanup script designed to comprehensively remove Copilot, Recall and other AI components from Windows 11. Suited for privacy-focused power users and IT administrators, it carries significant risk, compatibility concerns and unclear licensing—use cautiously in recoverable/test environments with backups.
GitHub zoicware/RemoveWindowsAI Updated 2026-01-15 Branch main Stars 8.4K Forks 262
PowerShell Windows 11 system-debloat privacy CBS package management Appx removal

💡 Deep Analysis

3
If backup was not enabled or revert fails, how can deleted system components be recovered? What are realistic recovery paths and risks?

Core Analysis

Core Question: If backup was not enabled or revert fails, how can deleted system components be recovered and what are the realistic recovery paths and risks?

Technical Analysis

  • Preferred recovery paths:
    1. Script revert: Use -revertMode if backups were created by the script.
    2. DISM and SFC repair: Run DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow to attempt repairs from Windows Update or local sources.
    3. In-place upgrade (repair install): Use Windows installation media to perform a repair install, which typically restores system files without wiping user data.
    4. Reinstall OS: As a last resort, perform a clean install and restore user data.

  • Limitations and risks:

  • DISM/SFC depend on available repair sources; severely corrupted CBS may not be fully recoverable.
  • In-place upgrade is effective but time-consuming and may be restricted by corporate policies.
  • Reinstall is most reliable but highest cost; ensure data backups.

Practical Recommendations

  1. Stop further modifications and collect logs (script output, Event Viewer) to scope the damage.
  2. Attempt DISM + SFC first and save outputs to determine next steps.
  3. Back up user data immediately before any repair or reinstall actions.
  4. In managed environments, engage support teams or follow official repair procedures rather than ad-hoc fixes.

Important Notice: Recovery without backups significantly increases complexity and cost. Enabling -backupMode before making changes is the most effective risk reduction.

Summary: Recovery without backups is possible but likely requires DISM/SFC, a repair install, or a full reinstall. Always enable backups to avoid these high-cost recovery paths.

87.0%
How does the script remove locked AI packages in the CBS store, and what are the advantages and risks of that approach?

Core Analysis

Core Question: The script claims to remove hidden and locked AI packages from the CBS (Component-Based Servicing) store—this is more thorough than Appx-only removal but also carries higher system risk.

Technical Analysis

  • Implementation (inferred): With administrator privileges, the script likely locates package identifiers or files in the CBS store and performs file-level removal or low-level operations that bypass Appx/Store protections. The requirement for Windows PowerShell 5.1 indicates interactions with system-level commands.
  • Main Advantages:
  • Thoroughness: Can remove packages labeled as system-level or non-removable, including WindowsWorkload components.
  • Privacy/Function Disablement: Can target AI functions that are otherwise protected by the OS.
  • Main Risks:
  • System integrity risk: Altering CBS may corrupt the component database and cause errors in Windows Update, DISM, or SFC.
  • Update compatibility risk: Major updates may fail or reintroduce components because of inconsistent component states.

Practical Recommendations

  1. Only run in test environments or systems protected by snapshots; do not run directly on critical production machines.
  2. Enable backup mode and keep the backup artifacts for recovery.
  3. If issues appear, start with DISM /Online /Cleanup-Image and SFC /scannow to try to repair component/registry inconsistencies.

Important Notice: CBS-level changes are high-risk and should be done only by advanced users or admins with full backups.

Summary: CBS-level removal delivers deeper cleanup than typical scripts but introduces significant stability and update risks—execute only with proper backups and in recoverable environments.

86.0%
How reliable is the script's mechanism of installing a custom Windows Update package to prevent reinstallation, and what is its long-term effectiveness?

Core Analysis

Core Question: The script installs a custom Windows Update package to prevent reinstallation of AI packages. This is an active pinning approach, but its reliability and longevity depend on external factors.

Technical Analysis

  • Short-term effectiveness: Injecting a custom update package (likely occupying the same package identity or providing a replacement) can prevent Windows Update from restoring the original package under current update rules and package naming. It usually works for known, fixed package names and paths.
  • Long-term limitations:
  • Signing and verification: Windows Update/CBS require strict signing and metadata; Microsoft can change signing strategies or publish override packages.
  • Package identity changes: If Microsoft renames or relocates packages, the placeholder approach may fail.
  • Major upgrades: Feature updates or cumulative updates may bypass or reset these protections.
  • Maintenance burden: The solution requires ongoing maintenance to remain effective against changes.

Practical Recommendations

  1. Treat the anti-reinstall approach as a short-term mitigation, not a permanent guarantee; check for script updates and system update logs regularly.
  2. Implement monitoring to verify that pinned packages remain not reinstalled.
  3. In managed environments, prefer centralized management controls (WSUS, SCCM) and policy-level blocks rather than relying solely on local placeholder packages.

Important Notice: This mechanism is not an official supported uninstall/disable method; Microsoft updates may restore or alter behavior.

Summary: Custom update packages are useful for short-term persistence but require active maintenance and monitoring for long-term effectiveness.

84.0%

✨ Highlights

  • Comprehensive removal of Copilot, Recall and AI services
  • Supports backup mode and optional revert to improve recoverability
  • Requires administrator privileges and must run under PowerShell 5.1
  • Repository lacks a clear license and contributor/releases info; maintenance risk is high

🔧 Engineering

  • Uses a PowerShell script to disable registry keys and remove Appx and locked AI packages from the CBS store
  • Can replace modern apps with classic versions and includes task/file cleanup and settings-page hiding

⚠️ Risks

  • Forcible modifications to CBS and system packages may cause update failures or system instability
  • Missing license and active maintenance information; legal and long-term compatibility are uncertain
  • Antivirus products may false-positive the script, requiring temporary disablement or exclusions and increasing operational complexity

👥 For who?

  • Targeted at power users, system administrators, and privacy-conscious users who want to thoroughly remove AI components
  • Recommended for users with admin rights and PowerShell experience; test first in a VM or backed-up environment