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.
SpanFinder is a fully-featured Windows file explorer replacement built with WinUI 3 and .NET 8, implementing the macOS Finder Miller Columns paradigm. The application supports multiple view modes (Miller Columns, Details, List, Icons), multi-tab with tear-off, split pane, Quick Look preview, batch rename, archive handling (ZIP, RAR, 7z via native OtterZip engine), remote file access (FTP/SFTP/SMB), Git integration, cloud sync badges, and a file shelf for drag-and-drop staging. The architecture follows MVVM with dependency injection, extensive use of Win32 P/Invoke and COM interop for shell integration, and a separate thumbnail worker process for crash isolation. The codebase is well-organized into Services, Models, ViewModels, and Helpers, with over 150 unit tests and 40+ UI automation tests. However, it exhibits some mixed abstraction layers and a few large partial classes (MainWindow, MainViewModel), and many comments reference specific bug fixes, indicating ongoing refinement. The repository is actively maintained with recent commits, a single open issue, and regular versioned releases (v2.0.7).
FastCopy (published as RoboCopyEx, v1.2.1.0) is a Windows desktop utility that replaces Explorer's default copy/move/paste/delete with a robocopy-backed engine. In production it is three cooperating native components: a WinUI 3 (C++/WinRT, Windows App SDK 1.8) application that renders copy progress, a speed graph, pause/resume, duplicate-file conflict resolution and delete confirmations; a COM shell-extension DLL that adds copy/move/paste/delete items to both the new Windows 11 and legacy Explorer context menus; and a global keyboard-hook executable that intercepts Ctrl+V inside Explorer to route pastes through FastCopy. A fastcopy:// URI handler (CommandLineHandler) is the transport by which components pass operations to the main app. The solution is an MSIX package of six projects: FastCopy (UI), FastCopyShellExtension (Explorer COM DLL), FastCopyKeyboardHook (global hook EXE), RobocopyInjection (DLL injected into robocopy.exe to expose per-file progress), UnitTest, and SpeedTest — a TUI benchmark that empirically compares robocopy, xcopy, std::filesystem, IFileOperation and SHFileOperation. The central data flow: RobocopyViewModel builds robocopy arguments; RobocopyProcess launches robocopy.exe suspended inside a JobObject, injects a DLL to force English locale output, then streams the child's stdout through a regex-driven template parser (OutputRegexParseBase) while ProcessIOUpdater samples GetProcessIoCounters/GetSystemTimes to animate the Win2D speed graph, taskbar progress and Windows toasts. Settings are persisted via a WinRT IPropertySet-backed Settings class and MVVM runtime classes declared in IDL. Engineering quality is mixed and should be read from the code rather than the README's speed claims. The repo knowingly ships a crash after the window is closed; RobocopyInjectDll.h and CreateSuspend.h contain null-byte encoding corruption; numerous features are disabled ('Under development!') or commented out; and the app depends on a third-party WinUI3Package (essential:) control library plus dual vcpkg/NuGet dependency chains, making rebuilds fragile outside the author's machine. The DLL-injection and global-hook design is also the likely reason the Store rejected the package, per drama.md. The last commit (2026-09-19) indicates the project is still actively developed. Despite containing a benchmark harness and careful README performance tables, this is an application, not a data/research repository: there are no datasets, notebooks, or pipelines, and the SpeedTest project is an empirically driven engineering tool, not analysis. Its most durable artifacts are the independently extractable OS-interop helpers and parsing templates described below.