Technical Anshu
Tutorials Blog
✅ Pre-Flight Checklist

Test a Custom Windows ISO Completely Before It Touches a Customer PC

An ISO is finished when testing says so, not when the build tool says so. This is the full sign-off a custom image should pass — in a VM, on real hardware, and against Windows Update — before it earns a place on a customer's PC.

✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 8 minute read
🎥 Watch the complete video — building a custom Windows ISO, removing unwanted components and setting the bypass options step by step

Every other page in this series prevents a class of failure. This page is the net that catches what prevention missed. The checklist below is deliberately strict — a master ISO that passes it can be installed on a customer's only computer with a straight face, and one that fails any line goes back to the bench, not into the field with fingers crossed. Run it for every new master, and the fast subset of it for every monthly refresh.

Sign-off sheet — the gates a master ISO must pass
VM install, unattended, no errorsgate 1
Bare-metal install on spare PCgate 2
Windows Update — two full runsgate 3
Store, activation, WinRE, driversgate 4
Previous master still on the shelfrollback ready
Five gates, in order. A failure at any gate stops the release — that is what makes it a checklist instead of a wish.
1

Gate 1 — The Clean Virtual Machine Install

  1. Install on a fresh VM with no snapshots or pre-seeded state, using the exact media you will carry
  2. Confirm the install is truly unattended where you designed it to be — and that no unexpected screen, error or second reboot loop appears
  3. Reach the desktop and verify your removals: the apps you removed are absent, the apps you kept are present, for a new user account, not just the first one
  4. Check the setup script log and confirm every standard app installed — read the log file, do not eyeball the desktop
2

Gate 2 — Bare Metal on a Spare Real PC

  1. Install on the oldest, least standard real machine you have access to — it represents customer hardware better than your newest bench PC
  2. Confirm Setup sees the disk without loading drivers by hand, and the first boot reaches the desktop
  3. Open Device Manager: no unknown devices, and the drivers you integrated are the ones actually bound
  4. Test the hardware you customised around — Wi-Fi, sound, touchpad or trackpad gestures, function keys, sleep and wake
3

Gate 3 — Servicing and Store Reality ⭐

  1. Run Windows Update, reboot, and run it again — the second run is the one that exposes component-store damage from aggressive removals
  2. Confirm activation status with slmgr.vbs /dli on licensed hardware
  3. Open the Microsoft Store, update the inbox apps, and install one free app — this catches a removed Store or a broken app plumbing quietly and early
  4. Boot into WinRE once (reagentc /info on the running system confirms it is enabled and present) and start one recovery tool
  5. Create a restore point and roll it back — shadow copy plumbing is another silent casualty of over-removal
4

Gate 4 — The Rollback Plan and the Paperwork

  1. The previous tested master stays available until this one has survived a real week in the field — rollback is a file you kept, not a hope
  2. The untouched Microsoft ISO stays on the same shelf; it is the universal fallback for servicing repairs and strange failures
  3. Write the changelog line now, while the build is fresh: version, date, components changed, tests passed, tester
  4. Label the physical stick with the master version. An unlabelled stick in a technician's bag is an incident waiting for a date

An ISO that clears all four gates is no longer a project — it is equipment. Treat it that way and it will repay you on every install.

🎥 Watch the Complete Video Guide

Every checkbox, removal and bypass option from this page is shown live in the full video — watch it end to end before you build your own ISO.

▶️ Watch Full Video
❓ Frequently Asked Questions

How long does the full checklist take?

About an hour of mostly unattended time for a new master: the VM install and updates run themselves while you do other work. The monthly refresh needs only the fast subset — VM install, one full update run, Store and activation checks.

My ISO passes in the VM but I have no spare PC. Can I skip bare metal?

You can, but you are accepting the exact risk the VM cannot see — storage controllers, firmware and OEM hardware behaviour. Borrow any old real machine for the first release of a master line; after that, monthly refreshes can reasonably be VM-only.

What is the single most skipped test that causes field failures?

The second Windows Update run. Builders test that the image installs; the component-store damage from aggressive removal only shows itself when the servicing system does real work, which for most people is the customer's first Patch Tuesday.

This guide is based on the Technical Anshu video on building your own Windows ISO and removing unwanted components • Stuck on a step? Ask in the video comments — you will get help 🙏