Google Chrome Cleanup / Software Reporter Tool HIGH CPU

Google Chrome Cleanup / Software Reporter Tool “software_reporter_tool.exe” Was running multiple processes (12 to be exact) and pegging my CPU usage meter.

I found this out by bringing up my task manager and observed the multiple processes running. Killing one or more services just popped up more. The name in my process manager is “Chrome Cleanup Tool.”

chrome cleanup tool processes
Win7 Pro 64 Process Manager – 96 Processes 100% CPU Usage

The system fan was whirling like mad trying to cool my CPU down.

Thinking id be cute – i deleted that sucker.. Walla.. 😆

But wouldn’t you know.. chrome cleanup tool came right back. 🙄

chrome cleanup tool directory files
Files in Google Chrome SwReporter 4.30.1 Directory. Google re-installs after deleting directory.

Next i deleted it’s whole directory.. But Google just re-downloaded all the files and re-created the directory, and my cpu meter was pegged again..

Running Win 7 Pro 64 Bit.

Any suggestions? 😉

Update 09/15/2015: OK here’s a quick fix until Google fixes the running of multiple processes in their Chrome Cleanup Tool. Simply uncheck ‘protect you and your device from dangerous sites.’ a quick fix until Google makes an update.

How to disable chrome cleanup tool
Uncheck protect you and your device from harmful sites. This disables chrome cleanup tool.

I'm an outspoken good ole southern boy. Fidonet computer bulletin board system operator, hobbyist webmaster, and MAGA blogger. Just hanging out in cyberspace keeping up with tech, 'blogging my opinion' without beating around the bush!

Notify of
Most Voted
Newest Oldest
Inline Feedbacks
View all comments
Charles Fitch
Charles Fitch
December 26, 2017 10:38 PM

Just find out what registry entry it is and rename it for example if its “report” name it “reportnulled” so you know what it is.

Mo Qy
Mo Qy
September 22, 2015 4:22 AM

problem has disapeared on my side . a software update released by google ?

September 16, 2015 5:57 PM

You may have to clear your browser cache in order to make this change effective (I did, anyway). Thanks!