Win11Debloat: a PowerShell script for stripping Windows 10 and 11 down

What Win11Debloat actually removes and disables

The problem Win11Debloat addresses is the gap between a fresh Windows install and a usable one. A new Windows 10 or 11 machine ships with preinstalled apps, telemetry and diagnostic data collection, suggested content, ads in Edge, the lock screen and the Start menu, Copilot, Recall and Click to Do, and a set of default behaviours such as Storage Sense, fast start-up and BitLocker automatic device encryption. Turning all of that off by hand means walking through Settings, Group Policy and the Microsoft Store, one toggle at a time.

The README frames the audience in two layers. The first is the ordinary user who wants to "quickly declutter and customize your Windows experience, no installation required". The second is explicit: the script includes features "that system administrators and power users will enjoy", naming a command-line interface, Windows Audit mode support, and the ability to apply changes to other Windows users. Export and import of settings is there so the same configuration can be replayed across machines.

The feature list is grouped rather than flat. App removal is one category. Privacy and suggested content covers telemetry, diagnostic data, activity history, app-launch tracking and targeted ads. AI features cover Copilot, Recall and Click to Do, plus preventing the WSAIFabricSvc service from starting automatically, and disabling AI features in Edge, Paint and Notepad. Then System, Windows Update, Appearance, Start Menu and Search, Taskbar and File Explorer. That grouping is the real product: it is a menu of roughly two dozen change categories, not a single switch.

How the script works: registry files, a menu, and a settings export

The repository layout tells you most of the mechanism. The top level contains Win11Debloat.ps1, a Run.bat launcher, a Regfiles/ directory, a Config/ directory, a Schemas/ directory, a Scripts/ directory and a Tests/ directory. There is no installer, no service and no background agent. The PowerShell script is the whole runtime.

The Regfiles directory is the load-bearing part. The changes the script makes are expressed as registry files that get applied, which is why the README can say that all changes "can easily be reverted" and that almost all of the apps can be reinstalled through the Microsoft Store. Reverting is a separate documented procedure in the wiki, not an undo button inside the script. That distinction matters: the revert path exists, but you have to go find it.

The Config and Schemas directories point at the export and import feature. Schemas implies the settings file has a defined structure that is validated, which is what makes the file portable between machines. Scripts holds the supporting logic, and Tests indicates there is at least some automated checking of the script's behaviour, though the README does not describe what those tests cover.

Execution is interactive by default. The README says to "carefully read through and follow the on-screen instructions" in every one of its three launch methods, which means the primary interface is a menu you answer, not a config file you write. The command-line interface is the alternative for people who want the same result non-interactively.

Installing Win11Debloat and running it the first time

There are three documented ways in. The quick method downloads and launches the script in one command. Open PowerShell or Terminal and paste this, exactly as the README gives it:

& ([scriptblock]::Create((irm "https://debloat.raphi.re/")))

The script downloads itself and starts. The README says to wait for it to launch and then follow the on-screen instructions. This form also accepts command-line parameters, which the wiki documents under the command-line interface page.

The traditional method avoids the remote fetch. Download the latest release, extract the ZIP, open the Win11Debloat folder and double click Run.bat. The README notes that if the console window immediately closes, you should use the advanced method instead. You then accept the Windows UAC prompt, which the README states is required for the script to function.

The advanced method is the one to use if you want to see what is running. Download and extract the release, open PowerShell or Terminal as administrator, then temporarily allow script execution for this process only:

Set-ExecutionPolicy Bypass -Scope Process -Force

The -Scope Process part is worth noticing. It lifts the execution policy for the current PowerShell session and no further, so the machine's standing policy is untouched. Then change into the extracted folder and run the script:

cd c:\Win11Debloat
.\Win11Debloat.ps1

From there the flow is the same in all three cases: read the menu, choose what to apply, and let the script write the changes. Because the changes are registry-level, a reboot is a reasonable expectation after applying appearance or taskbar options, though the README does not promise one.

The revert story is documented, but it is not automatic

The most honest limitation is in the README itself, in a warning block above the usage section: "Great care went into making sure this script does not unintentionally break any OS functionality, but use at your own risk!" That is the author telling you the blast radius is real. The script edits the registry and removes packages. A wrong choice in the menu is not a preview.

The mitigation is that changes are revertible and apps are mostly reinstallable from the Microsoft Store, with a wiki page dedicated to reverting changes. But reverting is a manual procedure you have to seek out. Nothing in the README suggests the script keeps a per-run journal of what it changed, and the export and import feature is described as a way to apply your preferred settings to other systems, not as a rollback log. If you apply a batch of settings and something behaves oddly a week later, you are reconstructing which of the applied changes caused it.

There is a second constraint that is easy to miss: administrator rights. The README states UAC elevation is required for the script to function, and the advanced method tells you to open PowerShell as administrator. That rules out running it under a standard user account without elevation, and it means the script has the authority to do everything it claims.

The third is scope. This is a Windows-only tool by definition, and the README says it works for both Windows 10 and Windows 11. If you are managing macOS or Linux fleets, or you need a configuration mechanism that Microsoft supports and that survives feature updates, a registry-editing script is the wrong layer. Feature updates from Microsoft can also reintroduce defaults, and the README does not claim otherwise.

Win11Debloat compared with Chris Titus Tech's WinUtil

The comparison people reach for is Chris Titus Tech's WinUtil, and the difference is architectural rather than cosmetic. WinUtil is a general Windows utility with an install-and-tweaks surface that covers package installation, updates and configuration in one interface. Win11Debloat is narrower: it is a PowerShell script whose purpose is decluttering and privacy defaults, and the README describes it as lightweight with no installation required.

That narrowness shows up in the feature list. The AI section is specific to this script's release cadence: disable and remove Microsoft Copilot, Windows Recall and Click to Do, prevent WSAIFabricSvc from starting automatically, and turn off AI features in Edge, Paint and Notepad. The Windows Update section targets update timing, automatic restarts while signed in, Delivery Optimization and auto-installing device companion apps such as LG Monitor App and Alienware Command Center. Those are not generic tweaks; they are responses to specific Windows behaviours.

The administrator-facing features are the other differentiator. Audit mode support and the ability to make changes to other Windows users are called out in the README, along with export and import of settings. That is a provisioning workflow, not a one-off cleanup. If your job is preparing an image or a shared machine, that matters more than the menu's breadth.

Neither tool is a supported Microsoft management surface. Both sit outside the supported configuration model, which is the actual trade-off. You gain control over defaults Microsoft does not expose; you take on the job of tracking what changed when a feature update lands.

Maintenance, releases and the MIT licence

The last push to the default branch was on 2026-08-24, and the most recent release carries the same date. Before that, releases landed on 2026-07-11 and 2026-06-24. The cadence is roughly monthly, and the version numbers are calendar dates rather than semantic versions, so 2026.08.24 is the August 24, 2026 release. The repository is not archived.

The upgrade cost is low in the mechanical sense. There is nothing to install, so there is no package to update. You download a new release, or you run the one-line command and get whatever the current script is. The cost is in re-verification: after a Windows feature update, the registry keys the script targets may have moved or been superseded, and you would need to re-run and re-check. The Tests directory suggests the project has some automated coverage of its own behaviour, but the README does not say what it covers, so do not treat it as a guarantee about your specific Windows build.

The licence is MIT. In practical terms that is permissive: you can read the script, fork it, and adapt it for internal use. MIT also means the software comes with no warranty, which lines up with the README's own "use at your own risk" warning. If you redistribute a modified version inside an organisation, the MIT terms are the ones to read, and the LICENSE file at the repository root is the authoritative copy. None of this is legal advice; if the script is going into a managed environment, the licence text is short enough to read in full.

Editorial conclusion

Win11Debloat suits people who reinstall Windows often, system administrators working in Audit mode, and anyone who wants a documented, repeatable set of registry and app changes rather than clicking through Settings. It is the wrong tool if you need a supported, reversible-by-design configuration layer, or if you cannot accept that a shipped script edits the registry directly. Before running it, read the wiki page on reverting changes, note that the README asks for administrator rights, and decide which of the roughly two dozen feature groups you actually want, because the interactive menu applies them as a batch.

Frequently asked questions

Official sources

1. Official README
2. Project repository
3. Release notes