Building installation media that actually boots
Media Creation Tool, a direct ISO and a USB writer, or Apple's createinstallmedia: what each is for, and the sizing and formatting mistakes that waste an afternoon.
A bootable installer is a small, unforgiving object. The image has to be the vendor's own, the USB stick has to be large enough, and the partition scheme has to match how the firmware boots. When one of those is wrong the symptom is unhelpful — the machine ignores the stick, or setup starts and then refuses the disk — and the usual advice on the internet is to start disabling firmware security settings.
This page compares the legitimate ways to produce installation media for Windows and macOS, and gives you a way to tell which failure you are looking at. All links lead to the vendor or, in the case of USB writing tools, to the tool's own publisher.
Pick the route that matches the job
For a straightforward Windows 11 reinstall on one machine, Microsoft's Media Creation Tool is the least error-prone route: it downloads the current image and writes a bootable stick in one pass. The vendor's own page documents what the tool needs and what each prompt means; use that wording in preference to a screenshot from a tutorial written for an earlier release.
The direct ISO download from the same Microsoft page is better when you want the image itself: for a virtual machine, for a machine without a reliable network during setup, or when you need to keep a copy of exactly what was installed. An ISO is not bootable by simply copying the file onto a USB stick; it has to be written with a tool that lays down the boot structures.
On a Mac, Apple's createinstallmedia command turns a full macOS installer downloaded from the App Store into a bootable volume. Apple's support article is the authoritative source for the command syntax and the volume name it expects. Recovery-based reinstall needs no USB stick at all, so only build one when you specifically need offline or clean-install media.
- One machine, one reinstall, normal network → Media Creation Tool.
- Virtual machine, repeat installs, or offline setup → official ISO plus a USB writer.
- Clean install of macOS with an erased volume → full installer plus createinstallmedia.
- Repairing an existing macOS system → Recovery, with no external media.
Size and format: the two numbers that matter
Use a 32 GB USB stick. That is Apple's own sizing for a bootable macOS installer, and it leaves comfortable headroom for current Windows images. A 16 GB stick is the number most often quoted in older guides; it can fail partway through creating a macOS installer, and it leaves no room for a second image or a driver folder.
The stick will be erased. Copy anything on it elsewhere first. For Windows media, the Media Creation Tool handles formatting; for a manually written ISO, the tool you choose will explain the partition scheme it produces. UEFI booting generally expects a FAT32-readable system partition, which is why some single files larger than 4 GB need special handling — a detail that a modern tool manages for you but that explains older advice about splitting archives.
Everything on the USB stick is erased
Writing an installer is not copying a file. The whole device is repartitioned. Check the drive letter or disk identifier twice; picking the wrong disk is the most destructive typo in this entire process.
Third-party USB writers: what is and is not acceptable
Rufus, Ventoy and balenaEtcher are open-source tools that write an image you already downloaded. They are not sources of Windows or macOS. That distinction is the whole editorial line of this site: the image must come from Microsoft or Apple, and the tool only puts those bytes onto a stick. Linking to the tool's own publisher is fine; downloading a 'Windows 11 ISO' from a mirror site is not.
Rufus offers options that change how the media is prepared, including tweaks to the Windows setup experience. Leave options you do not understand at their defaults. Ventoy is useful when you want one stick carrying several images, but it adds a boot menu layer of its own; if firmware will not boot it, try a directly written stick before changing firmware security settings.
- Download the image from the vendor, then write it locally.
- Use the tool's default settings unless a specific, understood requirement says otherwise.
- If the stick does not appear in the boot menu, rewrite it with a different tool before touching Secure Boot or CSM.
- Keep the image file until the install is confirmed working, so a failed write can be repeated without another download.
Booting the stick, and reading the failure
Firmware exposes a one-time boot menu on a key that varies by manufacturer; the exact key belongs to your model's documentation, not to a universal list. When the same USB device appears twice, the UEFI entry is the one to choose for a Windows 11 install to GPT.
If the machine ignores the stick completely, suspect the write or the port before the firmware: try another USB port, rewrite the stick, and confirm the image finished downloading. If setup starts but refuses the target disk, you are looking at a partition or driver question rather than a media question. Those are different problems with different fixes.
Do not disable Secure Boot to fix a boot failure
Official media boots with Secure Boot enabled. A stick that only works after disabling it is a strong hint that the media was prepared for legacy boot or that the image was modified.
Verify before you erase anything
A bootable stick is worth testing on the machine it will be used on: boot it, get as far as the first setup or Recovery screen, and then exit without erasing. That confirms the firmware sees it, the image is readable, and you know which boot-menu entry to use — all while the original system is still intact.
Also confirm the hash question honestly. Vendors do not consistently publish checksums for consumer images, and a checksum printed on the same page as an unofficial download proves nothing. The practical protection is provenance: the file came from the vendor's own domain over HTTPS, written by a tool you chose deliberately.
Mistakes to avoid
- Using a 16 GB stick for a macOS installer and having the create step fail partway through.
- Copying the ISO file onto a USB stick with File Explorer and expecting the firmware to boot it.
- Downloading the image from a mirror because it was faster, which removes the only guarantee that the installer is unmodified.
- Turning off Secure Boot or enabling CSM to make a badly written stick boot, then keeping those settings for the life of the install.
- Enabling extra 'tweak' options in a USB writer without knowing what they change about setup.
- Erasing the target volume before confirming the installer boots on that particular machine.
Questions people ask
Can I use the same USB stick for Windows and macOS installers?
Not at the same time with a simple write — each tool repartitions the device. Ventoy can carry several ISOs, but a macOS bootable installer is a different kind of volume, so use a separate stick for that.
Why does my USB stick show two entries in the boot menu?
One is the UEFI path and one the legacy/BIOS path offered by the firmware. For a Windows 11 install to a GPT disk, choose the UEFI entry.
Is Rufus a 'third-party mirror'?
No. It writes an image you supply. The distinction that matters is where the image came from: it must be Microsoft's or Apple's own download.
Should I verify a SHA-256 hash?
Only if the vendor published the hash on its own site for that exact file. A hash listed beside an unofficial download is not evidence of anything. Provenance from the vendor's domain is the stronger and simpler check.
Sources and further reading
- Create installation media for Windows Microsoft Support · Official support article The authority for current prompt wording and requirements. Tutorials age; this page is updated by the vendor.
- Download Windows 11 Microsoft · Vendor download page The three options are not interchangeable. We cite this page for which one suits an upgrade, a clean install or a virtual machine, and for the rule that the image comes from the vendor.
- Create a bootable installer for macOS Apple Support · Official support article Where the 32 GB figure and the command syntax come from. Copy the command from Apple, not from a blog post written for an older release.
- Rufus Rufus project (Pete Batard) · Open-source USB writer — publisher's site Cited as a tool, never as an image source. The image must already have come from the vendor.
- Ventoy Ventoy project · Open-source USB writer — publisher's site Explains the multi-image use case and the extra boot-menu layer it introduces.
- balenaEtcher balena · Open-source image writer — publisher's site The low-decision alternative for writing an ISO you already have.
Editorial note. This article describes decision logic and checks, not laboratory results. It quotes no benchmark, no test score and no screenshot. Screen labels are reproduced so you can find them on your own device; the sources listed below are the vendor documentation they were checked against.