If your Quick Access Menu lost its plug icon this month, or Decky Loader on Steam Deck now throws a wall of red text, you are not alone. A Steam client update on October 13, 2026 started a chain of crashes that the project’s issue tracker traced to one split piece of Steam’s interface code. Decky Loader v3.3.0, the newest release, carries the fix, and SteamOS 3.9.5 reached all users on October 23. This guide walks through 13 steps, about 35 minutes, to get a working install back.
Decky Loader is a community plugin loader, and the official Decky site explains that it works by injecting React components into the Steam UI and running scripts in the background. That design keeps it light, but it also means a change inside Steam’s own interface can break it overnight. If you have never installed it, start with our Decky Loader setup guide and come back here when something goes wrong. This article is the repair manual, not the first-install walkthrough.
We focus on the failures people actually search for: Decky Loader not working after an update, Decky Loader not showing up in the Quick Access Menu, plugins that fail with a TypeError, and installs stuck on an old version. Each step includes a command or menu path, the output you should expect, and the pitfall that trips people up. The last step turns everything into a small diagnostic script you can rerun after every SteamOS or Steam client update.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
The October Break: What Happened to Decky Loader on Steam Deck
The short version: Steam’s front end changed, and Decky had assumptions baked in. According to issue #988 in the SteamDeckHomebrew/decky-loader repository, a user opened a bug on October 16 titled “[BUG] October 13th update” after Decky ran normally for a short while and then displayed an error until they uninstalled it. That reporter listed SteamOS 3.8.28 on the Stable channel with Decky Loader v3.2.10. Other commenters in the thread described the same crash on SteamOS 3.9.3, on a Steam Machine running a SteamOS beta, on a ROG Ally X, and on handhelds running other Linux-based systems.
One commenter dug into the cause. They reported a Steam client build numbered 1792192922, built on 2026-10-16, in which a webpack module of interface class names had been split in two. One module held 20 keys such as PanelSection, PanelSectionTitle and BatteryDetailsLabels. The other held 55 keys including Title and QuickAccessMenu. Decky’s finder matched on keys from the first module, got an object where Title was undefined, and the loader died with a TypeError while rendering its title view. After that error, the plugin list stayed empty, so no plugin loaded at all.
Community patches appeared on October 17. Two commits referenced the issue and merged the split class tables whenever a key went missing. On October 18 the issue closed as completed through pull request #991, and the same day the project published Decky Loader v3.3.0. The release notes list a UI bump described as fixing the beta, along with ARM Linux support with experimental builds for every platform, a new plugin update API, a macOS type-checking fix, and a warning shown when you install unvetted third-party plugins. The previous stable release, v3.2.10, had landed on October 4 with a sort-plugins setting and a file picker fix.
| Date (2026) | Event | Why it matters for your Deck |
|---|---|---|
| October 4 | Decky Loader v3.2.10 released | Last release before the break. Still works on older Steam clients. |
| October 13 | Steam client update posted for Steam Deck | The date the issue thread blames for the interface change. |
| October 16 | Issue #988 opened, client build 1792192922 built | First public bug report. Maintainers asked for logs. |
| October 17 | Community commits merge the split class modules | Workaround for people willing to build from source. |
| October 18 | PR #991 merged, Decky Loader v3.3.0 released | The official fix. Install this version or newer. |
| October 23 | SteamOS 3.9.5 released to all users | New stable base with Plasma 6.7.3 and Linux kernel 7.2. |
Treat the exact cause as the issue thread’s explanation, not a Valve statement. We found no official Valve note tying the Decky crash to a specific client change, and the Decky project says it is not affiliated with Valve. What we can say with confidence is the order of events above, and that v3.3.0 is the newest release on the project’s release page as of October 25, 2026. If you run a Steam Deck OLED, the model Valve currently lists as its newest handheld, this applies to you exactly as it does to a Steam Deck LCD.
How Decky Works and Why Steam Updates Break It
Understanding the mechanism saves you from cargo-cult fixes. Gaming Mode on a Steam Deck is a Chromium-based interface that Valve updates through the Steam client, separately from the operating system. Decky runs a small Python service on the Deck, serves a JavaScript frontend from a local port, and injects that frontend into Steam’s interface so plugin panels can appear inside the Quick Access Menu. The plugins themselves have a Python backend for system tasks and a React frontend for the screens.
To draw those panels in a style that matches Steam, Decky borrows Valve’s internal class names for fonts, spacing and titles. It finds them by searching Steam’s bundled JavaScript modules for known keys. That is a clever shortcut and a fragile one. When Valve reorganizes how the modules are packaged, as the issue thread describes for the October client build, the search returns the wrong object, and every panel that asks for a title crashes. Nothing is wrong with your Deck, your SD card or your plugins in that scenario. The ground simply moved.
This explains three patterns you will see. First, breakage tends to follow Steam client updates more than SteamOS updates, because the client carries the interface. Second, beta client users hit problems first, since betas change the interface before the stable channel does. Third, fixes arrive as a new loader release or an updated plugin, never as something you can toggle in settings. When you read that “Decky broke,” ask which of the three layers moved: the OS, the Steam client, or the loader. Step 1 below answers that question for your Deck.
Prerequisites: Hardware, Versions and Tools
You need very little, but the versions matter because the whole story here is about version mismatches. Everything below is current as of October 25, 2026. If you are on an older number, step 1 will tell you, and later steps explain whether to move.
| Item | Version or detail | Notes |
|---|---|---|
| Handheld | Steam Deck OLED or LCD | Decky targets the SteamOS image Valve ships on Steam Deck. |
| SteamOS | 3.9.5 stable (released October 23, 2026) | Notes cover changes since 3.8 stable. Opt-in channels live under Settings, System, System Update Channel. |
| Decky Loader | v3.3.0 (newest release) | Previous stable was v3.2.10 on October 4. |
| Desktop Mode | KDE Plasma 6.7.3 | Moved up from Plasma 6.4.3 in SteamOS 3.9. |
| Kernel | Linux 7.2 | Rebased in SteamOS 3.9.5. |
| Network | Wi-Fi with access to GitHub | The installer downloads the release from the project’s repository. |
| Optional | Bluetooth keyboard or a second device for SSH | Typing commands with the on-screen keyboard works but is slow. |
SteamOS 3.9 is the first stable branch to ship the newer base. Coverage of the stable release, including the Linux 7.2 and Plasma 6.7.3 update, confirms the Desktop Mode jump you will see when you open Konsole. If you rarely leave Gaming Mode, read our Steam Deck Desktop Mode guide first so the terminal and file manager feel familiar before you start typing commands.
Charge the Deck above half or plug it in. A reinstall takes only a few minutes, but a SteamOS update triggered mid-repair can reboot you into a state that is harder to read. Also decide up front whether you are on a stable or beta Steam client, because that single fact explains most of the October reports. The steps below show you how to find out.
Steps 1 to 3: Record Versions, Back Up, Prepare Konsole
Step 1: Record your versions. Before touching anything, write down what you run today. In Gaming Mode open Settings, then System, and note the SteamOS version and the update channel. Then press the Steam button, choose Power, and select Switch to Desktop. Valve’s SteamOS 3.9.5 notes include a fix for a bug where changing the timezone could block the switch to Desktop Mode until a reboot, so if the switch fails on an older build, reboot once and try again.
Open Konsole from the application menu and run the following block. It prints the SteamOS identifiers, the kernel, the Steam client package files that hint at your client channel, and the contents of the homebrew folder.
grep -E '^(VERSION_ID|BUILD_ID|VARIANT_ID)=' /etc/os-release
uname -r
ls ~/.steam/steam/package/ 2>/dev/null | grep -i steam_client
ls ~/homebrew 2>/dev/nullTypical output on a healthy 3.9.5 install looks like the block below. Your build identifier will differ, and the package filenames can vary by client channel, so treat the third line as a hint rather than a guarantee.
VERSION_ID=3.9.5
BUILD_ID=(a date-stamped build number)
VARIANT_ID=steamdeck
7.2.x-valve-neptune
steam_client_publicbeta_ubuntu12.manifest (only if you opted into the client beta)
backups logs plugins services settings themesIf the listing of ~/homebrew is empty or the folder is missing, Decky is not installed at all, and you can skip ahead to step 8. If the folder exists with plugins and settings in it, you have something worth protecting, which brings us to the next step.
Step 2: Back up the homebrew folder. Everything Decky stores for you sits in your home directory, not in the read-only system image. That includes installed plugins, plugin settings, themes and logs. A copy takes seconds and turns a risky repair into a reversible one.
mkdir -p ~/decky-backups
tar -czf ~/decky-backups/homebrew-$(date +%F-%H%M).tar.gz -C ~ homebrew
ls -lh ~/decky-backupsStep 3: Set a sudo password. The installer and the service commands in later steps need administrator rights. A fresh Steam Deck has no password set for the deck user. Run passwd in Konsole, choose something you will remember, and note that the terminal shows nothing as you type. A third-party install guide at deckyloader.org says you can create a password temporarily for the installation, and that approach works fine. If you forget it later, run passwd again.
One more preparation habit saves time. If typing on the Deck’s on-screen keyboard (Steam button plus X) wears on you, enable SSH once and run the rest of this guide from a laptop on the same network. The commands below switch the service on and show the Deck’s address. Turn SSH off again when you finish if you do not use it regularly, since it opens a remote login path to your device.
sudo systemctl enable --now sshd
ip -4 addr show | grep inet
# later, to switch it off again:
sudo systemctl disable --now sshdSteps 4 and 5: Read the Real Error and Check the Service
Step 4: Read the error instead of guessing. Maintainers asked for logs in issue #988, and the commenters who supplied them are the reason the root cause surfaced within a day. You can do the same. Decky’s frontend is served from your Deck on port 1337, and Steam exposes its UI to a debugger when the developer option is on. In Gaming Mode, enable Developer Mode under Settings, System. A Developer menu then appears, and it holds the CEF remote debugging switch. Turn that on and Steam listens for a Chromium debugger on your Deck.
From a browser on the Deck in Desktop Mode, open http://localhost:8080. From a laptop, use the Deck’s address with the same port. Choose the SharedJSContext target. The console in that target shows the JavaScript error Decky hit. During the October break, the lines a reporter pasted looked like this.
TypeError: Cannot read properties of undefined (reading 'Title')
at TitleView (http://localhost:1337/frontend/chunk-BJJdCYVd.js:5483:87)If you see that signature, you are looking at the split class module problem, and the fix is simply v3.3.0 or newer (step 8). If you see something else, such as a plugin name in the stack trace, the loader itself is fine and one plugin is the culprit, which step 10 handles. Write the error text down. It is the single most useful thing to paste into a support request.
Step 5: Check the background service. Decky runs as a systemd service named plugin_loader. When the plug icon never appears, the service is often stopped, crashed, or missing after a SteamOS update. These commands tell you which.
systemctl is-active plugin_loader
sudo systemctl status plugin_loader --no-pager | head -n 15
journalctl -u plugin_loader -n 60 --no-pager
find ~/homebrew/logs -type f -name '*.log' | tail -n 5Healthy output starts with the word active. A result of inactive or failed means the loader is not running, and you should look at the last lines of the journal for a Python traceback or a missing file. A message saying the unit could not be found means the service is gone entirely, which usually happens after a clean OS reinstall or a factory reset. In that case a reinstall is the only path, and your backup from step 2 keeps your plugin settings safe. Restarting the service by hand is worth one try before reinstalling.
sudo systemctl restart plugin_loader
sleep 5
systemctl is-active plugin_loaderIf the service reports active but Gaming Mode still shows no plug icon, the loader is running and the failure sits in the injected interface, which is exactly the October pattern. Do not keep restarting. Move to the next steps and update the loader.
Steps 6 and 7: Developer Mode and the Update Channel
Step 6: Re-enable Developer Mode if it switched off. The deckyloader.org guide advises that a missing plug icon after a SteamOS update can mean Developer Mode was disabled, and says to turn it back on in Settings before re-running the installer. That site states on its own pages that it is not affiliated with the Decky project, so use it as a convenient checklist and not as an authority. The advice still matches what many users report. Go to Settings, System, and make sure Enable Developer Mode is on. Reboot afterward.
Step 7: Choose the right Decky update channel. If the plug icon does open, update from inside Decky. Open the Quick Access Menu, select the plug icon, then the settings cog, and look for the update channel and the check-for-updates control in the general section. Pick Stable. The project’s repository describes a latest-release channel for most users and a pre-release channel for plugin developers, and the installer guide recommends the stable option. A pre-release tag, v3.2.10-pre1, existed for the build before the October 4 stable release, which shows how close testing builds run to the real thing.
Three separate update channels confuse people, and mixing them up caused much of the October noise. The table below separates them.
| Channel | What it controls | Where you set it | Risk on beta or pre-release |
|---|---|---|---|
| SteamOS update channel | The operating system image (kernel, Plasma, drivers) | Settings, System, System Update Channel | Newer OS code before it reaches everyone, occasional regressions. |
| Steam client channel | The Steam interface Decky injects into | Steam settings (the menu label has moved between releases) | Highest risk for Decky, since the October break came from a client build. |
| Decky update channel | The loader itself | Decky settings, general section | Pre-releases are meant for plugin developers. |
The practical rule: if you want zero surprises, keep all three on stable. If you must run a beta somewhere, make it the SteamOS channel and keep the Steam client and Decky on stable. A beta Steam client combined with a stable Decky release was the exact mismatch in issue #988. When an in-app update works, jump to step 9 to verify. When the update screen itself crashes, continue with the reinstall.
Steps 8 and 9: Reinstall Decky Loader v3.3.0 and Verify
Step 8: Reinstall from the official installer. A reinstall is safe. The official FAQ says Decky does not change Steam files, and your plugins and settings stay in the homebrew folder you already backed up. In Desktop Mode, open a browser and go to the Decky project’s website, download the installer, and run it. If your browser cannot run the file directly, open it from the Dolphin file manager. The deckyloader.org guide adds one Firefox quirk: remove a trailing .download from the file name before you run it.
When the installer asks for a release type, choose the latest release. Enter your sudo password when prompted. The installer finishes in a few minutes on a normal connection and ends with a prompt to return to Gaming Mode. The project also documents a command line installer you can run in Konsole. Copy that one-liner from the project’s own README on GitHub and never from a forum post, because it pipes a script into your shell and you want the genuine source.
Be cautious with forks. A separate Droid-Deck fork of the loader exists, and an October 18 pull request in the Droid-Deck project changed its install path to fetch releases from the upstream SteamDeckHomebrew repository instead of the fork. That is a good reminder to confirm which repository a script points at before you run it. On a Steam Deck you want the upstream project.
Step 9: Verify the install. Use the Return to Gaming Mode shortcut on the desktop, press the Quick Access button (the three dots), and look for the plug icon at the bottom of the tab strip. Open it. You should see the plugin list and a store icon for the Plugin Browser. Then confirm from the terminal that the service and version agree.
systemctl is-active plugin_loader
ls -la ~/homebrew/services
cat ~/homebrew/services/.loader.version 2>/dev/nullThe expected output is active, a list containing the PluginLoader binary, and a version string that reads v3.3.0 or newer. If the hidden version file is absent on your build, open the Decky settings screen instead, because the version appears near the top of the general section. If the number says v3.2.10 or older, the installer picked a cached copy. Re-run it with your network connected and choose the latest release again.
Step 10: Repair Your Plugins After the Loader Update
A fixed loader does not guarantee fixed plugins. Many plugins read the same Steam interface classes that broke, and v3.3.0 also introduced a new plugin update API. After the update, open the Plugin Browser, check for updates, and install any that appear. Do this over Wi-Fi with the Deck plugged in, one plugin at a time, so a single failure does not hide behind a long list.
If a plugin still shows a TypeError popup, disable it from the plugin list, then reload the Quick Access Menu. Re-enable plugins one by one until the error returns. That tells you which plugin to remove or wait on. Check the plugin’s page on its repository for an open issue that mentions the October 13 or 16 client builds, because the author may already have a release queued. Reinstalling a single plugin never requires a full Decky reinstall.
Which plugins deserve your first reinstall? A September 26, 2026 roundup of the best Decky Loader plugins lists nine: SteamGridDB, NonSteamLaunchers, ProtonDB Badges, CSS Loader, Decky LSFG-VK for Lossless Scaling frame generation, Storage Cleaner, AutoFlatpaks, EmuDecky and MagicPods. It also names two to skip, vibrantDeck and Decky Recorder. Use that list as a starting point, not a prescription. ProtonDB Badges is worth restoring early because it surfaces community ratings right in your library, and our comparison of Steam Deck Verified versus ProtonDB explains how to read those ratings. If you run emulators, EmuDecky pairs with the setup in our EmuDeck tutorial.
One v3.3.0 change affects your habits. The loader now warns you about the risks of installing third-party plugins that the store has not vetted. Read the warning. A plugin runs with access to your Deck’s user account, so a plugin from a random link can read files in your home folder. Stick to the store unless you know the author, and avoid pasting plugin URLs from chat messages. CSS Loader themes are lighter-weight but still run code, so apply the same caution to themes from outside the official listing.
After the repair, reorder your plugin list so the ones you rely on sit at the top. The v3.2.10 release added a sort-plugins setting, and it pays off when you keep a dozen plugins installed. Remove anything you have not opened in a month. Fewer plugins mean fewer chances for the next client change to break something, and a shorter list makes step 10’s bisect-by-disabling method much faster.
Steps 11 and 12: Steam Client Channel and SteamOS 3.9.5 Quirks
Step 11: Decide whether to stay on the Steam client beta. If Decky works after step 9, you can leave the client channel alone. If you still hit crashes and you are on the Steam client beta, switch the client back to stable in the Steam settings and let the client restart. The October reports cluster around beta client builds, and a stable client usually trails by a few days, which gives plugin authors time to catch up. You lose nothing in your library by opting out.
Opting out can take a restart or two, and the client may redownload a package. Do it on Wi-Fi while charging. If you want to return to beta later for a specific feature, such as the Remote Play HDR fix that one report says reached a Steam client beta on October 22, check the project’s issue tracker first and confirm the current Decky release supports that client build. A five-minute search beats an evening of troubleshooting.
Step 12: Account for the SteamOS 3.9.5 changes. The 3.9.5 notes affect Decky users in a few ways. Desktop Mode jumped to Plasma 6.7.3, so window behavior and the Discover app look different from older screenshots. The Desktop Mode lock screen can now be turned on explicitly, though it stays off by default. If you enable it, a locked Desktop Mode session can interrupt a long install, so leave it off while you repair. Valve also lists an improvement to idle power use on Steam Deck when no audio is playing, which Steam Deck HQ covered, though Valve gave no percentage.
Hibernation deserves a mention because it keeps showing up in rumors. The official notes say preliminary hibernation support was added at the kernel level, is not exposed in the Game Mode interface, and is not yet enabled on Steam Deck because of an outstanding driver bug. Do not expect Decky plugins that promise hibernation to work, and be wary of any guide that tells you to hack it on. For now, sleep and shutdown remain the supported paths.
One quiet change helps repair work: Valve renamed various scripts and packages from steamos- to holo-, with aliases kept for the old names where appropriate. If an old guide tells you to run a steamos- command and it fails, try the holo- name or check whether the alias exists on your build. Decky itself does not depend on these names, but helper commands you find online sometimes do.
Step 13: Build the Decky Doctor Script (Complete Project)
Steps 1 to 12 repair a broken install. Step 13 keeps the next break from costing you an evening. The script below collects the same facts you gathered by hand: SteamOS version, kernel, client files, service state, plugin count, recent log errors, and an optional fresh backup. Run it after every SteamOS or Steam client update and paste the output into any bug report. Save it as ~/decky-doctor.sh in Desktop Mode.
#!/usr/bin/env bash
# decky-doctor.sh - read-only health check for Decky Loader on Steam Deck
set -u
HB="$HOME/homebrew"
BK="$HOME/decky-backups"
STAMP="$(date +%F-%H%M)"
row() { printf '%-26s %s\n' "$1" "$2"; }
echo "== Decky Doctor ($STAMP) =="
row "SteamOS" "$(grep -E '^VERSION_ID=' /etc/os-release | cut -d= -f2)"
row "Build" "$(grep -E '^BUILD_ID=' /etc/os-release | cut -d= -f2)"
row "Kernel" "$(uname -r)"
CLIENT="$(ls "$HOME/.steam/steam/package/" 2>/dev/null | grep -i '^steam_client_' | head -n 1)"
row "Steam client package" "${CLIENT:-not found}"
if [ -d "$HB" ]; then
row "homebrew folder" "present"
row "Plugins installed" "$(find "$HB/plugins" -mindepth 1 -maxdepth 1 -type d 2>/dev/null | wc -l)"
else
row "homebrew folder" "MISSING (Decky not installed)"
fi
STATE="$(systemctl is-active plugin_loader 2>/dev/null)"
row "plugin_loader service" "${STATE:-unknown}"
CODE="$(curl -s -o /dev/null -m 3 -w '%{http_code}' http://localhost:1337/ 2>/dev/null)"
row "Frontend port 1337" "HTTP ${CODE:-none}"
ERRS=0
LATEST_LOG="$(find "$HB/logs" -type f -name '*.log' -printf '%T@ %p\n' 2>/dev/null | sort -n | tail -n 1 | cut -d' ' -f2-)"
if [ -n "$LATEST_LOG" ]; then
row "Newest log" "$LATEST_LOG"
ERRS="$(grep -ciE 'traceback|typeerror|exception' "$LATEST_LOG")"
row "Error lines in log" "$ERRS"
if [ "$ERRS" -gt 0 ]; then
echo "-- last error lines --"
grep -iE 'traceback|typeerror|exception' "$LATEST_LOG" | tail -n 5
fi
else
row "Newest log" "none found"
fi
if [ "${1:-}" = "--backup" ] && [ -d "$HB" ]; then
mkdir -p "$BK"
tar -czf "$BK/homebrew-$STAMP.tar.gz" -C "$HOME" homebrew && row "Backup written" "$BK/homebrew-$STAMP.tar.gz"
fi
echo "== Verdict =="
if [ "$STATE" = "active" ] && [ "$ERRS" -eq 0 ]; then
echo "OK: service running, no errors in the newest log."
else
echo "CHECK: service is '${STATE:-unknown}' or the log has errors. See steps 4 to 8."
fiMake it executable and run it. The script only reads state unless you pass the –backup flag, which adds a dated archive to the backup folder from step 2.
chmod +x ~/decky-doctor.sh
~/decky-doctor.sh
~/decky-doctor.sh --backupA healthy run prints something like the block below. The numbers will differ on your Deck, but the shape should match.
== Decky Doctor (2026-10-25-2011) ==
SteamOS 3.9.5
Build (your build id)
Kernel 7.2.x-valve-neptune
Steam client package steam_client_publicbeta_ubuntu12.manifest
homebrew folder present
Plugins installed 6
plugin_loader service active
Frontend port 1337 HTTP 200
Newest log /home/deck/homebrew/logs/...
Error lines in log 0
== Verdict ==
OK: service running, no errors in the newest log.Two cautions about the script. First, the HTTP code for port 1337 may differ across Decky versions, so treat any numeric response as proof the frontend server is up and a result of none as the red flag. Second, the Steam client package name only identifies your channel and does not report the build number. If you file a bug, also copy the build line from the Steam settings screen. We built the script from the commands in this guide but could not run it on every SteamOS build, so test it once while your Deck is healthy to learn what normal looks like.
Decky Loader Beyond the Deck: Steam Machine, Ally and Bazzite
Many October reporters were not on a Steam Deck. They ran a Steam Machine, a ROG Ally X, an Odin 3 under a custom handheld OS, and a Retroid Nova. That matches Valve’s direction. Coverage of SteamOS 3.9 describes support spreading to Steam Machine, Steam Frame, and selected third-party handhelds, including Lenovo Legion Go hardware. If you are weighing those devices, our comparison of the Steam Deck, Steam Machine and Steam Frame lays out the hardware gap.
For Decky, the support line is clear on the official site. The project says Decky Loader is intended for the SteamOS installation that ships on Steam Deck, and that HoloISO and other third-party SteamOS-style distributions are not officially supported and may not work. The v3.3.0 release adds ARM Linux support and experimental builds for every platform, which widens what the code can run on, but experimental is the key word. Expect rough edges and ask in the project’s community channels before reporting a bug from a non-Deck device.
Bazzite users face a slightly different picture. Bazzite follows its own update cycle, separate from Valve’s, so a Steam client change and a Bazzite image update rarely land on the same day. If you run it on a handheld, check Bazzite’s documentation before reinstalling Decky by hand, and see our Bazzite install guide for how that system differs from SteamOS. On a Windows handheld, Decky is not officially supported, though unofficial community ports exist, and the choice between platforms in our Steam Deck, ROG Ally and Legion Go comparison often turns on that gap.
The takeaway for repair work: the 13 steps in this guide target an unmodified Steam Deck. On other hardware, steps 1 to 5 still diagnose the problem, but step 8 might point to a different installer or a distro-specific package. When in doubt, follow your distribution’s own instructions and keep the backup from step 2 close.
Seven Common Pitfalls That Break Decky Installs
These are the mistakes that turn a five-minute fix into an afternoon. Each one shows up in the project’s bug template, the official FAQ, or the October thread.
- Mixing a beta Steam client with an old Decky. This was the October failure. Match the loader release to the client you actually run, or move the client back to stable.
- Choosing the pre-release in the installer. The installer offers a latest release and a pre-release. Pre-releases target plugin developers and may be unstable, so ordinary users should pick the latest release.
- Editing the read-only filesystem. The project’s bug template asks whether you ever modified the read-only filesystem, because doing so is a known source of odd failures. Decky installs into your home folder and does not need you to unlock the root partition.
- Deleting the whole homebrew folder. It holds your plugins, settings and themes. Remove a single plugin folder instead, and keep the tarball from step 2.
- Running scripts from unverified sources. A third-party guide such as the one at deckyloader.org can be a useful checklist, but it says it is not affiliated with the project. Pull installers and commands from the official site and repository.
- Ignoring the file name quirk. A Firefox download may append .download to the installer name, and the file will not launch until you remove it.
- Skipping the sudo password. Without one, the installer prompt has nothing to accept, and people assume the tool is broken. Set it with passwd and clear it later if you wish.
One more pitfall deserves its own sentence: reporting a bug without logs. In issue #988 the first maintainer reply said the problem could not be reproduced and asked for logs. Reports that included the console error and the Steam client build made the diagnosis possible. The script in step 13 gives you most of that information in one paste.
Troubleshooting: 10 Decky Loader Problems and Fixes
Use this section when a specific symptom matches. The table gives the quick answer and the list below adds the reasoning. If you landed here from a search for Decky Loader not working, start with the first row.
| Symptom | Most likely cause | First fix |
|---|---|---|
| Plug icon missing | Service stopped or Developer Mode off | Steps 5 and 6, then reinstall. |
| TypeError on Title | Steam client build with split class module | Install Decky v3.3.0 or newer. |
| Plugin list empty | Loader crashed before plugins loaded | Check the SharedJSContext console, then update. |
| One plugin crashes the menu | Plugin out of date | Disable it, update it, re-enable. |
| Installer will not open | Browser blocks the file | Open it from Dolphin and drop the .download suffix. |
| Sudo prompt rejects input | No password set | Run passwd in Konsole. |
| Works until reboot only | Service not enabled | Reinstall and check systemctl status. |
| Desktop Mode will not open | Timezone bug on older builds | Reboot, then update to SteamOS 3.9.5. |
| Store will not load | No route to GitHub or the store | Check Wi-Fi, then retry. |
| Plugin vanished after OS update | Home folder intact, service missing | Reinstall Decky and keep ~/homebrew. |
- 1. Decky Loader not showing up. Run systemctl is-active plugin_loader. If it says inactive or failed, restart it. If the unit is missing, reinstall. If the service is active, the problem is the interface injection and you need a newer loader.
- 2. TypeError popups on every plugin. That points to a mismatch between the loader and the Steam client rather than any single plugin. Update Decky first, plugins second.
- 3. Empty plugin list after an update. A commenter in the October thread noted that the plugin collection stayed empty after the loader crashed. Check the console target from step 4 for the error that stopped initialization.
- 4. Everything works in Desktop Mode but not Gaming Mode. Decky injects into the Gaming Mode interface. Return to Gaming Mode with the desktop shortcut and test there.
- 5. Installer fails on the download. Confirm you can reach github.com from the Deck. Captive portals and some school networks block it. Try a phone hotspot.
- 6. A plugin install button does nothing. The v3.3.0 warning for unvetted plugins may be waiting for you to confirm. Look for a dialog that sits behind the Quick Access Menu.
- 7. CSS Loader themes look broken. Themes can lag behind Steam interface changes just like plugins. Switch to the default theme, update the CSS Loader plugin, then try the theme again.
- 8. The Deck will not boot to Gaming Mode at all. That is rarely Decky’s fault. Follow our Steam Deck won’t turn on fix before you reinstall anything.
- 9. Settings reset after reinstall. If you deleted ~/homebrew you lost them. Restore from the tarball with tar -xzf into your home folder, then restart the service.
- 10. Nothing here matches. Run the step 13 script with the backup flag, copy the output, and open an issue on the project’s repository after searching existing reports. The project also points users with basic questions to its community chat.
Advanced Tips: Debugging, Rollbacks and Safer Updates
Keep the CEF debugger handy
The remote debugging switch from step 4 is the best diagnostic tool you have. Turn it on before a big update, not after. When Steam’s interface changes, the console in the SharedJSContext target shows precisely which property went missing. That is how the commenter in issue #988 found the split module, and it is how plugin authors verify fixes. Leave the switch off during normal use if you prefer, since it opens a debugging port on your Deck’s network address.
Stage updates instead of taking them blind
Stage your updates in a safe order. Wait a few days after a Steam client change before you opt into any beta. Let SteamOS update first, run the doctor script, then update Decky, then plugins. Valve’s stream of SteamOS 3.9 builds, from the 3.9.0 preview on August 28 through the 3.9.2 beta on September 25 and the 3.9.3 beta on October 16 to the 3.9.4 beta reported on October 22 and the 3.9.5 stable on October 23, shows how quickly the base moves. Each step is a chance for a mismatch, and each is a reason to keep a backup.
Roll back a single plugin
If a new plugin version breaks, restore the old folder from your tarball without touching the rest. Extract only the plugin directory, restart the service, and report the regression to the author. Doing this beats a full reinstall because the loader keeps every other plugin working. Name your tarballs by date so you can find the last good one quickly. For more guides in this category, browse the gaming section on this site.
A final habit: read release notes before you update. The v3.3.0 changelog is short, five items, and it tells you everything that matters, from the new plugin update API to the third-party plugin warning. Reading it takes two minutes. If a release mentions an API change, wait a day or two for plugin authors to publish compatible versions, then update.
FAQ: Decky Loader on Steam Deck
Why is Decky Loader not working after the October update?
According to issue #988 on the project’s repository, a Steam client build split an interface class module, so the loader failed while rendering its title view. Decky Loader v3.3.0, the newest release, includes the fix. Install that version or newer and your plug icon should return.
What is the latest Decky Loader version?
As of October 25, 2026, the newest release on the upstream SteamDeckHomebrew repository is v3.3.0, published October 18. The one before it, v3.2.10, came out on October 4.
Will reinstalling Decky Loader delete my plugins?
Plugins and settings live in the homebrew folder in your home directory, and the installer flow in this guide does not target that folder for deletion. Back it up anyway with the tar command in step 2 so you can recover if something goes wrong.
Is Decky Loader safe, and does it void my warranty?
The official FAQ says Decky does not change Steam files and can be uninstalled at any time. It also says multiple people reported returning a Steam Deck under warranty after disclosing their use of Decky, while adding that you are responsible for the security of your device and your plugin choices. Valve has not published an endorsement.
Does Decky Loader work on Windows or other Linux distributions?
The project states that Decky is intended for the SteamOS installation on Steam Deck, with no plans to support other operating systems. Third-party SteamOS-style distributions are not officially supported. Version 3.3.0 adds ARM Linux and other platform builds, which you should treat as experimental.
Should I stay on the Steam client beta?
Only if you need a feature that exists nowhere else. The October reports cluster around beta client builds, so stable is the safer choice for anyone who relies on plugins. You can switch back to stable in the Steam settings at any time.
Does SteamOS 3.9.5 change how I install Decky Loader?
The install flow still runs from Desktop Mode: download the installer, run it, choose the latest release, then return to Gaming Mode. What changed is the desktop around it, with Plasma 6.7.3 and Linux kernel 7.2, plus the option to enable the Desktop Mode lock screen. Valve published no Decky-specific compatibility note in the 3.9.5 release notes.
How often should I run the doctor script?
Run it after every SteamOS update, every Steam client update, and every Decky release. It takes a few seconds, reads state only, and writes a backup when you ask for one with the backup flag.
