The USB that refuses to boot
You downloaded the Fedora ISO, plugged in a 16 GB flash drive, and copied the file over. You rebooted, selected the USB in the BIOS, and got a black screen with a blinking cursor. The drive isn't broken. The ISO isn't corrupted. Windows just copied a disk image file to a filesystem instead of writing the raw sectors. You need to burn the image, not copy it.
Why raw ISO files don't just copy-paste
An ISO file is a complete disk image. It contains the filesystem, the bootloader, the partition table, and the kernel. When you drag it to a USB drive in Windows Explorer, you are treating it like a regular document. The drive ends up with a single file named Fedora.iso sitting on a FAT32 or NTFS volume. The BIOS looks for a boot sector at the very beginning of the drive. It finds a Windows filesystem header instead. It gives up.
Writing a bootable USB means overwriting the drive's partition table and writing the ISO's raw bytes directly to the hardware. This process destroys everything on the drive. Back up your data first. The operation is irreversible once the write begins.
The reliable path: Fedora Media Writer
Fedora provides a dedicated tool for Windows. It handles partition alignment, writes the image, and verifies the checksum automatically. Download it from the official Fedora website. Run the installer. Insert your USB drive. The tool will detect it. Select your Fedora edition. Click Next. The tool will format the drive, write the image, and verify it. Wait for the success message. Safely eject the drive.
The tool abstracts away the low-level disk operations. It reads the ISO, calculates the correct block alignment for UEFI and Legacy BIOS compatibility, and writes the data in optimized chunks. It also runs a SHA-256 verification pass immediately after writing. If the checksum mismatches, the tool flags the drive as unbootable. This saves you from troubleshooting a corrupted bootloader later.
Run the verification pass. A mismatched checksum means a bad download or a failing flash drive, not a Fedora bug.
The terminal path: PowerShell and dd
If you prefer the terminal or need to script the process, PowerShell can write the image directly. Windows does not expose raw disk access through standard drive letters. You must use the device path syntax. The \\.\X: format tells Windows to bypass the filesystem layer and talk directly to the hardware.
Here's how to identify the correct drive letter and write the image safely.
# List all fixed and removable disks to find the USB drive letter
Get-Volume | Where-Object DriveType -eq 'Removable' | Select-Object DriveLetter, FileSystemLabel
# Write the ISO to the raw disk device. Replace X with your actual drive letter.
# bs=4M sets the block size to 4 megabytes for faster sequential writes.
# status=progress shows a live percentage so you know the process hasn't hung.
dd if="C:\Users\YourName\Downloads\Fedora.iso" of=\\.\X: bs=4M status=progress
The dd command reads the input file block by block and writes it to the output device. The bs=4M flag is important. Default block sizes are often too small for modern flash drives. A 4 megabyte block size reduces CPU overhead and matches the internal page size of most USB controllers. The status=progress flag prevents you from staring at a frozen terminal wondering if the write stalled.
PowerShell's dd is not a built-in Windows command. It comes from the community dd module or through WSL. If your system does not recognize dd, install the module first or use the Windows Subsystem for Linux. The syntax remains identical across environments.
Flush the write cache before unplugging. Windows delays physical writes to optimize performance.
Verify the drive before you reboot
Never trust a silent success message. Flash drives fail silently. Bad sectors get masked by the controller. A corrupted bootloader will drop you into a GRUB rescue prompt or a kernel panic. Verify the written data matches the source ISO.
Here's how to calculate the SHA-256 hash of the raw USB drive and compare it to the official checksum.
# Calculate the SHA-256 hash of the raw USB device. Replace X with your drive letter.
# The -Algorithm flag ensures you get the same hash Fedora publishes.
$usbHash = Get-FileHash -Path "\\.\X:" -Algorithm SHA256
# Output the hash for comparison with the official Fedora checksum file
$usbHash.Hash
Compare the output string to the .sha256 file downloaded alongside the ISO. If the strings match exactly, the drive is byte-for-byte identical to the source image. If they differ, the write failed, the drive has bad sectors, or the ISO download was interrupted. Re-download the ISO and try a different USB drive.
Run the hash check before you reboot. A mismatched drive will waste an hour of troubleshooting.
Common pitfalls and what the error looks like
The most frequent failure is selecting the wrong drive letter. dd does not ask for confirmation. It writes exactly where you point it. If you type \\.\C: instead of \\.\X:, you will overwrite your Windows system partition. The terminal will not stop you. Double-check the of= parameter. Triple-check it.
Another common issue is a drive that appears to finish writing but refuses to boot. The terminal prints records in and records out without errors, yet the BIOS ignores the USB. This usually means the drive letter mapping is wrong or the USB controller is in a legacy mode that conflicts with UEFI. Check your BIOS settings. Enable UEFI boot. Disable Secure Boot temporarily if the Fedora installer complains about unsigned modules. Fedora ships with secure boot support, but third-party drivers or custom kernels can trigger a SECURE BOOT VIOLATION message.
If you see Access to the path '\\.\X:' is denied, you are running PowerShell as a standard user. Raw disk writes require administrator privileges. Right-click the PowerShell icon and select Run as administrator. The elevated session will have direct hardware access.
If the write completes but the hash check fails, your flash drive is physically degraded. Cheap USB drives often report incorrect capacity or mask bad blocks. Replace the drive. Do not attempt to repair it with disk utilities. The controller firmware is already hiding the damage.
Check the drive letter twice. One wrong character wipes your host system.
Pick your tool
Use Fedora Media Writer when you want a guided process that handles partition alignment and checksum verification automatically. Use PowerShell and dd when you need to script the image creation or prefer direct terminal control. Use Rufus when you are working on older hardware that requires specific partition scheme adjustments like MBR for BIOS or GPT for UEFI. Stick to the official ISO when you need the exact upstream experience without third-party bootloader modifications.
Trust the checksum. A verified hash guarantees the bootloader and kernel are intact.