Technical Anshu
Tutorials Blog
🛠️ Tiny11 Builder

Build Your Own Tiny11 ISO With the Tiny11Builder Script

A prebuilt ISO asks you to trust a stranger's Windows. The tiny11builder script asks you to trust only Microsoft's ISO and a script you can read. Here is the full build process.

✍️ Technical Anshu🪟 Windows 11⏱️ 9 minute guide
🎥 Watch the full Tiny11 25H2 installation in the video — every step shown live

NTDEV publishes Tiny11 two ways: ready-made ISOs, and tiny11builder — an open-source set of PowerShell scripts on GitHub (ntdevlabs/tiny11builder) that trims a genuine Microsoft Windows 11 ISO on your own PC. It uses Microsoft's own tools (DISM) and an unattended setup file, nothing hidden. For the newest Windows versions, NTDEV recommends this route over old prebuilt images — and for safety, so do we. If you can follow steps carefully, you can build your own.

Windows PowerShell (Administrator) — the build in progress (illustrative)
PS C:\tiny11builder> .\tiny11maker.ps1 -ISO D -SCRATCH C Mounting Windows image... Removing Appx packages... Removing components... Applying unattended setup file... Creating tiny11.iso ... Done.
Output: a fresh tiny11.iso built from your own Microsoft download
Example console output. Exact wording varies by script version — the point is the whole process happens on your PC, in the open.
1

What You Need Before Starting

  1. A Windows 10 or 11 PC with administrator rights and plenty of free disk space — the build unpacks a full Windows image; plan on roughly 30-70 GB of working room depending on the source ISO
  2. The official Windows 11 ISO from Microsoft's download page, in your language and edition (the script works with virtually any 64-bit build and edition)
  3. Windows PowerShell 5.1 — the version built into Windows; the project's instructions specify it
  4. About 20-40 minutes — most of it is the script working unattended

No product key is needed to build. Activation is a separate, later step on the installed system, using a genuine licence.

2

Verify the Microsoft ISO Before Anything Touches It

The whole safety argument of this method is 'the source was genuine'. Prove it:

  1. Download the ISO only from Microsoft's official Windows 11 download page
  2. Open PowerShell in the download folder and run Get-FileHash .\Win11.iso -Algorithm SHA256 (use your file's real name)
  3. Compare the result, character by character, with the SHA256 Microsoft lists for your language on the download page
  4. Mismatch = corrupted or tampered file. Delete it and download again — do not 'try anyway'
3

Get the Script From the One Official Repository

  1. Go directly to the official repository: github.com/ntdevlabs/tiny11builder — type it yourself; do not follow random 'Tiny11 Builder download' sites, mirrors or YouTube description links
  2. Download the repository (Code → Download ZIP) and extract it to a simple folder such as C:\tiny11builder
  3. Read the README and glance at recent commits — the script is actively maintained and the current instructions always win over any older guide, including this one
  4. Know your two scripts: tiny11maker.ps1 builds the normal, serviceable Tiny11 — use this one. tiny11Coremaker.ps1 builds Tiny11 Core, which removes servicing too and is meant only for quick tests
4

Run the Build — Mount, Allow, Execute

  1. Mount the Microsoft ISO: right-click it in File Explorer → Mount. Note the virtual drive letter Windows gives it, for example D:
  2. Open Windows PowerShell as Administrator
  3. Allow scripts for this session only — this does not weaken your PC permanently: Set-ExecutionPolicy Bypass -Scope Process and confirm with Y. Closing the window restores your previous policy
  4. Move into the script folder: cd C:\tiny11builder
  5. Run the maker with your drive letters: .\tiny11maker.ps1 -ISO D -SCRATCH C — replace D with your mounted ISO letter and C with a drive that has the free space
  6. When asked, select the Windows edition (Pro is the common choice). Then wait — mounting, removing packages and repacking takes a while and the PC will work hard
  7. The script finishes by producing tiny11.iso in the output location shown on screen
5

Test Your ISO Before Trusting It

  1. First stop: a virtual machine (Hyper-V, VirtualBox or VMware). Install your ISO there and confirm it boots, reaches the desktop and opens Settings and Windows Update
  2. Check what the build kept and removed matches the README's list for the current script version
  3. Only then write it to USB with Rufus and install on real hardware
  4. Keep the ISO and note which Microsoft build and script version made it — when a new Windows version releases, you repeat this same process to get a fresh, current Tiny11 instead of forcing an old image to upgrade

That rebuild habit is the real long-term maintenance model of Tiny11 — and it is only possible because the builder is a script, not a frozen download.

🔍 Why this route is the safest: every ingredient is inspectable — Microsoft's hash-verified ISO, and a script written in plain PowerShell that you (or anyone) can read before running. A downloaded 'prebuilt Tiny11' from anywhere except NTDEV's own archive upload offers neither guarantee.

🎥 Prefer Watching? See the Tiny11 25H2 Install in the Video

Once your ISO is built, the installation itself is exactly what the video demonstrates, step by step.

▶️ Watch Full Video
❓ Frequently Asked Questions

The script is blocked and will not run. What is wrong?

That is PowerShell's execution policy doing its job. Open PowerShell as Administrator and run Set-ExecutionPolicy Bypass -Scope Process, then run the script again in the same window. The Bypass applies only to that session — it is the method the project itself recommends, and it leaves your permanent policy untouched.

Which script should a normal user run, maker or Coremaker?

tiny11maker.ps1. It produces the standard Tiny11 that still receives Windows Updates. tiny11Coremaker.ps1 removes servicing support to save more space, so the install can never be properly updated — it exists for quick tests and disposable VMs, not real PCs.

Can I choose exactly which apps get removed?

The standard scripts apply NTDEV's tested removal set rather than a pick-and-choose menu; newer builder versions and forks experiment with component selection, but the official repo's design goal is a known-good result. If you need one specific app back afterwards, our guide on adding components back to Tiny11 explains what is and is not possible.

This guide is based on the Technical Anshu Tiny11 25H2 installation video • Stuck on any step? Ask in the video comments — help is available there 🙏