A finished burn and a PC that ignores it - this is the most common bootable-USB frustration there is. Work this checklist in order and you will find the cause, because nearly every case is one of these seven.
Before you burn the stick again, understand the odds: the burn is rarely the problem. The PC was never asked to boot from USB, or was asked in the wrong firmware language, or quietly refused the image. Each card below is one real cause, in the order you should test them - menu first, settings second, reburn last.
Restart the PC and tap its boot-menu key as it starts: F12 on many Dell and Lenovo machines, F9 on HP, Esc or F8 on others; the first startup screen usually names it. The one-time menu asks this boot only, changes nothing permanently, and is the right tool for an install. Digging into BIOS boot order before trying the menu is the classic way to spend twenty minutes on a ten-second problem.
The menu may list your pen drive twice. Pick the entry that begins with UEFI: - that is the modern path, and it matches a GPT-burned Rufus stick. The plain or legacy entry boots the drive in old BIOS style, which pairs with MBR burns. Choosing the legacy entry for a GPT stick (or the reverse) is the most common reason a perfectly good USB appears to do nothing: the PC skips it silently and boots the old Windows, looking exactly like a failed burn.
Windows installer media often shows Press any key to boot from USB for a few seconds. It is a real question with a timeout. Press a key, or the PC continues to the hard disk and you will swear the USB is broken while it sits there working perfectly. Laptops with function-key layers may need Fn held as well.
If the drive never appears in the boot menu at all, suspect the burn's scheme before the drive. A GPT stick is invisible to a BIOS-only machine; an MBR stick can be hidden on a UEFI machine with legacy support disabled. The fix is not in the BIOS - it is back in Rufus: recreate the USB with the scheme that matches the target PC's firmware. PowerISO users have no such dial, which is why a stubborn machine is Rufus territory.
Secure Boot accepts only signed bootloaders. Windows installer media made by Rufus boots with Secure Boot on. Some Linux distributions and rescue tools are not signed, and a strict UEFI simply refuses them - often with no message at all. The honest options: use a signed distribution, or disable Secure Boot temporarily in the firmware settings for that one job and switch it back on afterwards. Do not leave it off because a guide was in a hurry.
Try a different USB port - a rear motherboard port on a desktop, and if the stick is USB 3, try a USB 2 port as well; some firmware is picky during boot even though Windows handles the same port fine later. Then suspect the drive itself: very old, very cheap pen drives develop bad blocks exactly where boot files land. A stick that fails on two known-good PCs has given you its answer - replace it.
Many UEFI boards offer a CSM (Compatibility Support Module) that emulates old BIOS booting. With CSM on, both entry types appear and confusion doubles. Simple discipline: modern PC, CSM off, GPT stick, UEFI entry. Old BIOS-only PC, MBR stick, the only entry it shows. Mixing worlds - CSM on, wrong scheme, wrong entry - accounts for nearly every 'USB will not boot' story that ends well.
Both tools are shown live in the video - every click, every setting, and the first boot from the finished USB.
▶️ Watch Full VideoBecause booting is a conversation between the stick and that PC's firmware. A different firmware mode (UEFI versus legacy), Secure Boot state, or partition-scheme expectation on the target machine can refuse a stick that boots fine elsewhere. Test and, if needed, recreate the USB for the target PC - its firmware, not yours, is the one that must be pleased.
For a one-off install, no. The one-time boot menu exists for exactly this and leaves your settings untouched. Permanent reordering makes sense only on a technician's test bench machine that boots from USB every day. On a normal PC, a USB-first order just adds a delay and a surprise every time a forgotten stick is plugged in.
First, a different port and a full power-off restart rather than a warm reboot. Second, check the partition scheme against the PC's firmware - GPT for UEFI, MBR for old BIOS - and recreate if they mismatch. Third, try the stick in another PC: if it is invisible everywhere, the drive itself has likely failed and no setting will resurrect it.