For a user: microcode applied at boot, which you never see but should have had; speakers, touchpads and Wi-Fi on laptops we don't own; and several COSMIC settings that did nothing because the program they call wasn't installed.
A hardware check on a desktop found things that were silent: the machine worked, and the feature simply wasn't there.
No edition shipped CPU microcode. The test machine's Intel N100 ran its factory revision while Intel's
microcode release was several generations ahead, and the health check reported it as vulnerable with no
microcode. Intel and AMD microcode is now built into the kernel and applied by the early loader. It rides
inside bzImage, so an installed machine gets it from a normal update, with no boot-menu or updater change.
Hardware outside our own machines had no driver. The kernel config had grown one owned machine at a
time. It now covers Intel's xe GPU driver (Lunar Lake, Arc B-series: no GPU acceleration before), Intel
Wi-Fi 7's MLD mode, MediaTek MT7925, Qualcomm ath12k and more rtw89 parts with their firmware, the AMD and
Intel platform-management drivers (without them s2idle never reaches deep sleep, so the laptop drains
battery while suspended), Intel power-button and hotkey drivers, ThinkPad/IdeaPad/ASUS/HP/Dell/Acer platform
drivers, the Cirrus CS35L41/CS35L56 and TAS2781 speaker amplifiers with their tuning firmware (silent
speakers on a lot of modern laptops), the Ryzen 7040+ digital microphone, Wacom/Microsoft/Lenovo/ASUS/Apple/Elan
HID devices and RMI4/Elan touchpads, sensor hubs, VirtualBox/VMware/Hyper-V graphics, and Bluetooth PAN. Core
gained the Intel IOMMU on by default, Yama and Landlock LSMs, and WireGuard (NetworkManager and the tools were
there; the kernel module wasn't).
Programs COSMIC runs by name were missing. Every Command::new("…") in the pinned COSMIC sources was
checked against the image. The on-screen keyboard was never built, though cosmic-session started it at every
login and the panel's applet toggled nothing. There was no rfkill, so Bluetooth couldn't come back after
airplane mode. No pactl, so Mono Audio didn't reach PulseAudio clients (every Flatpak browser, Discord,
Spotify). No qalc, so the launcher's calculator did nothing. No locale binary and only en_US.UTF-8, so
Settings → Region & Language listed no languages at all; about 50 UTF-8 locales came in. No xrdb, so X11
apps got no cursor theme. No notify-send. Orca, the screen reader the greeter's accessibility toggle starts,
is still a known gap: it needs GObject introspection and a speech stack, which means rebuilding most of the
desktop.
GameMode did nothing because its polkit actions are allowed only for a group no image created. That group
exists now, the installer adds the owner to it, and merge-accounts adds existing owners once to any group later
appended to the owner-groups list, which also fixed pipewire membership on machines installed before that group
existed. vm.max_map_count was 65530, which crashes Steam and Proton titles and is below Elasticsearch's
minimum; it's 1048576 everywhere now.
Two housekeeping items that stop noise becoming normal: two mDNS stacks had been fighting over port 5353 since
the previous release, and tools/pengyos-desktop-net had been emitting NetworkManager keys that don't exist, a
wpa_supplicant.conf with a placeholder network, COSMIC TOML files COSMIC never reads, and a text file at the
filesystem root. The tool is retired; only a valid NetworkManager.conf remains.