The worst moment to learn your installer USB does not boot is with a dead PC waiting on it. Three minutes of verification, done while everything still works, is the cheapest insurance in all of PC repair.
Every other page in this series assumes the burn worked. This one refuses to assume. A burning tool's success message certifies writing - nothing about your PC's willingness to boot what was written. The gap between those two words is where repair days go to die. Close it with the test boot, on the machine that matters, while you still have the leisure to fix what you find.
When Rufus shows its green READY bar or PowerISO reports success, the tool is certifying one thing: the bytes were written as instructed. Neither program can certify that your target PC's firmware will accept the result - that depends on the scheme you chose, the PC's boot mode, Secure Boot, and the port it is plugged into. Written and bootable are cousins, not twins. The only witness that settles it is a boot.
Do this while the patient is healthy, not mid-repair:
Three minutes now buys you certainty on the day the PC will not start without this stick.
A USB proven on your desk machine is probably good elsewhere - and probably is doing heavy lifting in that sentence. Firmware differs: the fixing-PC may want the other partition scheme, may enforce Secure Boot differently, may dislike the port. If the target PC is in front of you, its successful reach of the Setup screen is the only verification that counts. Technicians keep this religion because the alternative is discovering the exception with a customer's dead PC on the bench.
Rufus hides a lie detector in its advanced options: Check device for bad blocks, with a choice of passes. It writes and reads patterns across the whole stick before the real burn, flushing out the fake-capacity and dying drives that produce cursed installs - the ones that pass every casual test and fail at 70 percent of Setup. It adds time, so use it when the drive is old, unbranded, or has ever behaved oddly. PowerISO has no equivalent surface-level health check in its USB dialog.
Reached the language screen? The USB, the scheme, the port and the firmware are all compatible - write down what worked if this PC is a regular patient. Failed? Do not reburn blindly and hope; walk the failure like a checklist: entry chosen correctly, scheme matched to firmware, Secure Boot considered, second port tried, stick tested in another PC. Each test deletes a suspect. The boot checklist guide in this series walks that order in full - the habit to copy is the order, because random reburning teaches you nothing twice.
A verified installer deserves better than a drawer of identical black sticks. Put a tape flag on it: contents and date - 'Win11 24H2 - tested Oct 2026'. ISOs age; a stick burned for last year's version still boots beautifully into last year's problems, including missing the fixes your repair needed. Reburn or re-verify when a new Windows version lands, and retire sticks that start failing tests instead of promoting them to 'probably fine'. Tools you cannot trust are worse than tools you do not have.
Both tools are shown live in the video - every click, every setting, and the first boot from the finished USB.
▶️ Watch Full VideoPartly. A virtual machine can confirm the stick boots and Setup starts, which catches a corrupt ISO or a failed write. It cannot confirm your real PC's firmware behaviour - boot mode, Secure Boot acceptance, port quirks - which is where most real failures live. A VM pass is a good smoke test; a three-minute real boot on the target PC is the proof.
The files do not expire - a stick burned today will boot in five years. What ages is the version: Windows releases move on, and installing a years-old build means hours of updates and occasionally missing drivers for newer hardware. Recreate your installer when a new feature update arrives, and re-run the test boot after every reburn.
That pattern points at the drive itself rather than the boot chain - typically bad blocks or a failing stick that reads early files fine and dies on sustained reading. Run Rufus's bad-blocks check on it, or simply retire the stick and burn to a known-good drive; media is the cheapest component in the whole repair and the most blamed-last. Failing mid-install twice on one stick is the stick's confession.