Rufus looks simple, and it is - but three of its controls decide whether your USB boots, installs, or quietly fails. This guide walks the whole window in order and tells you honestly which settings to think about and which to leave exactly as Rufus sets them.
Most bootable-USB failures are not bad burns - they are one wrong dropdown. The burn completes, the drive looks right, and the target PC ignores it. Walk the Rufus window top to bottom with this page open and you will know which settings carry real consequences and which are safe defaults wearing a technical disguise.
The first dropdown is the only dangerous one. Rufus lists removable USB drives, and the honest check is capacity: if your pen drive is 16 GB and the selected device says 16 GB, you are looking at the right stick. If two drives are plugged in, unplug the one you are not burning. Rufus will erase whatever is selected here - the rest of the window cannot hurt you, this one can.
SELECT points Rufus at your ISO file. Hidden in the small arrow beside the button is a Download option that fetches official Windows ISOs from Microsoft's servers - a safer source than any random download portal. If Rufus refuses an ISO at this stage, believe it: the file is usually truncated or corrupt, and re-downloading now is cheaper than a failed install later.
With a Windows ISO loaded, Rufus offers Standard Windows installation and Windows To Go. Standard builds the normal installer USB - choose it. Windows To Go puts a full working Windows on the stick itself; Microsoft discontinued that feature years ago, so treat it as a technician's toy, not a daily system.
This is the setting worth understanding. GPT pairs with UEFI firmware, which is what essentially every PC from the last decade uses. MBR pairs with BIOS (or UEFI-CSM) and belongs to genuinely old machines. The rule that never fails: match the scheme to the target PC's firmware, not to the PC you are sitting at. Pick wrong and the burn succeeds perfectly - the target PC just never offers the USB in its boot menu, which sends people hunting for faults in the wrong place. Which scheme your disk and PC should use in depth is a full topic of its own; for burning an installer, target firmware is the whole decision.
When you choose GPT, Rufus sets the target to UEFI (non CSM); with MBR it becomes BIOS (or UEFI-CSM). This field follows your scheme choice automatically. If it ever appears to disagree, change the partition scheme, not this field.
Windows ISOs contain a file larger than the 4 GB limit of FAT32, so Rufus normally writes them as NTFS with a small UEFI-compatible loader, letting pure UEFI machines boot from an NTFS stick. Small Linux ISOs may be offered as FAT32. Either way, accept what Rufus proposes. Cluster size: Default, always. Nobody has ever fixed a boot problem with cluster size, and plenty have created one by experimenting here.
The label is cosmetic - name it something useful like WIN11 SETUP so future-you recognises the drive in a drawer. Then click START, read the erase warning like it matters, and wait for READY. For a Windows ISO, Rufus may show its Windows User Experience dialog after Start - those install-time options are a deep topic covered in the dedicated Rufus guides; for the basic burn, the window above is the whole craft.
Both tools are shown live in the video - every click, every setting, and the first boot from the finished USB.
▶️ Watch Full VideoNo. Nothing is damaged - the burn simply does not match the target PC's firmware, so that PC will not offer it as a boot option. Recreate the USB with the other scheme (GPT for UEFI machines, MBR for old BIOS machines) and it will boot. The ISO and the pen drive are both unharmed; only a few minutes are lost.
Almost. Rufus reads the ISO and proposes sensible values, and for a modern PC the defaults are usually right. The one setting to check with your own eyes is the partition scheme, because Rufus cannot know the firmware of the PC you will install on later - that knowledge is yours, not the program's.
No. Cluster size affects how small files pack into the file system, not installation speed in any way you could measure. Leave it on Default. Real install speed comes from the USB drive itself - a USB 3 stick in a USB 3 port - and from the target PC's storage.