High CPU usage after most recent update--System Monitor shows 'gnome software' as the culprit

I never had this issue before the most recent update--my system ran great. Now, it's huffing and puffing all the time. Fan's going nuts. gnome-software often jumps up to 40% of CPU.

Mission Center shows 'Windows App Support' using up most of the CPU, but I never installed Windows App Support on my system. Was it part of the most recent update?

So, I tried installing and then uninstalling Windows App Support. But, to no avail--Mission Center still shows 'Windows App Support' using the most CPU.

So, with System Monitor, when I right click on 'gnome-software,' I see this under Properties:

Does anyone know what's happening here? Like I said, my system was working great before the most recent update.

UPDATE shortly this initial post: I killed gnome-software in System Monitor. Everything seems to still be working fine and the CPU spikes are gone. The gnome-shell is still there and still fine.


This is very confusing.

ANOTHER UPDATE: gnome-software is still in my tasks, but it's behaving now:

This is very confusing.

Welcome to the Forum!

So, gnome-software works normal now? Because on Your last Picture is a Layer over the Values.

And because of Windows App Support: If You don#t have install it, it could be the Shortcut to install it. But that should need any System Ressources. But You could try to uninstall it with the Terminal Command:

sudo apt purge zorin-windows-app-support-installation-shortcut

Thanks for the info--I ran the terminal command. Right now, everything seems to be working fine. I had to close out gnome-software, as I mentioned, via System Monitor, and now it appears to be normal.

I'm still not really sure what was happening there, but it seems to be okay now. My old desktop isn't wheezing.

1 Like

It might have just been tat the software store got stuck while checking for updates, or installing one. Unfortunately it can be erratic at times. I've seen it take well over 10 minutes to install something that through the terminal took less than 10 seconds. As usual, reboots can do wonders.

2 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.