How to Create a Bootable Windows USB Installer

A bootable Windows USB installer is essential for a clean install, an in-place upgrade repair, or recovering a system that won’t boot at all. This uses Microsoft’s own Media Creation Tool — no third-party software needed.

Step 1: get a USB drive of sufficient size

You’ll need at least an 8GB USB drive, ready to be completely erased — the tool will overwrite everything on it.

Step 2: download the Media Creation Tool

Download it directly from Microsoft’s official Windows download page for the version you need (search “Download Windows 11” or “Download Windows 10” from a browser, on Microsoft’s own site specifically — avoid third-party mirrors for a system-level installer like this).

Step 3: run the tool and choose the USB option

Launch MediaCreationTool.exe, accept the license terms, and when prompted choose “Create installation media (USB flash drive, DVD, or ISO file) for another PC” rather than “Upgrade this PC now” — this builds a standalone bootable installer rather than immediately upgrading the machine you’re running the tool on.

Step 4: choose language, edition, and architecture

By default the tool recommends options matching your current PC — uncheck “Use the recommended options” if you specifically need a different language, edition, or architecture (for example, building media for a different machine than the one you’re currently using).

Step 5: select USB flash drive as the media type

Choose USB flash drive (rather than ISO file) when prompted, then select your target drive from the list. Confirm you’ve selected the correct drive before continuing — this step erases it completely.

Step 6: wait for download and creation to complete

The tool downloads the necessary Windows files and writes them to the USB drive, showing progress through several stages. This can take a while depending on your internet connection speed, since it downloads the full OS image before writing it.

Step 7: verify the installer actually works, before you need it in an emergency

Don’t wait until an actual emergency to discover a bad USB installer. On a spare machine or a virtual machine, boot from the USB drive and confirm you reach the Windows Setup screen:

Restart the target machine, and during startup, access the boot menu (commonly F12, F11, Esc, or Del depending on manufacturer) and select the USB drive.

Step 8: know your options once booted from it

From the Windows Setup screen, Shift+F10 opens a command prompt — useful for advanced recovery tasks like manually repairing the boot configuration data (bootrec) without needing to proceed through the full graphical installer at all.

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

These three commands, run in that order from the Setup command prompt, are the standard sequence for repairing a corrupted or missing Windows boot configuration without reinstalling anything.

Why verify it in advance rather than trusting it blindly

A bootable USB installer is exactly the kind of tool you need most when something has already gone wrong — discovering at that moment that the USB creation silently failed, or that your specific machine’s BIOS boot order needs adjusting, turns a recoverable situation into a much more stressful one. Testing it once, calmly, ahead of any actual emergency, is a small time investment against a much larger potential cost later.

Building the same media with the command-line alternative, when the GUI tool isn’t practical

DISM /Get-WimInfo /WimFile:D:\sources\install.wim

For scripted or repeated media creation — building installers for several different Windows editions, or automating the process as part of a larger deployment workflow — the Media Creation Tool’s GUI-only interface becomes a genuine limitation. Microsoft’s Windows ADK (Assessment and Deployment Kit) provides DISM and related command-line tools that can inspect, customize, and inject drivers or updates directly into an existing install.wim image before writing it to media, a meaningfully more flexible and scriptable path than the Media Creation Tool’s fixed, GUI-driven workflow, appropriate specifically once you’re managing more than an occasional single installer for personal use.

Choosing GPT/UEFI versus MBR/Legacy BIOS partitioning correctly

A USB installer built for a UEFI-based machine needs a GPT-partitioned, FAT32-formatted structure specifically, while an older Legacy BIOS machine expects MBR partitioning — the Media Creation Tool handles this automatically based on the machine it’s run on by default, but building installation media on one machine for use on a different, older machine with different firmware can produce media that simply won’t boot on the target if the partition scheme doesn’t match what that target’s firmware actually expects. Checking the target machine’s own firmware mode (msinfo32, checking the “BIOS Mode” field for UEFI versus Legacy) before assuming a USB built elsewhere will boot correctly avoids a confusing “USB doesn’t show up in the boot menu at all” failure that has nothing to do with the USB creation process itself having gone wrong.

Why an 8GB minimum is a floor, not a comfortable target

While 8GB technically fits a standard Windows installation image, a drive at or near that exact minimum leaves no room for the tool to work with temporary files during creation, and larger feature updates or specific editions can push actual space requirements higher than the stated minimum suggests. Using a 16GB or larger drive when one is available removes this as a variable entirely, rather than risking a creation failure partway through specifically due to insufficient free space on a drive that technically met the documented minimum.

Related:

Sources: