Chris Titus Windows 11 Debloater -

Overview — Chris Titus Windows 11 Debloater

Step 2: Run the Install Command

Copy and paste this command:

irm "https://christitus.com/win" | iex

(This downloads and runs the latest script from Chris Titus’s official domain.) chris titus windows 11 debloater

What Exactly Is It?

First, a crucial distinction: This is not a sketchy, one-off executable downloaded from a random forum. It is an open-source, community-vetted PowerShell script. When you run it, you aren't installing new software; you are instructing Windows to remove features Microsoft buried three layers deep in the settings menu. Overview — Chris Titus Windows 11 Debloater

The tool is a text-based GUI (Graphical User Interface) that runs inside a terminal window. It categorizes tweaks into simple menus, allowing you to remove telemetry, uninstall pre-loaded apps, disable startup services, and even install essential software like Firefox, GIMP, or 7-Zip. What it is: A community-maintained PowerShell script and

Tab 1: Install & Upgrade (Ignore this for now)

This is for installing apps like 7-Zip, Firefox, or Gimp. We are focused on removal.

How to get it

Why Choose Chris Titus’s Script Over Others?

Many debloaters are destructive or "black box" tools that break Windows Update or Windows Security. Chris Titus’s approach stands out for three reasons:

  1. Transparency – The entire script is open source on GitHub. You can read every line before running it.
  2. Selective debloating – You choose what to remove. It doesn’t force a "minimalist" setup on everyone.
  3. Reversibility – Many tweaks can be undone, and you can reinstall Microsoft Store or Defender easily.

Tab 3: Micro-Win (Advanced)

This is for creating a custom Windows 11 installation ISO. Ignore this for a general debloat.

How to approach using Chris Titus’ debloater (concise workflow)

  1. Clone/download the official GitHub repo for the Windows 11 debloater.
  2. Inspect README and script options; choose conservative flags.
  3. Create a system backup (disk image or restore point).
  4. Run the script in a test VM or secondary machine first.
  5. Apply to your main system if results are acceptable.
  6. Keep the original scripts and a note of commands used for future restoration.