Debloated Windows 11: Tiny 11 vs Atlas OS vs ReviOS

This guide compares three community-maintained debloated Windows 11 builds — Tiny 11, Atlas OS, and ReviOS — explains how to verify hardware compatibility, and walks through a clean USB install with privacy-respecting first-boot setup. It is the foundation for everything else on this site: the dual-boot guide starts from a working ReviOS install, the software inventory assumes a debloated base, and the Stata workflow runs on any of these three builds without changes.

---

The Problem With Standard Windows 11

Stock Windows 11 ships with significant bloatware and telemetry:

• Edge browser pinned to the taskbar, default for all web links
• Teams preinstalled and promoted in the Start Menu
• OneDrive aggressively syncing and consuming resources
• Copilot AI assistant baked into the OS
• Bing web search returning ads in Start Menu search results
• Microsoft account requirement for setup (in Home edition)
• Constant telemetry sending data to Microsoft servers
• Frequent forced updates interrupting your work

For a power user who wants a clean, bloatware-free Windows experience, there are two well-maintained community builds that strip all of this away.

---

Quick Comparison

Feature	Tiny 11	Atlas OS	ReviOS
Base	Windows 11 Consumer 25H2 stripped (official ISOs, rebuilt monthly)	Stock Windows 11 + Atlas Playbook via AME Wizard (or ISO injection) — current release v0.5.0 (Oct 2025)	Windows 11 Consumer 25H2 (configurable)
Install model	Prebuilt modified ISO	Playbook applied to a stock Microsoft ISO	Playbook with ISO injection from official image
Minimum RAM	2 GB	2 GB	4 GB
Minimum Disk	8 GB	12 GB	20 GB
Installed Size	~8 GB	~12 GB	~10–15 GB
Idle RAM Usage	~2.5 GB	~1.5–2.2 GB (vendor benchmark claims ~1.4 GB freed vs stock)	~3.0 GB

(Size and RAM figures are approximate community/vendor estimates — treat them as relative comparisons, not guarantees.)

Feature	Tiny 11	Atlas OS	ReviOS
Updates	Standard Windows Update	Security & cumulative updates apply; feature updates are skipped to preserve optimizations	Standard Windows Update
Update Support	Until Windows 11 end-of-life	Follows the underlying Windows 11 lifecycle	Until Windows 11 end-of-life
Microsoft Account	Not required (bypass built in)	Standard OOBE rules of your base edition; local account possible post-setup	Optional
Telemetry	Removed	Removed + firewall blocked	Removed + driver-blocked
Edge / Teams / OneDrive	Removed	Removed by playbook options	Removed (optional reinstall)
Microsoft Store	Optional	Configurable via playbook	Optional
Activation Required	Yes (see Disclaimer)	Yes (see Disclaimer)	Yes (see Disclaimer)
Rollback	Reinstall stock Windows	No rollback option — reverting requires reinstalling Windows	Reinstall or re-run playbook
Best For	Lightweight, modern UI	Performance tuning, gaming latency	Balanced debloat + maximum app compatibility
Maintenance	Active (NTDev, monthly ISO rebuilds)	Active (Atlas team, playbook releases)	Active (Revision team)

---

System Requirements

Tiny 11 bypasses the stock Windows 11 hardware checks (TPM, CPU generation) entirely, so it runs on hardware Microsoft rejects. The Atlas OS and ReviOS playbooks are applied to a stock Windows 11 install, so those paths need standard Windows 11 hardware — verify with Microsoft’s PC Health Check app.

---

Which Should You Choose?

Choose Tiny 11 if:

• You want the lightest possible Windows installation
• You have a low-spec machine (older laptop, 4-8 GB RAM)
• You prefer the standard Windows 11 look with modern features
• You want a familiar Windows Update experience
• You want to avoid frozen-feature-set app compatibility quirks

Choose Atlas OS if:

• You want security and cumulative updates to keep flowing while feature updates are skipped — new Windows functionality can’t break your tuned setup
• You run a performance-sensitive workflow (gaming, low-latency audio) where background services matter
• You prefer minimal telemetry with active firewall blocking
• You’re comfortable applying a playbook to a stock ISO (AME Wizard), like ReviOS
• You accept that there is no rollback — reverting means reinstalling Windows

Choose ReviOS if:

• You want a balanced approach — heavy debloat but with full app compatibility (Microsoft Store, Xbox apps, WSL, etc. all available)
• You use Microsoft Store apps regularly and want them to keep working without manual reconfiguration
• You want to block Recall, Click to Do, Copilot, and newer AI components by default (as of 25H2)
• You’re planning to dual-boot with Linux — ReviOS pairs cleanly with LMDE/Ubuntu and is the build the dual-boot guide is built around
• You prefer playbook-based tweaks (AME Wizard) over an opinionated ISO — ReviOS ships as a stock Windows ISO with a Playbook you load into AME Wizard for injection at install time
• You want active community-driven development with frequent playbook updates

Decision Flowchart

Do you have less than 8 GB RAM?
├── Yes → Tiny 11 (lighter, ~2.5 GB idle)
└── No
    │
    Do you want security updates without feature updates ever changing your system?
    ├── Yes → Atlas OS (feature updates skipped)
    └── No
        │
        Do you depend on Microsoft Store / Xbox / WSL apps?
        ├── Yes
        │   │
        │   Want to bake debloat INTO the install ISO?
        │   ├── Yes → ReviOS (ISO Injection via AME Wizard) or Atlas ISO injection
        │   └── No  → Tiny 11 (lighter base, install Store later)
        └── No
            │
            Pick whichever you prefer — Tiny 11 (lightest) or Atlas OS.

---

Download Sources

Tiny 11

Source	URL	Notes
Official (Archive.org)	archive.org/details/tiny11_25H2	Maintained by NTDEV; 25H2 ISOs rebuilt roughly monthly (check the page for the newest build and its published SHA-256)
tiny11 builder (GitHub)	github.com/ntdevlabs/tiny11builder	The script NTDEV uses — build your own tiny11 from an official Microsoft ISO

Atlas OS

Source	URL	Notes
Official Website	atlasos.net	Download portal (Atlas Playbook + AME Wizard)
Official Documentation	docs.atlasos.net	Installation guide (Playbook or ISO injection) — follow it exactly
Official GitHub	github.com/Atlas-OS	Source and releases

ReviOS

Source	URL	Notes
Official Website	revi.cc	Download AME Wizard and Playbook
Official GitHub	github.com/meetrevision	Revision team (ReviOS playbook, Revision Tool)

Atlas OS and ReviOS use the same install model (and the same AME Wizard tool): instead of shipping a prebuilt modified ISO, each provides a Playbook applied to an official Microsoft Windows 11 ISO — either during install (ISO injection) or on a running system. This means you always start from a genuine Microsoft image. Only Tiny 11 ships as a prebuilt modified ISO. The dual-boot guide is built around the ReviOS variant of this playbook flow; the same Revision Tool ecosystem can also apply ReviOS to an already-installed stock Windows without rebuilding anything — that’s the path documented on this site’s real machine.

Verify Checksum (PowerShell)

After downloading, verify the file integrity:

# PowerShell (Windows)
Get-FileHash -Algorithm SHA256 "C:\Users\$env:USERNAME\Downloads\tiny11_25H2.iso"

Compare the output hash against the value published on the official download page. They must match exactly.

# Bash (WSL, macOS, Linux)
sha256sum ~/Downloads/tiny11_25H2.iso

---

Creating a Bootable USB

You need a USB drive of at least 8 GB. This will be erased completely.

Using Rufus (Recommended)

Rufus is the most reliable USB creation tool for Windows.

1. Download Rufus from rufus.ie (portable, no installation)
2. Insert a USB drive (8 GB or larger)
3. Open Rufus
4. Configure:
   • Device: Select your USB drive
   • Boot selection: Click SELECT and choose your ISO file
   • Partition scheme: GPT
   • Target system: UEFI (non-CSM)
   • File system: FAT32 for the boot files; if your ISO exceeds 4 GB, Rufus will offer to split the install.wim or use NTFS/exFAT automatically — accept the prompt
5. Click START
6. Wait for the progress bar to complete (~10-20 minutes depending on USB speed)

Using balenaEtcher (Cross-platform Alternative)

On macOS or Linux, balenaEtcher flashes the same ISO with a three-click interface. Multi-ISO USB workflows (several installers on one drive) are covered by Ventoy in the dual-boot guide.

---

Installation Walkthrough

Step 1: Boot from USB

1. Save all open work in your current OS
2. Insert the USB drive
3. Restart your computer
4. During boot, press the boot menu key:
   • Lenovo ThinkPad: F12 or Enter then F1
   • Dell: F12
   • HP: F9
   • ASUS: Esc or F8
   • MSI: F11
   • Acer: F12
5. Select your USB drive from the boot menu
6. The Windows installer will load

Step 2: Windows Setup

The installation screens differ slightly by build path:

1. Language and Region: Select your preferences, click Next → Install now
2. Product Key (see Disclaimer above):
   • If you have a valid key, enter it
   • If not, click I don’t have a product key (you can add one later)
3. Edition Selection:
   • Tiny 11: Windows 11 Pro is selected by default
   • Atlas OS / ReviOS: install stock Windows 11 Pro from the official ISO — the playbook is applied afterwards (or baked in beforehand via ISO injection)
4. License Terms: Accept
5. Installation Type: Choose Custom: Install Windows only
6. Drive Selection: Select your target drive
   • If installing on a clean drive, delete all existing partitions first
   • Click Next to begin installation

The installer will copy files and restart several times (~10-15 minutes).

For Atlas OS: after setup completes and you reach the desktop, follow the official Atlas installation guide — download AME Wizard and the Atlas Playbook, then apply it. Same pattern for ReviOS with its Playbook, or use the Revision Tool on an existing install.

Step 3: First Boot Setup

After the final restart, you’ll see the Windows setup experience:

1. Region and Keyboard: Select your region and keyboard layout
2. Network: Connect Wi-Fi if needed — or skip ahead to the local-account methods below if you don’t want a Microsoft account
3. Microsoft Account vs Local Account:
   • Tiny 11: no Microsoft account required — create a local account directly
   • Atlas OS / ReviOS (stock ISO path): standard OOBE applies; see Local Account Bypass for current working methods
4. Privacy Settings: Disable all telemetry toggles
5. Cortana: Skip
6. Desktop: You’re now at your new, debloated Windows desktop

Local Account Bypass Methods for Any Windows 11 ISO

Microsoft removed the classic oobe\bypassnro script in March 2025 (builds 26200.5516+) — typing it at Shift+F10 now returns “command not recognized” on 24H2/25H2-era media, including current Tiny11 ISOs built from them. These methods still work:

Method 1 — Registry BypassNRO (most reliable):

1. At the “Sign in with Microsoft” screen, press Shift + F10
2. In the command prompt, run:

   reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f
   shutdown /r /t 0

3. After reboot, disconnect from the network when prompted and choose “I don’t have internet” → “Continue with limited setup”

Method 2 — Direct local-account dialog (25H2 stable):

1. Press Shift + F10 at the account screen
2. Run:

   start ms-cxh:localonly

3. A “Create a user for this PC” dialog opens — enter a local username/password and continue

Method 3 — Rufus: when creating install media, Rufus offers to remove the online-account requirement automatically (“Remove requirement for an online Microsoft account”).

Note: ms-cxh:localonly was blocked in recent Insider builds (26220+); on future stable releases, expect Method 1 or Rufus to be the durable options.

Applying the AME Wizard Playbook: What to Pick and What to Expect

For Atlas OS and ReviOS, the playbook run is where the real debloat happens. Guidance from a real ReviOS session (tested June 2026):

Recommended picks on the option screens:

• Disable Hibernate (the default) — hibernation enables Windows’ Fast Startup, which locks the system drive in a way that corrupts dual-boot setups when Linux mounts it. Also note the laptop caveat: without hibernate, Sleep still powers the RAM, so prefer a full Shut Down over closing the lid when the machine goes in a bag.
• Enable Legacy Context Menu — restores the full Windows 10 right-click menu instead of the buried “Show more options” flow.
• Disable Automatic Maintenance — stops Windows from launching background diagnostics/defrag/scans whenever it thinks the machine is idle.
• Remove pinned Start Menu items and Remove Xbox apps if you want a genuinely clean slate.
• Appearance options (dark mode, transparency, wallpaper) are pure preference — all reversible later.

Timing and gotchas:

• Activate Windows after the playbook finishes, not before. An offline install can’t reach activation servers anyway; connect to the internet once the playbook completes. If activation then errors (ReviOS removes some services Microsoft’s verification relies on), the Revision Tool can temporarily re-enable them.
• “Completed with Errors” is normal. Microsoft moves components between cumulative updates, so a playbook step occasionally fails against an app or service that no longer exists. Click Show logs, confirm the failures are cosmetic, reboot, move on.
• Prepare for a browser-less first boot. The playbook removes Edge, and an offline install means no bundled browser and possibly no WiFi driver yet. Before you start, put a browser installer and your laptop’s network driver on the same USB as the ISO.

---

Post-Install Configuration

Both builds share the same first-boot configuration steps:

Privacy Hardening

Open Settings → Privacy & security and disable:

Setting	Recommended State
Diagnostics & feedback → Send optional diagnostic data	Disabled
General → Let apps show me personalized ads	Disabled
Speech → Online speech recognition	Disabled
Search permissions → All sub-toggles	Disabled

Disable Remaining Telemetry (Atlas OS)

Atlas OS already blocks telemetry at the firewall level. To verify the rules are active:

Get-NetFirewallRule -Direction Outbound | Where-Object { $_.DisplayName -like "*telemetry*" -or $_.DisplayName -like "*diagtrack*" } | Select-Object DisplayName, Enabled

Update handling (including freezing updates entirely, as this site’s setup does) is covered by the frozen-update maintenance routine rather than manual service hacks.

Install Essential Software

Use winget (built into all three builds) to install your tools — the Power User Software Inventory is the full curated catalog with verified package IDs.

Configure Windows Terminal

Windows Terminal is preinstalled on both builds. Configure it as default:

1. Open Windows Terminal
2. Click the dropdown arrow → Settings
3. Set Default profile to PowerShell
4. Set Default terminal application to Windows Terminal

---

Troubleshooting

Boot Menu Key Not Working

If pressing the boot menu key doesn’t work:

1. Boot into Windows normally
2. Hold Shift while clicking Restart (in Start Menu)
3. Select Use a device → choose your USB drive

Windows 11 TPM Check Failure

If Windows setup refuses to install due to TPM/Secure Boot:

• For Tiny 11: The official ISO bypasses these checks automatically
• For Atlas OS / ReviOS: the playbooks include requirement bypasses; on a plain stock ISO you can also use Rufus’s “Remove TPM/Secure Boot requirement” option when creating the USB

Activation Prompt After Install

If Windows is not activated:

• Atlas OS: Activation prompt is non-intrusive; watermark in bottom-right corner only
• Tiny 11: Same behavior as stock Windows 11

See the Legal Responsibility Disclaimer at the top of this guide.

Audio or WiFi Not Working After Install

1. Open Device Manager (devmgmt.msc)
2. Check for devices with yellow warning icons
3. Right-click → Update driver → Search automatically for drivers
4. If no drivers found, download from your laptop manufacturer’s support page

---

Official References

• Microsoft Windows 11 System Requirements
• Tiny 11 25H2 ISOs (NTDev, Archive.org)
• tiny11 builder (GitHub)
• Atlas OS Official Website
• Atlas OS Installation Documentation
• Atlas OS GitHub Repository
• Rufus USB Creation Tool
• Microsoft PC Health Check App

---

Related Guides

• Power User Software Inventory — Install essential tools with winget
• Stata + VS Code Workflow on Windows — Development setup on Windows