The TrueNAS team is pleased to release TrueNAS 25.10-RC.1!
Early Release Software
Early releases of a major version are intended for testing and feedback purposes only. Do not use early-release software for critical tasks.
25.10-RC.1 Notable changes
Enhances remote syslog configuration to support up to two servers (NAS-137315). Updates the Syslog configuration options in System > Advanced Settings to allow configuring multiple syslog servers with individual transport and TLS certificate options.
Improves NVMeoF target configuration with automatic port defaults (NAS-137394, NAS-137395). Sets port 4420 as the default for NVMe over Fabric targets, eliminating the need for manual port configuration.
Clarifies VM secure boot configuration as create-only setting (NAS-137397). Removes secure boot option from VM edit form as this setting can only be configured during initial VM creation.
Fixes upgrade blocking issue for systems without BIOS partition (NAS-137352). Resolves traceback during 25.10 upgrades on systems originally deployed with TrueNAS CORE that lack a BIOS partition.
Fixes SMB service hanging during Windows client file operations (NAS-137095). Resolves issue where Windows clients became unresponsive during file moves and editing operations, requiring manual thread termination.
Fixes incorrect disk temperature threshold alerts (NAS-137385). Resolves issue where critical temperature alerts were triggered incorrectly when threshold was set to 0 degrees Celsius.
Improves password manager compatibility with WebUI login screen (NAS-136335). Resolves issue where password managers like Bitwarden and Dashlane failed to automatically recognize and fill login credentials.
Consolidates Users page interface (NAS-137443). Removes legacy Users page and renames Users (WIP) to Users for a cleaner interface experience.
Fixes network usage units display on Applications page (NAS-137428). Corrects network usage units from lowercase ‘b’ to capital ‘B’ (B/s, kB/s, MB/s) to properly indicate bytes per second.
Fixes UI Bug Reporting feature “FAILED: This TrueNAS build is experimental” error (NAS-137445). Resolves issue preventing bug report submissions through the UI.
Fixes incorrect time sort for frequency on Cloud Sync Tasks screen (NAS-137096).
Fixes Users page showing “can not retrieve response” error due to invalid email address (NAS-137198).
Fixes Virtual Machines page not refreshing properly (NAS-136973).
Adds VM disk image import and export capabilities (NAS-137334, NAS-137335). Enables importing disk images (QCOW2, QED, RAW, VDI, VHDX, and VMDK formats) during VM creation and exporting VM disks to portable image formats, streamlining VM migration and setup processes.
Improves Virtual Machine configuration performance (NAS-136937). Prevents libvirt service from starting automatically when browsing VM creation options, improving system responsiveness.
Enhances session security with improved random number generation (NAS-137318). Uses SSL-based random number generator for creating session IDs, improving overall cryptographic security.
Fixes an issue where the ACL editor ignored unchecked “Apply Owner” and “Apply Group” checkboxes and always applied owner/group changes recursively, potentially causing unintended ownership changes (NAS-137378).
The PGP public keys for the TrueNAS Security Team have been renewed and published to the TrueNAS Security Advisories.
Filed a small UI bug with replication tasks. It’s existed since 25.04, or maybe earlier, but I kept forgetting to submit it.
Also, is there a post upgrade script or something that runs? I noticed an elevated level of IOwait on my overall CPU usage, but I can’t seem to correlate it to anything.
Only stuck around for a couple hours. It was like 3-5% IOwait, where normal is 0-1%. What was odd is nothing seemed to be generating IO as far as I could tell. I noticed it after I ran a new replication job, but it complete for an hour before before the IOwait dropped that couple percent back to normal. I tried rebooting after that to see if it was something that appeared after a cold boot, but nothing showed up.
Not bad or even noticeable to most people, but it was a “huh, that’s odd…”
Also just tested the installation of a Win11 VM - worked flawlessly with all-VirtIO devices.
The only thing that’s still annoying is the Spice web viewer which freezes after a few seconds of not using it.
I’d guess the UI team spends a fair bit less time running on mobile browsers to notice little details like this, so any issues you do see are probably worth a bug report.
Use your head:
They made it impossible in the GUI to disable secure boot AFTER the VM is created to avoid people disabling it and then complaining that their windows VM “stopped booting”.