Discofork
Repository brief

Raphire/Win11Debloat

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T19:57:56.533Z
1mo ago

Raphire/Win11Debloat

Win11Debloat is an actively maintained PowerShell-based Windows 10/11 debloating and customization tool. It focuses on removing pre-installed apps, disabling telemetry, and trimming intrusive UI elements, with both interactive and command-line usage. The repo looks fork-worthy if you want a practical Windows cleanup utility with a large user base, ongoing feature work, and a modular script/config structure.

GitHub
Loading tags...
Stars42,988
Forks1,708
Default branchmaster
Last pushed2026-03-28T23:25:13Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer this fork if the main priority is Chinese localization and cleaner Chinese text handling. Prefer upstream if you want the newest app-removal features and recent UI/CLI improvements first.

Prefer this fork if you want Chinese documentation and a near-upstream Win11Debloat experience. Prefer upstream if you care about the latest features, fixes, and the broadest maintenance coverage.

Prefer upstream unless you specifically want this fork’s older, opinionated defaults and do not need recent features or compatibility work. This fork looks best for users who value a frozen cleanup preset over an actively maintained debloating tool.

Choose this fork if language accessibility matters more than staying current with upstream. Choose upstream if you want the latest debloating features, fixes, and compatibility work.

Choose this fork only if its extra cleanup and Sysprep-oriented behavior matter more than staying current with upstream. For most adopters, upstream looks safer and more complete; this fork is mainly for users who want a more customized but aging variant.

Choose this fork only if you specifically want an unchanged Win11Debloat copy. If you want the newest fixes, settings workflow improvements, or UI refinements, upstream is the better choice.

Prefer upstream unless you specifically want a frozen base for your own customization. This fork adds no visible capability and is materially behind current upstream work.

Prefer upstream unless you specifically need a frozen 2025 snapshot; this fork adds no clear capabilities and is substantially behind on active maintenance.

Prefer upstream unless you specifically need this exact fork snapshot; it adds no visible capabilities and is behind on upstream maintenance.

Choose this fork only if you specifically want its extra removal and Sysprep-oriented behavior. For most adopters, the upstream project looks safer because it is actively maintained and materially ahead on features and fixes.