Qubes OS 4.3.2-rc1 is available for testing

The first release candidate (RC) for Qubes OS 4.3.2 is now available for testing. This patch release aims to consolidate all the security patches, bug fixes, and other updates that have occurred since the release of Qubes 4.3.1.

What’s new in Qubes 4.3.2?

  • Default Fedora template upgraded to Fedora 44
  • kernel-latest upgraded to Linux 7.2
  • Numerous bug fixes

When is the stable release?

That depends on the number of bugs discovered in this RC and their severity. As explained in our release schedule documentation, our usual process after issuing a new RC is to collect bug reports, triage the bugs, and fix them. If warranted, we then issue a new RC that includes the fixes and repeat the process. We continue this iterative procedure until we’re left with an RC that’s good enough to be declared the stable release. No one can predict with certainty, at the outset, how many iterations will be required (and hence how many RCs will be needed before a stable release), but we tend to get a clearer picture of this as testing progresses.

Since the changes between 4.3.1 and 4.3.2 are relatively minor, we currently don’t anticipate any major problems requiring a second RC. We currently expect to be able to publish the stable 4.3.2 release around the end of September.

How to test Qubes 4.3.2-rc1

If you’d like to help us test this RC, the best way to do so is by performing a clean installation with the new ISO. As always, we strongly recommend making a full backup beforehand and updating Qubes OS immediately afterward in order to apply all available bug fixes.

As an alternative to a clean installation, there’s also the option of performing an in-place upgrade without reinstalling. However, since Qubes 4.3.2 is a patch release, it’s essentially Qubes 4.3 inclusive of all updates to date, which largely amounts to just using a fully-updated 4.3 installation. By contrast, a clean installation covers other areas that could also benefit from testing, such as the installation procedure, which is why it’s the recommended testing method.

Regardless of your testing method, please help us improve the eventual stable release by reporting any bugs you encounter. If you’re an experienced user, we encourage you to join the testing team.

Known issues in Qubes OS 4.3.2

It’s possible that templates restored in 4.3.2 from a pre-4.3 backup may continue to target their original Qubes OS release repos (#8701). After restoring such templates in 4.3.2, enter the following additional commands in a dom0 terminal:

sudo qubes-dom0-update -y qubes-dist-upgrade
sudo qubes-dist-upgrade --releasever=4.3 --template-standalone-upgrade -y

This will automatically choose the templates that need to be upgraded. The templates will be shut down during this process.

Fresh templates on a clean 4.3.2 installation are not affected. Users who perform an in-place upgrade from 4.2 to 4.3 (instead of restoring templates from a backup) are also not affected, since the in-place upgrade process already includes the above fix in stage 4. For more information, see issue #8701.

View the full list of known bugs affecting Qubes 4.3 in our issue tracker.

What’s a release candidate?

A release candidate (RC) is a software build that has the potential to become a stable release, unless significant bugs are discovered in testing. RCs are intended for more advanced (or adventurous!) users who are comfortable testing early versions of software that are potentially buggier than stable releases. You can read more about Qubes OS supported releases and the version scheme in our documentation.

What’s a patch release?

The Qubes OS Project uses the semantic versioning standard. Version numbers are written as [major].[minor].[patch]. Hence, we refer to releases that increment the third number as “patch releases.” A patch release does not designate a separate, new major or minor release of Qubes OS. Rather, it designates its respective major or minor release (in this case, 4.3) inclusive of all updates up to a certain point. See our supported releases for a comprehensive list of major and minor releases and our version scheme documentation for more information about how Qubes OS releases are versioned.


This is a companion discussion topic for the original entry at https://www.qubes-os.org/news/2026/09/18/qubes-os-4-3-2-rc1-available-for-testing/
3 Likes

The digital signature offered together with the new ISO file does not match. It refers to the DIGESTS file and matches that.

Unfortunately, the correct signature file, which matches the ISO file, is not offered, and the DIGESTS file, which contains the (correct) SHA-256 and SHA-512 checksums, is not offered either.

Both missing files can be retrieved from the directory containing the ISO file. So this is no real problem, just a clerical one.

4 Likes

No ipv6 by default in todo list?

Thanks for letting us know. It should be fixed now:

There’s an open issue for this part:

3 Likes

By default? I think not.
IPv6 is, and has been for some time, an option that is easily
configured for those that want it.

I never presume to speak for the Qubes team. When I comment in the Forum I speak for myself.
1 Like

@nogui It is still too early and not necessary in my opinion to enable IPv6 by default. Feel free to enable IPv6 if you prefer.

Why do you think so? About 50% of all requests to google are ipv6: IPv6 – Google . If it’s not enough, what is? And yes, I understand that actual numbers probably lower, but anyway IPv6 is quite mature

Please update the installer as well so newer hardware dont run into brick walls