Qubes OS 4.3.0-rc4 has been officially released, marking a significant milestone in the journey toward the final stable version of the operating system. This release features important updates, such as the upgrade of Dom0 to Fedora 41 and Xen to version 4.19. Users with older versions of Qubes OS may need to update their default templates to either Fedora 42 or Debian 13 to ensure compatibility.
In addition to these core enhancements, Qubes OS 4.3.0-rc4 introduces several new features aimed at improving user experience. Notable upgrades include a more efficient hardware setup process through preloaded disposables, which facilitates quicker virtual machine (VM) configurations, and a revamped New Devices API that allows for better management of hardware devices tied to system identity. The release also reinstates Qubes Windows Tools with enhancements, providing better functionality for users operating on Windows systems.
The testing phase is still in progress, with developers actively collecting bug reports and implementing necessary fixes. This iterative approach may result in additional release candidates before the stable version is finalized. Current feedback from testers indicates that this release could potentially be the last step before announcing Qubes OS 4.3 as stable.
For those interested in participating in the testing process, options include setting up Qubes OS from scratch on new hardware or upgrading an existing Qubes 4.2 installation using the "in-place update" method. Users are encouraged to back up their data before proceeding with the update to avoid any loss.
Additionally, for those utilizing Whonix within their Qubes OS environment, now is an opportune moment to upgrade the Whonix setup to align with the latest improvements and bug fixes.
In summary, Qubes OS 4.3.0-rc4 is available for testing, and the enhancements made in this release reflect a commitment to refining the user experience and system functionality, paving the way for a robust final version in the near future
In addition to these core enhancements, Qubes OS 4.3.0-rc4 introduces several new features aimed at improving user experience. Notable upgrades include a more efficient hardware setup process through preloaded disposables, which facilitates quicker virtual machine (VM) configurations, and a revamped New Devices API that allows for better management of hardware devices tied to system identity. The release also reinstates Qubes Windows Tools with enhancements, providing better functionality for users operating on Windows systems.
The testing phase is still in progress, with developers actively collecting bug reports and implementing necessary fixes. This iterative approach may result in additional release candidates before the stable version is finalized. Current feedback from testers indicates that this release could potentially be the last step before announcing Qubes OS 4.3 as stable.
For those interested in participating in the testing process, options include setting up Qubes OS from scratch on new hardware or upgrading an existing Qubes 4.2 installation using the "in-place update" method. Users are encouraged to back up their data before proceeding with the update to avoid any loss.
Additionally, for those utilizing Whonix within their Qubes OS environment, now is an opportune moment to upgrade the Whonix setup to align with the latest improvements and bug fixes.
In summary, Qubes OS 4.3.0-rc4 is available for testing, and the enhancements made in this release reflect a commitment to refining the user experience and system functionality, paving the way for a robust final version in the near future
Qubes OS 4.3.0-rc4 released
Qubes OS 4.3.0-rc4 has been released as another step towards the final stable version, introducing updates such as Dom0 switching to Fedora 41 and Xen being updated to version 4.19. Additionally, the developers have incorporated several new features, including improved hardware setup using preloaded disposables and a refreshed New Devices API for more control over managing hardware. The testing process is ongoing, with bug reports being gathered and fixes implemented before potentially releasing another RC if needed.
