winutil: install, debloat, and tweak Windows fast
winutil earns its keep by turning a string of manual Windows setup chores into one PowerShell command run once per fresh install. The presets do the real work: Standard covers ordinary use, Advanced hands power users granular tweaks, and neither makes you click through a GUI installer per app. The catch: you're piping a remote script into an admin shell, so check `config/preset.json` before running one blind.
What is winutil
winutil is a free, open-source PowerShell utility from Chris Titus Tech for installing programs, debloating Windows, fixing configs, and managing Windows Update from one script. It replaces a string of separate installers and Control Panel visits with a single admin-terminal command, and it's released under the MIT license.
What winutil can do for your system
- ✓One-command install: piping `irm https://christitus.com/win | iex` into an admin PowerShell session pulls and runs the whole utility with no separate download step.
- ✓Three built-in presets — Standard, Minimal, and Advanced — apply a predefined set of tweaks without walking through every option by hand.
- ✓Program installation panel batches multiple app installs in one pass instead of running separate installers one at a time.
- ✓Debloat and tweak options handle Windows configuration fixes alongside install tasks, in the same session.
- ✓Windows Update controls are exposed in the same tool, so update behavior gets configured without hunting through separate Settings pages.
- ✓A development branch (`irm https://christitus.com/windev | iex`) exists for testing changes ahead of the stable release.
- ✓Preset contents are documented in `config/preset.json` in the repo, so you can check exactly what a preset changes before running it.
How to install winutil
Open PowerShell or Windows Terminal as Administrator — right-click Start and choose it, or press the Windows key, type PowerShell or Terminal, then hit Ctrl+Shift+Enter. Then run the stable branch with: ``` irm https://christitus.com/win | iex ``` For the development branch, run `irm https://christitus.com/windev | iex` instead. To skip the menu and apply a preset directly, run `& ([ScriptBlock]::Create((irm https://christitus.com/win))) -Preset Standard`, swapping in `Minimal` or `Advanced` as needed. Administrator rights are required because winutil makes system-wide changes.
Strengths
- ✓Runs as a single remote script, so there's nothing to download and unzip before you reach the actual menu.
- ✓MIT license means you can use, modify, and redistribute it without asking permission.
- ✓Presets save you from repeating the same setup by hand.
- ✓A dedicated known-issues page and GitHub issue tracker exist for reporting problems.
Risks and limitations to consider
- △The one-line install pattern (`irm ... | iex`) pipes a remote script straight into an admin shell — review what a preset changes in `config/preset.json` before trusting it on a machine you can't easily reimage.
- △The README doesn't document an undo or rollback mechanism for changes winutil makes, so treat tweaks as one-way unless you've made your own backup or restore point.
- △It requires Administrator privileges to run at all, which rules it out on locked-down or centrally managed corporate machines.
- △Individual tweak descriptions beyond the three preset names aren't documented in the README itself — you have to open `preset.json` to see specifics.
Alternatives to winutil
Frequently asked questions
winutil is designed to run on Windows systems and requires Administrator rights to make its changes, which the README states directly. The project keeps a known-issues page on its documentation site for tracking problems that come up, though the README doesn't publish a formal Windows 10/11 compatibility matrix.
winutil must be run as Administrator, because it makes system-wide changes — the project's own documentation explicitly notes this requirement.
winutil's README doesn't document a built-in undo or rollback feature for the changes it applies. Treat any preset or tweak as a one-way action unless you create a system restore point or backup beforehand — that precaution isn't part of the script itself, so it's on you to set one up first.
winutil ships three presets: Standard, described as balanced defaults for most users; Minimal, for the smallest set of changes; and Advanced, aimed at power users who want deeper tweaks. Run one directly with a `-Preset` flag, or check `config/preset.json` in the repo to see exactly what each one changes.
winutil is released under the MIT license, which permits commercial use, modification, and redistribution without paying for the script itself. A separate, paid 'Faster Dotnet Implementation' is sold on the maintainer's store, but that's an optional alternate build, not a requirement to use winutil.
winutil's README doesn't list individual debloat targets — it describes the tool broadly as handling installs, tweaks, fixes, and Windows Update configuration. For the exact list of what a given preset disables or changes, the repo points to `config/preset.json` rather than spelling it out in prose.
The problem it solves
Setting up a Windows machine the way you want it means visiting Control Panel, the Settings app, an installer for every program, and Windows Update options, usually in that order, every time you reimage or buy a new PC. winutil packages that whole sequence — installs, tweaks, config fixes, and update settings — into one PowerShell command run from an admin terminal, instead of redoing the same manual steps by hand on each machine.
Best use cases
- •Setting up a brand-new Windows install in one pass instead of clicking through installers one by one.
- •Reapplying a known-good preset across multiple machines you manage, like a home lab or a small office.
- •Debloating a Windows machine that came loaded with OEM trialware and default services you don't want.
- •Fixing specific config or Windows Update problems without digging through several Settings menus.
Who should try it — and who should skip
Anyone setting up a new Windows PC from scratch, or reimaging one on a schedule, gets the most out of winutil — the presets turn a routine into a five-minute script run. IT people managing a handful of similar machines benefit too, since the same preset can be reapplied identically each time. Skip it if you're on a locked-down or managed corporate machine without local admin rights, or if you're not willing to read `config/preset.json` before running a script you haven't inspected.
Related repositories
Curious whether winutil is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about winutil.
