Your Custom Windows ISO Fails to Install, Restarts in a Loop, or Blue-Screens - Why
A stock ISO installs anywhere; your custom one dies at 70%, or reboots into a blue screen on first start. Almost always, the build — not the PC — is at fault. Work through the causes in order.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 8 minute read
🎥 A clean, working custom ISO build to compare your steps against — full video
First, the diagnostic that saves you hours: boot the same PC from the original, untouched Microsoft ISO. If the stock image installs perfectly, your hardware is fine and the problem lives inside your custom build — which is good news, because builds can be fixed. Custom ISO failures almost always trace back to one of five causes: components removed that Setup quietly needed, a bad or wrong driver baked into the image, a corrupted image file, faulty USB media, or a broken answer file. Here is how to identify and repair each one.
Windows Setup
Windows could not configure one or more system components. To install Windows, restart the computer and then restart the installation.
The exact Setup message that ends most over-stripped builds — installation dies in its final configuration phase.
1
Cause: Components Removed That Setup Needed
The classic symptom is Setup stopping with "Windows could not configure one or more system components" or failing during the final phase (specialize/OOBE). Removing language packs for the setup language, Windows Recovery, "Windows Setup" support files, or certain .NET and scripting components produces exactly this.
Rebuild the image removing apps only — no system components — and test that build
If it works, re-add component removals in small groups, testing each build in a virtual machine, until the failing group reveals itself
In NTLite, keep the compatibility protections for Windows Update, OOBE and Recommended enabled — they exist to block precisely these removals
2
Cause: A Bad Integrated Driver (Blue Screen After Install)
If installation completes but the first boots end in INACCESSIBLE_BOOT_DEVICE or random blue screens, suspect a driver you integrated — above all a storage/NVMe driver of the wrong version or architecture, which Windows must load before it can even see your disk.
Rebuild the ISO without any integrated drivers and test — if the blue screens vanish, the driver set was the problem
Re-add drivers one family at a time (storage first is the riskiest), using only signed drivers for your exact Windows version and 64-bit/32-bit architecture
Never integrate driver .exe installers or drivers "for a similar model" — only the extracted .inf packages for your exact hardware
Blue Screen
:(
Your device ran into a problem and needs to restart. We'll restart for you.
Stop code: INACCESSIBLE_BOOT_DEVICE
The blue screen that points at a bad boot-critical driver: Windows cannot reach its own disk.
3
Cause: Corrupted Image or Faulty USB Writing
Errors like 0x8007025D (missing/corrupt files) during the copying phase usually mean the image got damaged — a DISM operation interrupted mid-way, a bad download, or a dying USB stick.
Verify your image with DISM before rebuilding media: dism /Get-WimInfo /WimFile:"C:\ISO\sources\install.wim" — if it errors out, the image is damaged
Re-extract from the original Microsoft ISO and redo the edit instead of patching a suspect image
Write the USB again with Rufus or Ventoy, and try a different USB stick — cheap sticks fail exactly at multi-GB files
Test the finished ISO file itself in a virtual machine: if it fails there too on clean virtual hardware, the image — not your PC or stick — is guilty
Windows Setup
Windows cannot install required files. The file may be corrupt or missing. Make sure all files required for installation are available, and restart the installation. Error code: 0x8007025D
Error 0x8007025D during the copying phase — the fingerprint of a corrupt image file or failing USB media.
4
The Fix Workflow That Always Finds It ⭐
Guessing wastes days. Bisect instead:
Stock ISO on the same machine — passes? Hardware is innocent
Apps-only debloat build in a VM — passes? Your base process is sound
Add back one change group at a time (components → drivers → updates → unattended file), testing in the VM after each
The first group that breaks the VM test is your culprit — rebuild without it, or fix that group's contents
Save the NTLite preset of every build so "what changed?" is never a mystery
⚠️ About that answer file: if you use autounattend.xml, a single malformed entry can halt Setup with "Windows could not parse or process the unattend answer file". Test any new answer file in a VM first, and try the same ISO without the file to rule it out — disk-partition instructions in a bad answer file can also target the wrong disk on the real machine.
🎥 Watch a Build That Works, Step by Step
The complete custom ISO process done cleanly — genuine ISO, careful debloat, drivers, and a working final image.
Setup says "Windows could not configure one or more system components" — what now?
A component removed from the image is needed during the configuration phase. The practical fix is to rebuild with apps-only removal, confirm it installs, then reintroduce component removals gradually with VM tests, keeping your tool's compatibility protections on.
Why does my PC blue-screen with INACCESSIBLE_BOOT_DEVICE only on the custom ISO?
Because the boot-critical storage path changed: usually a wrong or unsigned storage driver integrated into the image, or storage-related components removed. Rebuild without integrated drivers to confirm, then add only the exact signed driver for your controller.
The error is 0x8007025D during file copying. Is my ISO corrupt?
Very likely either the image or the USB media. Test the ISO in a virtual machine first — if it installs there, re-write the USB (different stick if possible). If it fails in the VM too, verify the WIM with DISM Get-WimInfo and rebuild from the original Microsoft ISO.
This guide is based on the Technical Anshu video on creating your own custom Windows ISO • Stuck on a step? Ask in the video comments — you will get help 🙏