Win11Debloat

Win11Debloat

A simple, lightweight PowerShell script that allows you to remove pre-installed apps, disable telemetry, as well as perform various other changes to declutter and customize your Windows experience. Win11Debloat works for both Windows 10 and Windows 11.

github CLI Tools Shell free
★ 45,800Stars
1,865Forks
45,800Watchers
2Views
May 2026Last Update

About Win11Debloat

A simple, lightweight PowerShell script that allows you to remove pre-installed apps, disable telemetry, as well as perform various other changes to declutter and customize your Windows experience. Win11Debloat works for both Windows 10 and Windows 11.

What you should know about Win11Debloat

Win11Debloat — A simple, lightweight PowerShell script that allows you to remove pre-installed apps, disable telemetry, as well as perform various other changes to declutter and customize your Windows experience. Win11Debloat works for both Windows 10 and Windows 11.. It is categorized under CLI Tools and primarily built with Shell. The project has gathered 45,800 stars and 1,865 forks on GitHub, indicating strong adoption among developers.

Pricing & licensing: This tool is offered free of charge , released under the MIT license. The source code is openly available on GitHub, allowing engineers to audit, contribute, or fork as needed.

Use cases & topics: Win11Debloat is associated with the following topics: automated, bloatware, bloatware-removal, cleanup, cli, debloat, debloater, interactive. Teams working in automated / bloatware / bloatware-removal spaces typically evaluate this kind of tool when scoping new architecture decisions or replacing legacy components.

Getting started: Check out the official GitHub repository for installation steps, configuration examples, and the latest release notes. Most teams hit value within the first week if the tool aligns with their existing CLI Tools stack.

Editor's note from Fanny Engriana (Founder, Wardigi Digital Agency): when evaluating tools in the CLI Tools category for our agency clients, we look at three things first — license clarity, community size, and active maintenance. Tools with explicit license terms and ongoing commits tend to remain viable across multi-year projects.

Related Tools