{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"github-zoicware--removewindowsai","slug":"zoicware--removewindowsai","name":"RemoveWindowsAI","type":"cli","url":"https://github.com/zoicware/RemoveWindowsAI","page_url":"https://unfragile.ai/zoicware--removewindowsai","categories":["automation","code-editors"],"tags":["ai","bloatware","bloatware-removal","copilot","debloat","generative-ai","image-creator","optimizer","powershell","privacy","recall","rewrite","security","windows"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"github-zoicware--removewindowsai__cap_0","uri":"capability://automation.workflow.privilege.escalated.appx.package.removal.with.trustedinstaller.bypass","name":"privilege-escalated appx package removal with trustedinstaller bypass","description":"Removes 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.","intents":["Remove Copilot and Recall AppX packages that Windows marks as non-removable","Uninstall AI-related packages without triggering Windows Update reinstallation","Achieve system-level package removal without manual registry hacking"],"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"],"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"],"requires":["Windows 11 (build 25H2 or later)","Administrator privileges (script auto-elevates)","PowerShell 5.1 or PowerShell 7","TrustedInstaller service running and accessible"],"input_types":["Package names (string array)","Execution mode flag (dry-run, removal, force)"],"output_types":["Removal status per package (success/failure)","Operation log entries","Backup manifest for restore operations"],"categories":["automation-workflow","system-administration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_1","uri":"capability://automation.workflow.component.based.servicing.cbs.package.manipulation.with.hidden.component.targeting","name":"component-based servicing (cbs) package manipulation with hidden component targeting","description":"Identifies 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.","intents":["Prevent Windows Update from reinstalling Copilot and Recall after removal","Remove hidden CBS packages that AppX removal alone cannot address","Block automatic restoration of AI features during monthly Windows updates"],"best_for":["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"],"limitations":["CBS manipulation can affect Windows Update stability if incorrect packages are targeted","Requires elevated privileges and may trigger Windows Defender alerts on some systems","CBS database is locked during Windows Update operations — timing conflicts possible","Removal is irreversible without full Windows reinstallation in some cases"],"requires":["Windows 11 (build 25H2 or later)","Administrator privileges","DISM tool available (included in Windows)","Component-Based Servicing database accessible"],"input_types":["CBS package identifiers (string)","Component manifest paths (string)"],"output_types":["Removed package list (structured)","CBS database modification log","Windows Update prevention status"],"categories":["automation-workflow","system-administration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_10","uri":"capability://automation.workflow.execution.mode.selection.with.dry.run.removal.force.backup.and.revert.options","name":"execution mode selection with dry-run, removal, force, backup, and revert options","description":"Provides 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.","intents":["Preview removal operations before applying them","Execute removal with standard safety checks","Force removal when safety checks are too restrictive","Create backups before removal for recovery","Revert removal operations to previous state"],"best_for":["Users wanting to test removal before committing","System administrators managing removal across multiple systems with different risk tolerances","Organizations requiring backup/restore capabilities for compliance"],"limitations":["Dry-run mode may not accurately predict all side effects of removal","Force mode bypasses safety checks and can cause system instability if misused","Revert mode requires valid backup — cannot recover if backup is corrupted or deleted","Mode selection adds complexity — users must understand implications of each mode"],"requires":["PowerShell 5.1 or later","Administrator privileges for removal, force, and revert modes","Sufficient disk space for backup mode (500MB-2GB)","Valid backup for revert mode"],"input_types":["Execution mode selection (string: 'dry-run', 'removal', 'force', 'backup', 'revert')","Backup identifier for revert mode (string)"],"output_types":["Mode-specific operation log (text)","Dry-run preview output (text)","Backup manifest (JSON/XML for backup mode)","Revert status log (text for revert mode)"],"categories":["automation-workflow","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_11","uri":"capability://automation.workflow.detailed.operation.logging.and.troubleshooting.output","name":"detailed operation logging and troubleshooting output","description":"Generates 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.","intents":["Troubleshoot failed removal operations with detailed error messages","Maintain audit trail of removal operations for compliance","Debug system issues caused by removal operations"],"best_for":["System administrators troubleshooting removal failures","Organizations requiring audit trails of system modifications","Users experiencing issues after removal and needing diagnostic information"],"limitations":["Logging adds overhead and increases script execution time","Log files may contain sensitive information (registry keys, file paths) requiring secure storage","Very verbose logging can generate large log files (10MB+ for full system removal)","Log file rotation and cleanup must be managed manually"],"requires":["Write access to log directory (typically %TEMP% or script directory)","Sufficient disk space for log files","-EnableLogging flag to activate logging"],"input_types":["-EnableLogging flag (boolean)","Log directory path (string, optional)"],"output_types":["Log file (text format with timestamps)","Console output (real-time operation status)","Error details with full stack traces (if applicable)"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_12","uri":"capability://automation.workflow.windows.service.disablement.for.ai.related.background.services","name":"windows service disablement for ai-related background services","description":"Disables 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.","intents":["Disable AI-related Windows services from starting automatically","Stop running AI service instances without removing packages","Reduce system resource consumption from AI background services"],"best_for":["Users wanting to disable AI services without full package removal","System administrators reducing AI-related system load","Organizations wanting reversible AI feature disablement"],"limitations":["Disabled services may be re-enabled by Windows Update or feature updates","Some AI features may not use Windows services and will continue running","Service disablement does not prevent manual or on-demand AI feature invocation","Stopping services may cause dependent processes to fail if not properly handled"],"requires":["Administrator privileges","Windows 11 (build 25H2 or later)","Service Control Manager (sc.exe) or PowerShell Service cmdlets available"],"input_types":["Service names (string array)","Service name patterns (regex or wildcard)"],"output_types":["Disabled service list (structured)","Service status before/after disablement","Dependent service impact report"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_13","uri":"capability://automation.workflow.settings.app.visibility.hiding.for.ai.feature.ui.elements","name":"settings app visibility hiding for ai feature ui elements","description":"Hides 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.","intents":["Hide Copilot and Recall settings from Windows Settings app","Prevent users from re-enabling AI features through Settings UI","Reduce visibility of AI features in system settings"],"best_for":["Organizations wanting to hide AI features from users without full removal","Users preferring UI-level hiding over package removal","Enterprise deployments with managed Settings app policies"],"limitations":["Hiding is UI-level only — does not prevent AI features from running if packages are installed","Registry modifications can be reverted by users with registry editor access","Settings app may cache visibility settings and require restart to apply changes","Does not prevent programmatic access to AI features via APIs"],"requires":["Administrator privileges (for HKCU modifications)","Windows 11 (build 25H2 or later)","Registry editor access"],"input_types":["Registry key paths for Settings app visibility (string array)"],"output_types":["Modified registry keys list (structured)","Settings app restart requirement status"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_14","uri":"capability://automation.workflow.notepad.rewrite.feature.disablement.via.registry.and.policy.modification","name":"notepad rewrite feature disablement via registry and policy modification","description":"Disables 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.","intents":["Disable AI Rewrite feature in Notepad without removing Notepad","Prevent users from using AI text rewriting in Notepad","Maintain Notepad functionality while removing AI features"],"best_for":["Users wanting to disable Notepad Rewrite without full AI removal","Organizations restricting AI feature use in built-in applications","Enterprise deployments with Notepad policy restrictions"],"limitations":["Rewrite feature disablement only affects Notepad — does not remove AI from other applications","Registry modifications can be reverted by users with registry editor access","Notepad updates may re-enable Rewrite feature if registry keys are not persistent","Does not prevent users from using alternative text editors with AI features"],"requires":["Administrator privileges","Windows 11 (build 25H2 or later with Notepad Rewrite feature)","Registry editor access"],"input_types":["Registry key paths for Notepad Rewrite settings (string array)"],"output_types":["Modified registry keys list (structured)","Notepad restart requirement status"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_2","uri":"capability://automation.workflow.registry.and.group.policy.modification.for.ai.feature.disablement","name":"registry and group policy modification for ai feature disablement","description":"Disables 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.","intents":["Disable Copilot and AI features without full package removal","Apply Group Policy restrictions to prevent AI feature re-enablement","Disable voice effects and AI-related DLL contracts at the registry level"],"best_for":["Enterprise administrators wanting reversible AI feature disablement","Users preferring policy-based disabling over package removal","Organizations needing to maintain Windows Update compatibility while disabling AI"],"limitations":["Registry modifications can be reverted by Windows Update or system resets in some cases","Group Policy changes only apply to domain-joined machines in enterprise environments","Some AI features may bypass registry policies through alternative activation paths","Requires careful registry key targeting — incorrect modifications can cause system instability"],"requires":["Administrator privileges","Registry editor access (regedit or PowerShell registry provider)","Windows 11 (build 25H2 or later)","Group Policy Editor (gpedit.msc) for enterprise deployments"],"input_types":["Registry key paths (string)","Policy values (DWORD, string)","JSON policy files (IntegratedServicesRegionPolicySet.json)"],"output_types":["Registry modification log","Policy application status","Backup of original registry values for restore"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_3","uri":"capability://automation.workflow.scheduled.task.enumeration.and.removal.for.ai.background.processes","name":"scheduled task enumeration and removal for ai background processes","description":"Identifies 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.","intents":["Stop AI background processes and telemetry tasks from executing","Remove Recall indexing and Copilot update tasks","Prevent AI features from running on schedule even if packages are present"],"best_for":["Users wanting to disable AI background activity without full package removal","System administrators reducing AI-related system load and telemetry","Privacy-focused users preventing scheduled AI data collection"],"limitations":["Removed tasks may be recreated by Windows Update or feature updates","Some AI processes may not use scheduled tasks and will continue running","Task removal does not prevent manual or on-demand AI feature invocation","Requires enumeration of all tasks to identify AI-related ones — incomplete task lists may miss some processes"],"requires":["Administrator privileges","Task Scheduler service running","PowerShell 5.1 or later","Windows 11 (build 25H2 or later)"],"input_types":["Task folder paths (string array)","Task name patterns (regex or wildcard)"],"output_types":["Removed task list (structured)","Task metadata backup for restore","Execution status per task"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_4","uri":"capability://automation.workflow.windows.update.prevention.through.deployment.package.injection","name":"windows update prevention through deployment package injection","description":"Prevents 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.","intents":["Prevent Windows Update from automatically restoring Copilot and Recall","Ensure removed AI packages stay removed across monthly and feature updates","Block Windows from re-provisioning AI components during system maintenance"],"best_for":["Users wanting permanent AI removal that survives all Windows Update cycles","System administrators deploying AI removal across fleets with automatic updates enabled","Organizations requiring compliance with strict AI feature removal policies"],"limitations":["Deployment package injection requires deep knowledge of Windows servicing architecture","Major Windows feature updates (e.g., 25H2 to 26H1) may override deployment packages","Incorrect package manifests can cause Windows Update failures or system instability","Requires access to Windows servicing directories that may be protected by TrustedInstaller"],"requires":["Administrator privileges and TrustedInstaller context for some operations","Windows 11 (build 25H2 or later)","Understanding of Windows deployment package format and manifest structure","Access to Windows\\Servicing\\Packages directory"],"input_types":["Deployment package manifests (XML)","Component removal lists (string array)","Package identity strings (string)"],"output_types":["Deployment package installation status","Windows Update prevention verification log","Package manifest backup for rollback"],"categories":["automation-workflow","system-administration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_5","uri":"capability://automation.workflow.file.system.cleanup.for.ai.component.binaries.and.libraries","name":"file system cleanup for ai component binaries and libraries","description":"Removes 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.","intents":["Remove Copilot and Recall binary files and libraries from disk","Clean up orphaned AI component files after package removal","Reclaim disk space used by AI features and ensure no executable remnants remain"],"best_for":["Users wanting complete removal of AI feature files from disk","System administrators cleaning up after AppX package removal","Organizations with strict data retention policies requiring complete file deletion"],"limitations":["File deletion requires TrustedInstaller context for system-protected directories","Files in use by running processes cannot be deleted — requires process termination","Hardlinks or file references may prevent complete cleanup","Deleted files may be recoverable with disk forensics tools — does not use secure deletion"],"requires":["Administrator privileges and TrustedInstaller context","Windows 11 (build 25H2 or later)","Target files not locked by running processes","Write access to System32, Program Files, and AppData directories"],"input_types":["File paths (string array)","Directory paths for recursive deletion (string array)","File pattern wildcards (string)"],"output_types":["Deleted file list (structured)","Deletion status per file (success/failure/in-use)","Disk space reclaimed (bytes)"],"categories":["automation-workflow","system-administration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_6","uri":"capability://automation.workflow.interactive.ui.driven.operation.selection.and.dry.run.preview","name":"interactive ui-driven operation selection and dry-run preview","description":"Provides 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.","intents":["Preview removal operations before applying them to the system","Select specific AI features to remove without affecting others","Understand what each removal operation will do before execution"],"best_for":["First-time users unfamiliar with AI removal procedures","System administrators testing removal on pilot systems before fleet deployment","Users wanting granular control over which AI features are removed"],"limitations":["Interactive UI requires manual user input — not suitable for automated deployments","Dry-run mode may not accurately predict all side effects of removal operations","Console-based UI is limited to text output — no graphical visualization of changes","Menu navigation is sequential — no ability to batch-select multiple operations at once"],"requires":["PowerShell 5.1 or later","Interactive console session (not suitable for remote execution without input redirection)","Administrator privileges for actual removal (not needed for dry-run preview)"],"input_types":["User menu selections (numeric or string)","Execution mode selection (dry-run, removal, force, backup, revert)"],"output_types":["Operation preview output (text)","Dry-run change log (text)","User confirmation prompts (interactive)"],"categories":["automation-workflow","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_7","uri":"capability://automation.workflow.backup.and.restore.functionality.for.removal.reversibility","name":"backup and restore functionality for removal reversibility","description":"Creates 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.","intents":["Safely test AI removal with ability to revert if issues occur","Restore AI features if removal causes system problems","Maintain audit trail of what was removed and when"],"best_for":["Users wanting reversible removal with safety net for system issues","System administrators testing removal on production systems","Organizations requiring audit trails of system modifications"],"limitations":["Backup storage requires significant disk space for full registry and package exports","Restore may not fully recover system state if Windows Update has modified components since backup","Some operations (file deletion) may not be fully reversible if files were modified after backup","Backup files themselves may be targeted by security tools or disk cleanup utilities"],"requires":["Administrator privileges","Sufficient disk space for backup (typically 500MB-2GB depending on system)","Backup directory with write access","PowerShell 5.1 or later"],"input_types":["Backup directory path (string)","Backup identifier or timestamp (string)","Components to backup (string array)"],"output_types":["Backup manifest (JSON or XML)","Registry export files (REG format)","Package manifest backups (XML)","Restore status log (text)"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_8","uri":"capability://automation.workflow.non.interactive.command.line.execution.with.granular.operation.specification","name":"non-interactive command-line execution with granular operation specification","description":"Enables 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.","intents":["Automate AI removal across multiple systems without manual intervention","Integrate removal into Windows deployment and provisioning pipelines","Execute specific removal operations via command-line for scripting and orchestration"],"best_for":["System administrators deploying AI removal across enterprise fleets","DevOps teams integrating removal into Windows image building pipelines","Organizations automating AI feature removal as part of system provisioning"],"limitations":["Non-interactive mode requires pre-validation of all parameters — no user confirmation","Error handling must be robust because there is no user to intervene on failures","Logging becomes critical for troubleshooting since there is no interactive feedback","Parameter validation errors may cause silent failures if not properly logged"],"requires":["PowerShell 5.1 or later","Administrator privileges (script auto-elevates if needed)","Windows 11 (build 25H2 or later)","Proper parameter syntax and valid operation names"],"input_types":["Operation names (string array via -Options parameter)","-AllOptions flag (boolean)","-nonInteractive flag (boolean)","-EnableLogging flag (boolean)"],"output_types":["Operation execution log (text file or console)","Exit code indicating success/failure","Structured operation results (JSON or XML if logging enabled)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-zoicware--removewindowsai__cap_9","uri":"capability://automation.workflow.automatic.privilege.escalation.and.trustedinstaller.context.switching","name":"automatic privilege escalation and trustedinstaller context switching","description":"Automatically 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.","intents":["Automatically elevate to administrator if script is run without privileges","Switch to TrustedInstaller context for system-protected file and registry operations","Enable removal of system components that standard admin context cannot access"],"best_for":["Users running the script without pre-elevated administrator privileges","System administrators wanting automated privilege escalation in deployment scripts","Operations targeting system-protected files and registry keys"],"limitations":["UAC prompts may be blocked in restricted environments or headless systems","TrustedInstaller context switching adds ~200-500ms latency per operation","Some operations may fail if TrustedInstaller service is disabled or unavailable","Privilege escalation may trigger security alerts in enterprise environments with strict UAC policies"],"requires":["Windows 11 (build 25H2 or later)","UAC enabled (for automatic elevation)","TrustedInstaller service running (for TrustedInstaller context operations)","PowerShell 5.1 or later"],"input_types":["Script execution context (implicit — detected at runtime)","Operation requiring TrustedInstaller context (implicit — determined by operation type)"],"output_types":["Elevation status (success/failure)","TrustedInstaller context switch status","Operation execution within elevated context"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":48,"verified":false,"data_access_risk":"high","permissions":["Windows 11 (build 25H2 or later)","Administrator privileges (script auto-elevates)","PowerShell 5.1 or PowerShell 7","TrustedInstaller service running and accessible","Administrator privileges","DISM tool available (included in Windows)","Component-Based Servicing database accessible","PowerShell 5.1 or later","Administrator privileges for removal, force, and revert modes","Sufficient disk space for backup mode (500MB-2GB)"],"failure_modes":["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","CBS database is locked during Windows Update operations — timing conflicts possible","Removal is irreversible without full Windows reinstallation in some cases","Dry-run mode may not accurately predict all side effects of removal","Force mode bypasses safety checks and can cause system instability if misused","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.6399717180369138,"quality":0.35,"ecosystem":0.7000000000000001,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.1,"match_graph":0.28,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:22.064Z","last_scraped_at":"2026-05-03T13:58:39.623Z","last_commit":"2026-05-01T18:07:49Z"},"community":{"stars":11516,"forks":388,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=zoicware--removewindowsai","compare_url":"https://unfragile.ai/compare?artifact=zoicware--removewindowsai"}},"signature":"KyE8DOMP8A8U23lJuAeJFJEip+So/CfiqYt0OjC3D8BiGDCbGF+yOwbEtK2h7KjfHuwHG5xZrB/o3KBMwJJdAQ==","signedAt":"2026-06-23T00:00:18.514Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/zoicware--removewindowsai","artifact":"https://unfragile.ai/zoicware--removewindowsai","verify":"https://unfragile.ai/api/v1/verify?slug=zoicware--removewindowsai","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}