Procedures
Preparing a Windows installation drive
The awkward part is not the writing, it is the 4 GB file inside a modern Windows image and the firmware requirements the installer enforces. Both are manageable once you know they are coming.
Key points
- Download the image from Microsoft's own page; a valid licence is required to use Windows.
- Current images contain a file larger than FAT32 allows — the tool must handle it.
- Recent Windows releases expect UEFI mode, GPT and Secure Boot on the target machine.
Check these first
- A licence covering the installation. The installer will run without a key entered, but using Windows requires one.
- A 16 GB or larger USB drive with nothing on it you want to keep.
- The target machine's firmware mode and whether it meets the release's requirements — recent versions check for UEFI, Secure Boot and a TPM.
- A backup of the machine you are about to install on. Installation is destructive by design.
- Network drivers for that machine saved somewhere separate, in case the installer does not include them.
Getting the image
Microsoft publishes installation images and its own media creation utility on its software download pages, under microsoft.com. Take the file from there rather than from a third-party mirror: you get the current build, and you can compare what you received against the published details.
Watch the address bar. Windows images attract lookalike download sites in large numbers. A page that looks right but sits on an unfamiliar domain is worth closing.
Microsoft's own media creation utility will prepare a drive for you in one pass, which is the shortest route if you are already on Windows and want no decisions. The rest of this page is for when you want control, or you are not on Windows.
Choosing a method
| Situation | Approach |
|---|---|
| On Windows, one machine to install | Microsoft's media creation utility, or Rufus |
| On Windows, want to set partition scheme or split behaviour | Rufus |
| On Linux | WoeUSB-ng, or an image loader |
| On macOS | An image loader on a spare drive, or a Windows machine — native options are limited |
| Drive also carries other systems | Image loader; copy the ISO as a file |
The usual route on Windows
Select device and image
Open Rufus, pick the USB drive at the top, then select the ISO. Read the device name carefully; external hard drives have been erased at this step.
Set partition scheme and target
GPT with target "UEFI (non CSM)" for a modern machine. MBR with "BIOS or UEFI" if the target is older or you are not sure. Leave the file system at the suggested value.
Let it deal with the large file
Rufus detects an oversized
install.wimand either splits it or builds an NTFS partition with a UEFI driver. Both are normal and both boot.Write and wait
Ten to twenty minutes on a reasonable drive. Do not unplug it because progress appears stuck at 99% — that is the flush at the end.
Boot the target machine from it
Use the one-time boot menu — usually
F12,F9,EscorOptiondepending on the vendor. Pick the entry prefixed UEFI if two appear.
Doing it from Linux
WoeUSB-ng handles the file-copy path including the oversized file. A typical invocation, with the device
path confirmed by lsblk beforehand:
# confirm which device is the stick before running anything
lsblk -o NAME,SIZE,MODEL,TRAN
sudo woeusb --device Win.iso /dev/sdX --target-filesystem NTFS
The alternative is an image loader: install it on the stick once, copy the Windows ISO across as a file, and let the menu handle the rest. That also leaves room for other images on the same drive.
Common stumbles
| What you see | What it usually means |
|---|---|
| "The file is too large for the destination file system" | FAT32 and an oversized install image — let the tool split it or use NTFS |
| Drive missing from the boot menu | Wrong partition scheme for the firmware mode, or the drive is NTFS with no driver shim |
| "This PC can't run Windows 11" | Firmware requirements — TPM, Secure Boot or CPU generation. Check the machine's specification against the release requirements |
| Setup cannot find drivers for the drive | Storage controller driver missing; fetch it from the machine vendor and load it during setup |
| Install starts, then fails partway | Verify the ISO checksum and the health of the USB stick before retrying |