Win11Debloat is a PowerShell-based Windows 10/11 debloating and configuration utility. It provides both a WPF graphical interface and a command-line interface, allowing users to remove pre-installed bloatware, disable telemetry and AI features, customize the taskbar, Start menu, File Explorer, and apply numerous registry tweaks. The tool is data-driven: feature definitions, app catalogs, and localization strings are stored in JSON files, while registry modifications are applied via `.reg` files. It supports undo operations, registry backup/restore, system restore points, and multi-user or Sysprep deployment scenarios. The architecture is modular, with dot-sourced PowerShell scripts organized into functional directories (Features, Helpers, GUI, AppRemoval, FileIO, Threading) and a comprehensive Pester test suite. External dependencies include PowerShell 5.1, winget, and standard Windows command-line tools. The codebase demonstrates high craftsmanship with reusable patterns for registry file parsing, non-blocking execution, user profile resolution, and localization.
This repository provides a cross-platform desktop application (GUI and CLI) for debloating Android devices by uninstalling or disabling unwanted system packages. It is built in Rust using the Iced GUI framework for the interface and a shared core library (`uad-core`) that abstracts ADB communication, package list management, backup/restore, and self-update logic. The tool leverages a community-maintained package classification database (embedded JSON) that categorizes packages by vendor (AOSP, Google, OEM, etc.) and removal safety (Recommended, Advanced, Expert, Unsafe). The architecture is modular: `uad-core` handles all ADB operations and data logic, `uad-cli` provides a command-line interface with subcommands for device management, package list filtering, and actions, and `uad-gui` offers a modern graphical interface with search, filter, bulk selection, and settings for cross-user and fallback modes. The codebase is well-organized with clear separation of concerns, custom theming, and a generic modal overlay widget. It demonstrates solid engineering practices for a desktop tool, though some components (like the embedded large JSON and complex fallback logic) introduce maintenance complexity.