>
Tech News

CachyOS quietly fixed the things that push first-time users away

The first time I installed CachyOS, I bailed halfway through because the boot screen and the desktop looked like they came from two different operating systems. That was a couple of years ago. The August 2026 ISO is the first CachyOS release I would hand to a friend without writing them a wiki summary first, and the reason is not the flashy changes. It is that the rough edges people trip on during the first hour are finally getting attention from the team, not just from the issue tracker.

Here is the frame for anyone who has never touched CachyOS. It is an Arch-derivative with a hand-curated kernel, a graphical installer, and a focus on desktop responsiveness. Updates roll forward weekly. The install removes the biggest Arch friction, which is the install itself. The August ISO pushes that philosophy further by cleaning up what happens between the desktop selection and the first login.

Why The Greeter Mismatch Was A Bigger Problem Than It Sounds

The most user-visible change in this ISO is also the most subtle. When you pick Hyprland with Noctalia during install, you now get noctalia-greeter as the login manager instead of SDDM (Simple Desktop Display Manager). When you pick Cinnamon, you get lightdm-slick-greeter instead of the older lightdm-gtk-greeter. If you do not know what a greeter is, it is the graphical prompt that asks for your username and password before your desktop session starts.

Why this matters more than it sounds: the login screen is the first thing a new user sees on every reboot. If the boot screen looks like KDE and the desktop looks like Hyprland, or the boot screen looks like the early 2000s and the desktop looks like 2026, the user concludes that something is broken even when nothing is. CachyOS has finally aligned greeter choice with desktop choice at install time, which means a Hyprland Noctalia install now boots into a consistent Noctalia-themed login, and a Cinnamon install gets a modern themeable login instead of the legacy GTK greeter.

It is the kind of change that does not show up in a feature list. You only notice it when you watch someone go through the install for the first time and not feel confused.

GNOME And COSMIC Picked Up Quiet Upgrades

Two desktops got quiet but useful work. GNOME now includes gvfs-dnssd by default, which gives the file manager the ability to find shared folders, printers, and media servers on the local network without manual configuration. The protocol under the hood is mDNS (multicast DNS) plus DNS-SD (DNS-based Service Discovery, the advertising protocol that lets printers and media receivers announce themselves), and it is the same machinery macOS and modern Windows machines have used for years. If you have ever set up a Linux file server and been disappointed that your laptop could not find it automatically, this is the change that fixes that experience.

COSMIC now ships with a native system monitor, replacing the generic GTK (the GIMP Toolkit, the cross-platform widget library behind many Linux desktops) tool that COSMIC users used to fall back to. The new monitor matches the visual language of the rest of the COSMIC desktop. It is not a flashy upgrade, but it tells you that COSMIC is being treated as a first-class citizen rather than an experimental also-ran.

Shelly 3.0 And The Mirror Speedup

Two packaging-related changes affect every install. The default graphical package manager was bumped to Shelly 3.0, which is the visual layer most users will click through when they want to install or remove software without typing commands. Coming from Ubuntu or Fedora, this is the equivalent of Software Center or GNOME Software. The 3.0 release is a real upgrade, not a version-number nudge, and the click-through experience is noticeably smoother than the previous default.

The second change is invisible to most users but matters on first install. cachyos-rate-mirrors (the tool that ranks download mirrors by measured speed) now pulls rankings from the CachyOS mirrorlist API. Until this update, the installer used a mirror snapshot from the day the ISO was built, which meant new installs often downloaded from a mirror that had since slowed down. The new ranking reflects current speed, which means updates install faster out of the box. A related fix in CachyOS-Welcome makes the speed test results actually apply to your session instead of being computed and ignored.

What this means for you:

  • One GUI (graphical user interface) to install, update, and remove packages without opening a terminal.
  • Updates pick the closest fast mirror instead of the one that happened to be best when the ISO was built.
  • The welcome screen speed test now actually feeds into the system, not just into a hidden config file.

What This ISO Is Actually Trying To Be

If you step back from the changelog and look at the August ISO as a product, the pattern is clear. CachyOS is making the case that an Arch-derivative can be a polished daily driver for someone who has never compiled a kernel, not just a tuned playground for people who already know their way around a wiki.

The moves that add up to that:

  • Greeter choice now follows desktop choice at install time, so the boot screen and the desktop look like they belong together
  • GNOME picked up mDNS file sharing that just works, which closes a gap most users only notice when it is missing
  • COSMIC shipped a native system monitor instead of punting users to a generic GTK tool
  • Shelly 3.0 is the package manager CachyOS should have shipped two years ago, with a click-through that does not feel like a debug session
  • The mirror ranking fix means the installer picks the fastest download server at install time, not at ISO build time
  • Server Edition support in the CLI installer opens the door to headless installs without a custom script

Quiet Plumbing Work Worth A Quick Note

A handful of changes are worth flagging even though they never show up in a feature list. The system tray updater was rebased on a newer Arch-Update and rewritten with a Rust-based applet, so the tray icon should start faster and use less memory. chwd, the hardware detection tool, now classifies virtual machines more reliably and improves handheld detection for Steam Deck-class devices.

The Server Edition profile is the change with the longest tail. CachyOS has historically targeted gaming handhelds and desktop workstations, and adding a headless install profile signals the project is thinking about a wider audience, including homelab operators and people running small home servers who want the same kernel tuning on machines they will never plug a monitor into.

What I Would Hand This To

If a friend who has never used an Arch-derivative asked me today whether to install CachyOS, I would say yes, with two conditions. First, only on hardware that already has working Linux drivers or where you are willing to spend an hour reading the wiki if something does not work out of the box. Second, do not switch your main daily driver until you have lived with the ISO for a week in a VM (virtual machine) or on a spare laptop, so you know whether the custom kernel is doing anything your existing distribution does not.

The August ISO is the first CachyOS release I would actively point a beginner toward. The greeter fix alone removes the most common reason first-time users abandon the install mid-flight. Add in the GNOME and COSMIC improvements, the Shelly upgrade, and the mirror ranking fix, and you have a release that polishes the first-hour experience in ways the changelog does not fully convey. None of these are headline-grabbing changes on their own, but the cumulative effect is what makes a distribution feel finished instead of feel like a hobby project.

The Catch

This release is a snapshot image, so its primary audience is people starting fresh or rebuilding on purpose. If CachyOS is already running on your machine, you do not need to install this ISO to get the changes. The same packages will roll through pacman within a few days, and your existing install will end up with the same software as a fresh install did.

The Server Edition profile is still flagged experimental. If you are using CachyOS for any production workload, do not flip to Server Edition yet. Give it a couple of months to settle.

Trade-offs to keep in mind:

  • Snapshot images always carry a small risk of installer regressions during the first week, so waiting before installing on critical hardware is the conservative move
  • Hand-tuned greeter configurations will likely reset during the upgrade, so back up any custom greeter themes or settings before you reinstall
  • The shipped Linux 6.18 LTS kernel is solid, but the newest consumer hardware sometimes needs kernels from the AUR (Arch User Repository, the community-maintained collection of user-submitted packages) to behave

What To Do Next

If you are new to CachyOS, grab the August image from the official site, pick Desktop or Handheld edition depending on what you are installing onto, and let the installer handle the new greeter choices for you. There is no manual setup required to get the polished first-boot experience. Existing users get the same software through the normal pacman update stream, so no reinstall is required to pick up these changes.

The headline here is not a single feature. It is the pattern of investing in the first-hour experience, which is what most users actually judge a distribution by. People do not read release notes. They just want the boot screen to match the desktop, and they want their package manager to feel like software that respects their time. This release moves the needle on both.

Trade-offs

A snapshot ISO is not a replacement for an install that is already working. If your current CachyOS install is healthy, the August packages will reach you through normal updates and you can skip the reinstall entirely. If you do reinstall, be aware that any greeter customization you did by hand will likely reset, and there is always a small early-ISO installer regression risk that gets ironed out within a week or two. The Server Edition profile is labeled experimental for a reason, and if you are running anything in production you should wait for a stable tag before pointing it at a real workload.

Leave a comment