First day cover ·
Rufus 4.16 works around a UEFI firmware bug and adds faster USB detection
Rufus 4.16 avoids a UEFI NTFS firmware flaw and improves Windows setup options and USB speed detection up to 80 Gbps.


Rufus 4.16 tackles a firmware problem that can make some PCs misread files on NTFS USB drives during startup. The release also adds setup options for Windows, corrects a partitioning regression and improves detection of newer USB storage devices. For people building Windows installation media, the firmware workaround is the central change: it aims to make boot-time checks reliable on affected systems without waiting for a firmware update.
Developer Pete Batard published the release on GitHub. Rufus writes ISO images to USB drives and can prepare Windows 11 installation media with selected hardware requirement checks, including TPM and Secure Boot, bypassed. That makes it useful for users installing Windows on older equipment, though the new firmware fix addresses a separate problem that can appear before Windows starts.
A workaround for fragmented NTFS files
The issue sits in an AMI UEFI NTFS driver built into firmware used by systems from manufacturers including Asus, Gigabyte, Dell and Intel. The driver lets a computer read an NTFS-formatted USB drive during startup, before the operating system loads. When it encounters files split into small, scattered pieces on the drive, the faulty driver can return incorrect data.
That behavior can interfere with checks that happen during boot. Rufus 4.16 changes how it preallocates and writes files to reduce severe fragmentation on the USB drive, working around the conditions that trigger the driver bug. The adjustment is preventive: it does not repair the firmware itself. Batard says AMI has known about the flaw for two years and describes the affected computer count as millions, but the release notes provide no model by model list of systems that may be affected.
For users, the practical question is whether their machine relies on the faulty driver and whether a particular USB layout triggers the bad reads. Rufus’s approach addresses the storage arrangement it creates, which is useful when making new installation media. It cannot establish that every boot problem on an affected computer has the same cause, and the source material gives no estimate of how often the fault occurs in everyday use.
Windows setup options get more control
The Windows User Experience options in Rufus now include a way to restore the classic right-click context menu associated with Windows 10 on the installed system. That gives people preparing a clean installation a setup-time choice rather than requiring them to change the interface afterward.
The same section now accepts periods in local account names and fixes an issue that could duplicate time zones during installations in languages other than English. Rufus also stops using Group Policy as a way to suppress the system prompt asking whether a drive should be formatted. Together, the changes refine the setup process for people who use Rufus to customize Windows installation media, especially when preparing systems with non-English settings.
USB detection covers speeds up to 80 Gbps
Rufus 4.16 improves its identification of USB storage devices, including USB 3.2 at 20 Gbps, USB 4.0 at 40 Gbps and USB 4.1 at 80 Gbps. That helps users see which connection class Rufus detects when they attach a drive, though the listed interface speed alone does not establish the drive’s actual transfer rate. Real performance also depends on the drive and the computer’s port.
The change follows USB detection work that began in the beta release. For anyone choosing a port or checking whether a fast external drive is being recognized as expected, clearer interface identification can make troubleshooting easier. It still isn’t a speed test: Rufus reports the device category, not measured read or write results.
Other fixes in the release
The “Write as ESP” function had a regression that could consume the entire drive instead of creating the intended 1 GB partition. Version 4.16 corrects that behavior. The “Silent” installation option has also been adjusted so it won’t be applied when its required dependencies are missing, and the bundled GRUB software has been updated to version 2.16.
For most Rufus users, these fixes are smaller than the UEFI workaround, but they improve specific parts of the media creation process. The key takeaway is to use Rufus 4.16 when creating new installation drives if you want its updated fragmentation handling and USB identification. The firmware defect itself remains in the affected systems, so the workaround’s value depends on how those machines handle the files Rufus writes.