Rufus 4.16 Beta Fixes a Widespread UEFI NTFS Bug and Improves USB Device Reporting
The latest Rufus beta works around a flaw in an AMI UEFI NTFS driver that can read incorrect data from fragmented files. It also improves the way the utility identifies modern USB 3.2 and USB4 devices.
What Is New in Rufus 4.16 Beta?
Rufus is a free, open-source Windows utility for formatting USB flash drives and creating bootable installation media from ISO images. Administrators and enthusiasts commonly use it to prepare Windows installers, Linux distributions, recovery environments, and firmware utilities.
Version 4.16.2434 Beta, published on October 30, 2026, focuses on a UEFI NTFS compatibility workaround and more accurate reporting of high-speed USB devices. The release also includes fixes for runtime media validation, Windows installation customization, partition handling, localization, and security vulnerabilities.
UEFI NTFS workaround
Writes files contiguously to NTFS media to avoid the affected AMI firmware driver’s fragmented-file read bug.
Modern USB reporting
Recognizes and reports USB 3.2, USB4 and USB4 Version 2.0 device capabilities.
Boot-media validation
Fixes an issue involving updated CA 2023 files during runtime UEFI media validation.
Additional maintenance
Includes partition, installation-option, localization, component-update and security fixes.
Understanding the AMI UEFI NTFS Bug
The headline issue involves an AMI UEFI NTFS driver identified as version 0x10000. According to Rufus developer Pete Batard, this driver is present in firmware used by multiple PC and motherboard vendors. The Neowin report names Asus, Gigabyte, Dell and Intel among the manufacturers whose systems may use firmware containing the affected driver.
Why fragmented files trigger the problem
NTFS stores file data in clusters. When a volume has enough free space, a file may be stored in one continuous run of clusters. On a fragmented volume, however, parts of the same file can be distributed across different, non-contiguous locations.
The reported AMI driver can return incorrect data when reading certain fragmented files. In the investigation described by Neowin, files were intact and their MD5 checksums matched when checked from Windows or Linux, but checksum validation from the UEFI environment produced errors. Further investigation reportedly showed the firmware driver reading clusters that did not belong to the requested file.
Why this matters for bootable USB drives
UEFI firmware must access boot files before an operating system loads. If firmware reads incorrect data from installation media, runtime validation can fail even though the files appear healthy when inspected from a running operating system. That can make troubleshooting confusing: the same media may pass checks in Windows or Linux but fail when validated by firmware.
How Rufus Works Around the Problem
Rufus 4.16 beta introduces a workaround that writes files contiguously to NTFS media. By avoiding fragmentation in the relevant file layout, Rufus aims to prevent the affected AMI driver from following the faulty read path.
Neowin describes the approach as similar to a technique used by 7-Zip since version 17.0. The key point is that Rufus is working around the firmware driver defect rather than repairing the driver installed in a PC’s motherboard firmware.
Prepare a suitable USB drive
Back up any files on the USB device. Creating bootable media normally repartitions or formats the selected drive and destroys its existing contents.
Obtain a trusted ISO image
Download the Windows or Linux ISO from its official publisher. Verify its published checksum when one is provided.
Run Rufus 4.16 beta
Download the beta from the official Rufus GitHub releases page. Connect the USB drive and confirm that Rufus has selected the intended device.
Configure and create the media
Select the ISO, review the partition scheme and target-system settings for the computer you intend to boot, and start the write process. Read the confirmation prompt carefully before proceeding.
Validate the result
Allow Rufus to finish, safely eject the drive, and test it on a non-production system where possible. If runtime UEFI validation is enabled and supported for the selected image, use it as an additional check.
The contiguous-write workaround is handled by Rufus; there is no separate Windows registry change or motherboard firmware setting described as necessary for this fix.
Improved USB Device Reporting
Rufus 4.16 beta also improves detection and reporting for newer USB devices. The release notes list the following interface generations and headline link rates:
| USB generation | Reported headline speed | Practical note |
|---|---|---|
| USB 3.2 | 20 Gbps | Rufus can now report devices in this higher-speed category. |
| USB4 | 40 Gbps | Improved identification helps distinguish modern USB4 hardware. |
| USB4 Version 2.0 | 80 Gbps | Rufus adds reporting for this newer capability. |
These figures describe interface capabilities, not guaranteed file-copy speeds. Actual throughput depends on the USB device, host controller, cable, port configuration, protocol overhead, and workload. A drive advertised for a high USB link rate may still be limited by its internal flash memory or controller.
Other Fixes and Changes in Rufus 4.16 Beta
The beta changelog includes several additional changes beyond the headline NTFS and USB reporting work:
- CA 2023 validation: Fixes updated CA 2023 files not being considered during runtime UEFI media validation.
- Silent installation: Fixes a case where the Silent installation option could be applied even when all required dependencies were not met.
- Write as ESP: Fixes a regression that caused the operation to use the whole drive instead of the expected 1 GB partition.
- Localization: Fixes duplicate WUE time-zone entries for non-English locales and restores dots in local usernames.
- Context menu: Adds an option to restore the classic right-click context menu through the Quality of Life improvements option.
- Format prompt: Removes the problematic use of Group Policy to disable the Windows “Do you want to format this drive?” prompt.
- Partition handling: Improves raw image partition remounting.
- Boot components: Updates embedded GRUB to 2.16 and updates libcdio.
- Secure Boot revocation data: Updates the official DBX URLs following changes by Microsoft.
- Security: Addresses multiple reported vulnerabilities listed in the project changelog.
For the authoritative, complete list, check the release notes accompanying the exact build you download. Beta changelogs can change as the project publishes newer builds.
Download Rufus 4.16 Beta
Rufus 4.16.2434 Beta is available through the Rufus project’s official GitHub releases page. Neowin also published a software listing for the beta.
Rufus 4.16.2434 Beta
Version: 4.16.2434 Beta
Release date: October 30, 2026
License: Open source
Purpose: Create and format bootable USB media
Best Practices for Creating Bootable USB Media
- Download Rufus from its official project website or GitHub repository, not from repackaged download portals.
- Use ISO files from Microsoft, a Linux distribution publisher, or another trusted software vendor.
- Double-check the selected USB device by its name and capacity before starting.
- Keep a backup of important USB contents because the creation process can erase the drive.
- Match the partition scheme and target system to the computer’s boot configuration, typically GPT/UEFI for modern systems.
- Test installation media before a planned deployment or recovery operation.
- Do not treat a reported USB interface speed as a promise of real-world transfer performance.
Final Thoughts
Rufus 4.16 beta addresses an unusual but potentially widespread compatibility problem in certain AMI UEFI NTFS drivers. Its contiguous-file-writing workaround is intended to make runtime UEFI media validation more reliable on systems affected by the defect, without requiring users to wait for motherboard firmware updates.
The improved USB 3.2 and USB4 reporting is a useful quality-of-life enhancement for technicians who work with modern storage devices. Alongside the additional bug fixes and security updates, this makes Rufus 4.16 beta worth testing—while remembering that beta software should be validated before it becomes part of a production deployment workflow.
Share This Article
References and Sources
- Neowin — Rufus brings improved USB reporting, fixes NTFS bug affecting “millions” of PCs
- Neowin — Rufus 4.16.2434 Beta release listing and changelog
- Rufus — Official GitHub releases
- Rufus — Official project changelog
- Rufus — Official website
This article is based on the Rufus 4.16.2434 beta changelog and the reporting available on October 31, 2026. Product behavior and release details may change in subsequent builds.
