Ready-made rescue disks run into gigabytes and carry hundreds of programs you will never touch. A toolkit you build yourself can be a few hundred MB, boot in seconds, and contain exactly your tools — nothing else. Here is the full build, in the right order.
In the video, Technical Anshu shows the bootable USB he is building for himself: a light custom WinPE, his own WIM file, and roughly 400–500 MB of hand-picked tools — made for the worst case, a PC that does not turn on at all. This guide follows the same build-your-own idea end to end: pick a base, lay out the stick, add only the tools each repair job needs, and test the finished drive before you trust it on a real dead PC.
Everything starts with the boot environment. You have two honest routes. Route one: build a WinPE from Microsoft's free Windows ADK and WinPE add-on, then mount the boot.wim, copy your portable tools inside, and unmount with dism /unmount-wim /commit. Full control, smallest size, but you maintain every piece yourself.
Route two: install Ventoy on the stick and simply copy your own WinPE ISO or WIM-boot setup onto it alongside Windows installer ISOs. Less pure, far easier to update — replacing the toolkit means replacing one file. The video's build follows the WIM idea: one light boot image, his tools, his layout. Pick route one for a single-purpose repair stick, route two if the same stick must also install Windows.
A toolkit you cannot navigate under pressure is just storage. Create the skeleton first: Tools split by job (Disk, Recovery, Backup, Network), a separate Drivers folder, a Scripts folder for your own batch files, and a CHANGELOG.txt at the root. Keep names short and English — WinPE command lines and older BIOS screens punish long names and spaces.
Put nothing loose in the root except the boot files and the changelog. Six months later, mid-repair, you will thank yourself: every tool is one folder away, and a teammate opening the stick understands it without asking you.
Resist the collector habit. A working repair stick needs one trusted tool per job: disk health check, partition manager, file recovery, disk imaging, password reset for local accounts, an offline antivirus scanner, a file manager, and a browser-free way to copy files off a dead system. One per job. Two tools that do the same thing means you will hesitate at the worst moment.
Prefer genuinely portable builds from the maker's own site — they run from the stick without installing and leave the patient's PC untouched. Every extra hundred MB should have to justify itself; the video's whole toolkit is around 400–500 MB, and that lightness is exactly why it boots fast on old machines.
The heart of offline repair is a handful of commands. From the WinPE command prompt, with the patient's Windows usually on D: or C: (check with diskpart then list volume): repair files with sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows, repair the component store with dism /image:C:\ /cleanup-image /restorehealth, check the disk with chkdsk C: /f, and rebuild boot files with bcdboot C:\Windows.
Save these as small batch files in your Scripts folder so a tired evening repair is one click instead of five typed commands. That one-click habit is the whole point of a custom build — the toolkit works the way you work.
A toolkit that fails on its first real job is worse than none. Boot it in a virtual machine first, then on one real spare PC, and walk the checklist: does it boot on UEFI and on legacy BIOS, does it see an NVMe drive, does the network work, does every menu entry open. Only after that test does the stick go in your bag.
Be honest about the limit: a custom WinPE is yours to maintain. When Windows changes, drivers age, and tools stop opening, there is no vendor to call — the fix is your quarterly update routine. That trade is fair: total control, total responsibility.
Choosing the base, adding the tools and the first real boot test — the complete custom build is shown live in the video.
▶️ Watch Full VideoThe toolkit itself can be tiny — the build in the video is roughly 400–500 MB of tools around a slim WinPE. A 32 GB stick is comfortable if the same drive also carries Windows installer ISOs; a 16 GB stick is enough for a pure repair toolkit. Speed matters more than size, so prefer a decent USB 3.x stick over a huge slow one.
For learning and for speed, yes — you know every tool on it and it boots fast. The honest cost is maintenance: ready-made projects are updated by their makers, while a custom build is updated by you. Many technicians do both: a ready-made image as backup, and their own slim stick as the daily driver.
The clean, legal route is Microsoft's free ADK plus the WinPE add-on, which gives you the official base image to customise. Shortcut builders from random forums often bundle outdated or modified system files — for a tool you will boot on other people's PCs, start from the official base.