How to Try Qubes OS 4.3.2 (2026): A Compartmentalized Linux

Figure: AI-generated illustration. Real Qubes OS screenshots were unavailable at time of writing.

Qubes OS is the only mainstream desktop Linux distribution that takes the
“security by compartmentalization” model to its logical conclusion: every
piece of your digital life runs in its own lightweight Xen virtual machine,
and the host operating system itself is a thin control plane (Dom0) that
holds nothing user-facing. Released on 2026-09-08, Qubes OS 4.3.2 is the
latest stable point release in the 4.3 series and is the version you should
be installing if you’re curious about the project today.

This is a hands-on guide for evaluating Qubes on real hardware in 2026:
what’s new since 4.2, what the install actually looks like, and what you
should expect day-to-day from the “many qubes” workflow.

What’s new in Qubes 4.3 (vs 4.2)

If you read about Qubes a few years ago and bounced off because of the
cumbersome installer, the news is mostly good. Qubes 4.3 ships against Fedora
41 as the Dom0 base (up from Fedora 37 in 4.2), which means:

• The default Xfce4 desktop in Dom0 is on a much newer GTK stack — it
  no longer feels like a 2018-era interface
• qubes-core-admin-client 4.3 supports qvm-features for declarative
  per-qube metadata, which makes scripted installs less painful
• Disposable VMs are noticeably faster to spin up thanks to a qvm-create --class DispVM --template refactor in 4.3.0
• The kernel is still a custom Xen-aware build (currently 6.12.x), so
  don’t expect bleeding-edge mainline features
• Hardware support is the major pain point: Qubes still requires VT-x and
  VT-d with IOMMU enabled in firmware, and recent AMD Ryzen 7000/9000
  systems are far better-supported than Intel 12th/13th gen, where
  uncore graphics isolation has been broken for months

The 4.3.2 point release (out 2026-09-08) is mostly bug-fix housekeeping:
fixed USB passthrough on certain Lenovo ThinkPad X1 Carbon Gen 13
firmware, restored sys-usb autostart on suspend-resume, and tightened
the default qrexec policy for whonix-workstation updates.

What you actually do, day to day

The conceptual model of Qubes is unusual if you’ve only ever used a
single-tenant Linux distro. Every “thing you do” lives inside a qube — a
VM that may exist for a single session (Disposable VM), may persist
across reboots, and may be marked “trusted” or “untrusted” by color-coded
domain label in the top bar.

The five qubes I keep open most often look like:

The reason this matters: when an attachment in untrusted tries to
phone home, it’s already inside a VM that has no clipboard or filesystem
access to anything except what you explicitly copy-paste into it via
qvm-copy-to-vm and qvm-paste. When whonix-workstation gets popped,
it’s the Tor circuit that gets popped, not your real identity.

This is the workflow most people miss: it’s not a hypervisor you put apps
into, it’s a security policy you happen to also be able to run apps in.

Installing Qubes 4.3.2 on bare metal

The official ISO (about 1.4 GB) is downloadable from
https://www.qubes-os.org/downloads/. The installer is the same Anaconda
graphical flow Fedora uses, but with a custom disk-layout screen.

You will need at minimum:

• 16 GB of RAM (8 GB technically works, but you want at least 2 GB per
  persistent qube plus 4 GB for Dom0)
• A CPU with VT-x and VT-d (Intel) or AMD-Vi (AMD), both enabled in
  firmware
• An SSD — Qubes on a spinning disk is genuinely miserable
• A wired Ethernet connection for the initial install; Wi-Fi passthrough
  is doable but requires manually enabling sys-net against a USB NIC

The installer walks you through three high-level choices:

1. Disk layout: LVM-on-LUKS is the default. If you have a separate
   SSD you can dedicate to Qubes, pick the “encrypt everything except
   /boot” option. Full-disk encryption on Qubes is more interesting than
   on Fedora because the threat model includes someone pulling the SSD
   while the system is off and trying to read the storage backing each
   qube’s image.
2. Default template: Fedora 41 (Xfce), Debian 12, Whonix 17, and
   the minimal Fedora template are all checked by default. Uncheck
   anything you don’t intend to provision.
3. USB keyboard / mouse policy: by default, USB input devices go
   through sys-usb. If your keyboard uses a non-standard HID profile
   (gaming keyboards often do), uncheck this or you’ll sit at a stuck
   GRUB prompt wondering why your typing doesn’t register.

Reboot at the end and you’ll land in a Dom0 Xfce4 session with a
not-very-promising-looking single window that says “Create a new qube.”
Click it.

The first 30 minutes after install

Most of the day-one experience is convincing yourself that the model
actually works. A few useful commands:

# list all qubes and their state
qvm-ls --raw-data | column -t -s,

# create a new persistent qube from the fedora-41-xfce template
qvm-create --label red --class AppVM --template fedora-41-xfce personal

# create a disposable VM template from fedora-41-xfce
qvm-create --label gray --class TemplateVM --template fedora-41-xfce fedora-41-dvm

# route a qube through sys-whonix (Tor) instead of sys-firewall
qvm-prefs --set netvm sys-whonix personal

The two UI affordances worth knowing are the top-bar Q menu (it’s the
Xen-aware menu of all running qubes and their applications) and
Ctrl+Alt+Shift as the “release keyboard / mouse from current qube”
shortcut. Until you’ve internalized the second one, you’ll occasionally
type a password into the wrong qube and have to invalidate it.

Is Qubes for you in 2026?

Honest answer: probably not, if your threat model is “I want a secure
laptop for daily web browsing.” The day-to-day friction is real —
clipboard operations are slightly slower, file transfers between qubes
are explicit instead of seamless, and you cannot trivially run a GPU
through any qube other than Dom0.

It is for you if your threat model is “I want a single workstation
where a malicious PDF I opened can’t read my GPG key, where an XSS in my
browser can’t phish my banking session, and where a compromised Tor
exit node can’t deanonymize my real IP.” That’s the audience Qubes is
built for, and on that axis it’s unmatched.

A practical middle path: install Qubes on a second SSD and dual-boot.
You get Fedora or whatever for “normal life” and Qubes for “things I
don’t trust.” It’s how the Qubes core developers themselves use it.

Qubes 4.3.2 is the first release in over a year that I’d call “smooth”
rather than “tolerable” on a current AMD Ryzen laptop. If you’ve been
waiting for a reason to try it, this is the one.

Project home page: https://www.qubes-os.org/ — installation guide,
hardware compatibility list, and the security architecture overview are
all there.