Rufus

Overview

Rufus is one executable, roughly the size of a photograph, and it does one job better than tools hundreds of times larger. Point it at an image and a USB stick, press start, and a few minutes later you have media that boots. It has become the default recommendation for the simple reason that it is consistently faster than the alternatives and it does not produce sticks that fail at the boot menu.

The interface fits in one window with no wizard. It detects the attached removable drives, reads the image you select and populates the partition scheme, target system, file system and cluster size with correct defaults derived from the image itself. Most people never change any of it. The controls are there because on unusual hardware the defaults occasionally are not right, and having them exposed is the difference between solving that in thirty seconds and giving up.

The system installer options are what pushed it from useful to essential. Writing a current system installer optionally applies changes during the write: removing the hardware requirement checks, bypassing the account requirement at first boot, disabling data collection prompts, setting the regional options in advance, and disabling automatic drive encryption. These are applied as answer file entries rather than as modifications to the image itself, so the installer is otherwise untouched.

It also handles the awkward cases. Images larger than the file size ceiling of the older file system are split automatically so the stick still boots. Persistent storage can be allocated on live images so changes survive a reboot. Bad block checking runs several passes over cheap or suspect sticks before writing. The whole thing is portable, needs no installation, and can be kept on the same stick it writes to.

Key Features

• Single portable executable of a few megabytes with no installation required
• Automatic detection of removable drives with correct defaults derived from the selected image
• Partition scheme, target system, file system and cluster size overrides for awkward hardware
• System installer options applied as answer file entries rather than image modifications
• Hardware requirement check removal and account requirement bypass for current installers
• Regional and data collection preferences set in advance during the write
• Automatic file splitting for images exceeding the older file system size ceiling
• Persistent storage allocation on live images so changes survive a reboot
• Multi pass bad block checking before writing to suspect sticks
• Consistently faster writing than the larger alternatives

What Changed in This Build

• Installer option list updated for the current system releases
• Improved detection of drives behind certain USB controllers
• Faster write on high speed sticks with better buffering
• Fixed a rare failure when writing images with unusual partition layouts

System Requirements

Processor	Any x86 or x64 processor
Memory	512 MB
Storage	5 MB for the executable, plus a USB stick of appropriate size
Operating system	Windows 8 or newer
Permissions	An administrator account is required for direct drive access

Release Details

Full title	Rufus
Version string	4.15.2396
Publisher	Akeo
Category	Utilities
Licence	Open source, free
Platform	Windows 8 through 11, 32 and 64-bit
Interface language	Multilingual, 38 interface languages
Archive size	1.4 MB
Mirrors	4 active, all reporting online
Listed	refreshed 2 months ago, checked again 40 minutes ago

Installation Notes

• The target stick is erased completely. Check twice that the selected drive is the one you meant before pressing start.
• Leave the defaults alone unless a machine refuses to boot from the result. They are derived from the image and are usually correct.
• Run bad block checking on a cheap or unfamiliar stick. A stick that fails mid install wastes far more time than the check does.

Before You Start

Read the notes above before running setup. Most of the problems people write in about are covered there, and almost all of them come down to an older version of the same software still being installed, a graphics driver that predates the release, or a security suite quarantining part of the package mid install.

There is no archive password on this or any other entry in the library. If something you downloaded elsewhere claims to come from here and asks for one, it did not come from here. Nothing on this site is behind a survey, a shortener or a countdown either.

If the entry does not match what the page describes, say so on the contact page and include the version string from the release details table. Reports naming a specific version get checked first because the checker can reproduce them straight away.

Frequently Asked