Unraid 7.3.0 Stable Now Available
Internal Boot, Critical Security Updates, and a stack of improvements across Docker, storage, and virtualization come to Unraid.
Internal Boot + New Licensing Options
Flash drives have always been how Unraid boots and how your license is validated. That worked well for a long time, but USB flash reliability has been on a steady decline, and you end up with a single point of failure and no good redundancy options. With 7.3.0, that changes.
Internal Boot lets you install and boot Unraid from an internal drive: NVMe, SSD, eMMC, or an existing storage device. Boot times are faster, the system is more resilient, and it unlocks licensing options that weren't possible before. For users who want an extra layer of resilience, internal boot also supports a mirrored boot pool: two devices in a ZFS mirror, so Unraid continues running if one device fails. Replace the failed device through the normal drive assignment flow to restore the mirror.
Existing users: nothing changes unless you want it to. Flash boot with flash-based licensing remains fully supported. If you do want to move to Internal Boot, you have two paths:
Path 1: Internal Boot + Flash Licensing. Boot internally and leave your licensed flash drive connected as the licensing anchor. Faster boots, better reliability, no changes to how your license works. The right move if your system doesn't have TPM 2.0, or you simply don't want to use it.
Path 2: Internal Boot + TPM-Based Licensing. If your system was built in 2019 or later, your motherboard likely already has TPM 2.0 support, often enabled through firmware with no dedicated chip required. With TPM-based licensing, your license is anchored to the motherboard. Pull the flash drive entirely and your license stays put. The most streamlined long-term option for supported hardware, but a choice, not a requirement. Many older motherboards without onboard TPM include a TPM header where an inexpensive add-on module can be installed.
One important distinction: Internal Boot (where Unraid boots from) and licensing (what hardware your license is tied to) are separate choices. You can get the full performance and reliability benefits of Internal Boot while keeping flash-based licensing, which is especially relevant for older systems without TPM.
Unraid 7.3: Convert Your Existing Server to Internal Boot
New users don't need to think about any of this up front. Unraid automatically selects the best available licensing option based on your hardware: TPM if it's detected, flash-based if not.
Bottom line: faster boots, fewer failure points, more control over how your license is held. Your old setup still works. This is addition, not replacement.
Unraid 7.3: Set Up a New Server with Internal Boot
Have Internal Boot Questions?
See our Internal Boot FAQ or TPM Licensing FAQ for more details!
Better Onboarding
New users getting started with 7.3.0 will be greeted by a completely redesigned onboarding wizard that gets your server configured and ready in about three minutes. It walks you through server name, time zone, language, SSH access, theme, boot method selection, and plugin installation in a clean step-by-step interface, with a summary screen to review everything before it's applied.
The boot method choice (USB/Flash Drive or Internal Boot) is built directly into the flow, so new users encounter it from day one rather than discovering it later buried in settings.
Existing users switching to Internal Boot can access the same wizard under Tools → Onboarding Wizard.
Security
This release includes several security fixes. Upgrade is recommended.
The 7.3 kernel patches two local privilege escalation vulnerabilities: Copy Fail (CVE-2026-31431) and Dirty Frag (CVE-2025-43284), the latter previously addressed in 7.2.6. Users upgrading from 7.2.5 or earlier get both fixes in one update.
The release also includes package-level security updates to GnuTLS, Info-ZIP, telnet, and X.Org Server. bind is updated from 9.20.13 to 9.20.20.
Docker: Smarter Networking
Docker is updated from 29.3.1 to 29.4.3.
The bigger improvement is a new optional fixed MAC address field in Docker templates. Containers that need a stable network identity across restarts (for DHCP reservations, router or firewall rules, switch ACLs, or monitoring) can now have a consistent MAC address that doesn't change. Container MAC addresses are also visible in Advanced View alongside existing network and IP information.
Legacy --mac-address= values from Extra Parameters are automatically migrated to the new fixed MAC field where it's safe to do so, leaving templates unchanged when networking is still owned by Extra Parameters.
Also fixed: an issue where some Docker containers on VLAN networks could fail to receive DHCP or use the expected static network configuration after upgrading from 7.2.4 or 7.2.5.
Storage and ZFS
ZFS is updated to 2.4.1, and this release brings meaningful quality-of-life improvements for ZFS users.
Corrupted files are now surfaced in ZFS pool status. If a pool has files with checksum errors, they'll be visible in the WebGUI rather than invisible until a scrub.
ZFS ARC max size is now a user-facing control under Settings → Disk Settings → Tunable (zfs_arc_max). Previously, this was configured through a custom ZFS driver parameter in the ZFS settings for your pool, a less visible location that required manual editing. It's now a proper setting in Disk Settings. Unraid will attempt to migrate your existing value automatically, but if you had a custom ARC max configured, it's worth confirming the new Tunable reflects your expected value after upgrading.
The ZFS pool replacement workflow is fixed for cases where a dropped device was marked REMOVED. This could previously leave a pool degraded with a stale state or trigger repeated overwrite warnings. Reserved ZFS name prefixes (mirror, raidz, draid, spare) are now blocked at pool creation time to prevent downstream failures. ZFS pools no longer wake unnecessarily every 24 hours in affected configurations. Drives no longer spin down during parity copy as part of a parity swap. Overall pool and drive health visibility is improved, with smarter duplicate drive detection and clearer messaging.
Ready to jump to Unraid 7.3.0?
For a step by step guide to upgrading, see our onboarding guide.
File Manager
The File Manager got a meaningful performance pass. Same-filesystem move operations are faster, upload behavior is improved, and the overall UI is snappier. A number of long-standing edge cases are also resolved: directories with double quotes in their names, path handling involving /sub/ segments, scrollbar interaction freezing during copy or move operations, empty directories being dropped during renames, and several other move and rename edge cases. Styling on the Main tab now correctly follows the selected theme.
Virtualization
QEMU is updated to 10.2.2 and libvirt to 12.2.0, with a refreshed OVMF firmware package: a significant step forward for the VM stack.
Deprecated VM machine types are now updated automatically during startup, so older VMs no longer fail with unsupported QEMU machine-type errors after upgrading. VMs created from user-defined templates no longer inherit the source VM's MAC address. VM snapshot commit cleanup now correctly updates snapshot metadata. System Devices visibility and VM template workflows are improved, as are custom VNC port validation and defaults.
Hardware and Networking
The kernel configuration is updated for broader AMD XDNA and ACP support. AMD NPU firmware, Intel Bluetooth firmware, Intel wireless firmware, and the amdxdna kernel module are included. Strix Point iGPU support for Docker workloads is fixed on affected systems.
One more thing: Tailscale now has a dedicated stub page in Settings, making the plugin easier to discover and install. If you're not already running Tailscale on your Unraid server, this is your nudge to do so!
WebGUI and System
A handful of fixes are here:
When no valid TPM or flash licensing device is detected, the licensing status message is now clearer about what's missing and why.
RAM display is fixed after a dmidecode unit label change caused incorrect readings. Time zone label and identifier issues in affected regions are resolved.
On the system side, WebGUI and API requests no longer unnecessarily spin up the full HDD array on affected systems. The built-in rclone configuration is now persisted across reboots rather than reset on each boot. The chassis serial number appears in System Info when the system firmware provides a valid value.
Smaller fixes: Discord notification formatting is corrected, and the Cooler Master Qube 500 case is now recognized in the case model list.
ReiserFS warnings and stale references are removed throughout, and reiserfsprogs is removed from the base distro.
Unraid 7.3.0 Stable
Important Release Links
-
Docs
Version 7.3.0 Release Notes
-
Bug Reports
Please help us by reporting bugs!
-
Forum Thread
Unraid 7.3.0 Stable Forum Thread
-
Discord
Discord Release Discussion
-
TPM Licensing FAQ
Have Questions on TPM Licensing?
-
Internal Boot FAQ
Internal Boot FAQs are answered here.
Try before you buy
Not sure if Unraid is right for you? Take Unraid for a test drive for 30 days—no credit card required.