Rufus, the indispensable bootable USB creation tool for Windows users, rolled out its final update on June 30, 2026. Version 4.15 arrives as a swan song from developer Pete Batard, packing critical fixes for Windows 11 installation headaches, resolving long-standing ARM64 boot crashes, and even adding experimental support for RISC-V 64 processors. For a utility that has become synonymous with hassle-free Windows installations, this release marks both a culmination and an end of an era.
Batard confirmed on the project's GitHub repository that 4.15 would be the last planned release, citing a desire to move on after more than a decade of maintenance. The decision sent ripples through the Windows community, where Rufus had cemented itself as the preferred alternative to Microsoft's own Media Creation Tool, especially for users needing to bypass Windows 11's stringent hardware requirements.
Windows 11 Customization Bugs Finally Squashed
Among the most celebrated fixes in version 4.15 is the restoration of reliable Windows 11 customization options. Since Microsoft tightened the screws on hardware checks in Windows 11 24H2 and subsequent builds, Rufus has been a lifeline for users installing the OS on unsupported hardware. However, recent Windows 11 updates had broken Rufus’s ability to seamlessly disable TPM 2.0, Secure Boot, and RAM checks during USB creation.
Specifically, users reported that the “Extended Windows 11 Installation” options—which strip out the compatibility checks and optionally create a local account—would sometimes fail silently when crafting installation media from newer ISOs. This left many stuck at the dreaded “This PC can't run Windows 11” screen despite using Rufus. The 4.15 update resolves these regressions by updating the internal scripting engine to handle Microsoft’s latest installation metadata structures. Batard noted in the changelog that the fix involved parsing the install.wim index more robustly, ensuring that the bypass commands are injected correctly even in multi-edition ISOs.
Additionally, the update addresses a bug where custom unattended answer files would not be applied correctly when using the “Silent Install” mode. This feature, popular among IT administrators for automating deployments, had broken in version 4.14 due to a path handling error. With 4.15, the /silent command-line switch and the GUI’s silent installation checkbox now work as expected, correctly merging user-provided XML answer files with Rufus’s own bypass modifications.
UEFI:NTFS Crashes on Snapdragon X ARM64 Systems
A particularly thorny issue fixed in this release involved UEFI:NTFS boot crashes on Snapdragon X-powered ARM64 devices. Rufus has long used its custom UEFI:NTFS driver to allow booting from NTFS-formatted USB drives on UEFI systems, a necessity for Windows installation images that exceed the FAT32 file size limit. However, on Qualcomm’s Snapdragon X Elite and X Plus platforms—which have gained traction in the Windows-on-ARM ecosystem—the driver would often cause a blue screen or hang during early boot.
The culprit was a memory alignment bug in the UEFI:NTFS driver when running on ARM64 firmware, which triggered translation faults in the pre-boot environment. Batard rewrote parts of the driver in pure assembly for ARM64, optimizing the page table setup to avoid the crashes. The fix also benefits other ARM64 devices, such as those running Windows on Ampere Altra or Microsoft’s custom SQ processors, though the Snapdragon X series was the primary motivation.
Community testing on the Windows Insider ARM64 forum confirmed that Rufus 4.15 now boots reliably on devices like the Surface Pro 10 5G and the Lenovo ThinkPad X13s, both of which had exhibited the UEFI:NTFS crash with previous versions. This fix alone makes the update essential for anyone managing Windows deployments on ARM hardware.
Experimental RISC-V 64 Support
In a surprising forward-looking move, Rufus 4.15 introduces experimental support for creating bootable media for RISC-V 64 systems. While RISC-V consumer hardware is still nascent, the architecture has been gaining momentum in server and embedded spaces, and Microsoft has hinted at a Windows port for RISC-V through its Project Optima initiative.
Rufus now includes a basic bootloader and partition scheme suitable for RISC-V 64 platforms that adhere to the UEFI specification. The tool can write system images to USB drives with the correct GUID Partition Table (GPT) layout and populate the EFI system partition with a RISC-V compatible bootloader. Batard cautioned that this feature is highly experimental and intended primarily for developers working on RISC-V firmware and OS ports. It lacks the extensive customization options available for x64 and ARM64, and users will need to supply their own UEFI firmware image.
Nonetheless, the addition signals Batard’s faith in a multi-architecture future, even as he steps away from the project. It also underscores how Rufus has evolved from a simple Windows USB tool into a universal bootable media creator supporting Linux ISOs, Windows To Go, and now emerging ISAs.
Silent Installation Failures Corrected
IT professionals and power users who rely on Rufus’s command-line interface for automated scripting will appreciate the fixes to silent installation failures. In version 4.14, the /silent flag would occasionally exit without creating the USB drive if certain prerequisite checks—like the presence of the Windows ADK—were not met, but it would not provide clear error codes. Version 4.15 adds proper error handling and returns distinct exit codes so that scripts can react accordingly. The GUI also now correctly disables the silent installation checkbox when incompatible options (such as persistent storage for Linux ISOs) are selected, preventing user confusion.
The End of an Era: Pete Batard’s Farewell
Pete Batard’s decision to end active development on Rufus is the emotional core of the 4.15 release. In a README update, he stated that after more than 13 years and countless late-night debugging sessions, he felt the tool had reached a state of maturity where it could “retire gracefully.” He acknowledged the community’s support and the role Rufus played in democratizing Windows installations, particularly during the contentious Windows 11 rollout.
Batard’s departure does not mean Rufus will disappear immediately. The source code remains open-source under the GPLv3 license, and he encouraged the community to fork and continue development if desired. However, without its tireless maintainer, the tool will inevitably lag behind new Windows releases and hardware quirks.
Community Reaction and Immediate Impact
On the Windows forum that first broke the news, reactions ranged from gratitude to anxiety. Long-time users celebrated the tool’s reliability, with many recounting how Rufus had rescued them from bricked PCs or botched installations. Others expressed concern about the lack of a clear successor, especially as Microsoft’s own Media Creation Tool remains limited in functionality.
Some forum members suggested alternatives like Ventoy, which offers a different approach to multi-boot USB drives, but acknowledged that Ventoy lacks the deep Windows-specific customization that Rufus provides. For now, IT administrators are stockpiling the 4.15 release and hoping that critical bugs in future Windows ISOs won’t break its functionality.
What This Means for Windows 11 Installations
Rufus has been one of the few reliable ways to bypass Windows 11’s hardware requirements without resorting to manual registry hacks during installation. With the tool now in maintenance-only mode, any future changes Microsoft makes to the installation process could render the bypass methods ineffective. Users who depend on these workarounds should keep a copy of Rufus 4.15 and compatible Windows ISOs archived.
For those running Windows 11 on officially unsupported hardware, the end of Rufus development is a stark reminder that Microsoft could tighten enforcement at any time. However, with version 4.15, at least the current generation of bypasses is in a stable state.
Performance and Reliability Tweaks
Beyond the headline fixes, version 4.15 includes several under-the-hood improvements. The USB drive detection engine now better handles devices that report zero media size, preventing rare crashes. The progress bar during ISO extraction is more accurate, and the integrity check for downloaded ISOs (when using the built-in script) has been updated to support SHA-256 hashes in addition to SHA-1. A memory leak that occurred when repeatedly writing large images has been plugged, improving long-term stability for enterprise users preparing multiple USB drives in succession.
How to Get Rufus 4.15
Rufus is available for download from the official website at https://rufus.ie, as well as from its GitHub releases page. The 4.15 installer includes both the standard and portable versions, and the application remains lightweight with no telemetry or bundled software. Windows users on x64, x86, and ARM64 architectures can download the appropriate executable. The RISC-V 64 support is currently limited to the ARM64 build with a runtime switch, reflecting its experimental nature.
Looking Ahead: The Legacy of Rufus
Rufus leaves behind a towering legacy. It demonstrated that a single developer, armed with deep knowledge and a commitment to quality, could create a tool that surpassed corporate offerings. From its early days as a replacement for the discontinued HP USB Disk Storage Format Tool, to its pivotal role in the Windows 11 era, Rufus has been a constant companion for system builders and tinkerers.
The addition of RISC-V 64 support in its final release feels poetic: a nod to the future even as the project closes its own chapter. Batard’s work will likely inspire forks and new tools, but the original Rufus will be remembered for its elegance, speed, and trustworthiness.
For now, Windows enthusiasts can breathe easier knowing that the last official Rufus release fixes critical bugs that have plagued recent installations. As the community digests the news, the advice is clear: download 4.15, keep it safe, and maybe raise a toast to the developer who made deploying Windows a simple click away.