Why You’re Unable to Update Snap Store Because It Has Running Apps (and How to Fix It)

If you’ve been using Ubuntu for more than five minutes, you’ve probably seen that annoying little notification in the corner of your screen. It tells you there's an update for the "Snap Store," but when you actually try to click the update button, it fails. You get a cryptic message saying it’s unable to update snap store has running apps, followed by some random process IDs (PIDs) that look like a cat walked across a keyboard.

It's frustrating. Honestly, it’s one of those "Linux moments" that makes newcomers want to pull their hair out. Why can't the store just update itself? It’s a bit like trying to change a tire while the car is still doing 60 mph on the highway. The system won't let you replace the files because the program is currently using them.

The Ridiculous Loop of the Snap Store

The Snap Store (which is technically just a rebranded version of gnome-software or the newer ubuntu-app-center) is itself a Snap package. This is where the logic breaks down. To update a Snap, the snapd daemon needs to unmount the current version and mount the new one. But since you’re using the Snap Store to find the update, the Snap Store is running.

You can't use a program to kill itself and then revive itself in a new version. Not without some clever background magic, which—let's be real—Ubuntu hasn't quite perfected yet in the GUI. Even if you close the window, the process often hangs out in the background to make the store "launch faster" the next time you need it.

How to Actually Fix the "Running Apps" Error

You've probably tried closing the app window and clicking "Update" again. It didn't work, did it? That’s because the background process is still clinging to life. To fix the unable to update snap store has running apps error, we have to get our hands a little dirty in the terminal.

The Reliable Terminal One-Liner

The fastest way to handle this is to force the store to quit and then immediately tell the system to refresh it. Open your terminal (Ctrl+Alt+T) and paste this:

killall snap-store && sudo snap refresh snap-store

Basically, killall sends a "stop" signal to every instance of the store. The && tells the computer, "Hey, if that first part worked, immediately do the next part."

What if killall Doesn't Work?

Sometimes the process is stubborn. If the command above gives you an error or nothing happens, you might need to be more aggressive. You can check exactly what is blocking the update by running:

sudo snap refresh

The output will show you a specific PID (Process ID). It might look like pids: 1234. You can then manually terminate that specific process:

💡 You might also like: Whose Phone Number Is This Free: What Most People Get Wrong

sudo kill -9 1234

(Replace 1234 with the actual number you saw). Using -9 is the "nuclear option." It doesn't ask the program to close nicely; it just cuts the power. Once it's dead, run the refresh command again.

Why Does This Keep Happening?

It’s a design choice that many in the Linux community find, well, annoying. Since Ubuntu 22.04 and 24.04, the desktop environment treats the app store as a persistent service.

• Background Refreshing: Even when you aren't looking for apps, the store checks for updates for your other Snaps (like Firefox or Discord).
• Snap Design: Snaps are mounted as read-only squashfs file systems. You literally cannot change the files while they are mounted and active.
• User Interface Limits: The graphical "Software" app isn't designed to handle its own self-destruction during an update cycle smoothly.

Some people suggest just waiting. Eventually, snapd is supposed to update these things in the background when the system is idle or during a reboot, but we all know that "eventually" can feel like forever when that notification won't go away.

Alternative: The GUI Method (No Terminal)

I get it, not everyone wants to type commands. If you’re allergic to the terminal, there is a way to do this using the System Monitor.

1. Open System Monitor from your app list.
2. Click the Processes tab.
3. Click the magnifying glass and search for "snap-store" or "software."
4. Right-click the process and select Kill or End.
5. Quickly open your "Software Updater" (the one for system updates, not the store itself) or wait for the system to auto-trigger the refresh.

Honestly, though? The terminal is faster.

Can You Just Disable Snap Updates?

You can, but it’s usually more trouble than it’s worth. You can set a "refresh hold" if you're on a metered connection or if you're just tired of the pop-ups, but eventually, you'll want those security patches.

If you're truly fed up with the Snap Store's behavior, some users go as far as removing it entirely and replacing it with the standard gnome-software (the non-snap version) or using Flatpaks. But for most people, just knowing the killall command is enough to keep the peace.

💡 You might also like: What is ln 1? The Math Secret Everyone Forgets After High School

Actionable Next Steps

• Immediate Fix: Run killall snap-store && sudo snap refresh in your terminal right now to clear that pending notification.
• Check for Other Blocks: If it still won't update, check if other apps like Firefox or Thunderbird are also "running" and blocking a general sudo snap refresh.
• Check Your Version: If you are on an older version of Ubuntu (like 20.04), consider moving to a newer LTS where the snapd messaging is at least a little bit clearer about what's happening.

Stopping the process manually is the only way to break the loop when the system gets stuck. It’s not elegant, but it works every time.