Avast working on fix after CCleaner uninstall also removed other programs

midian182

Posts: 9,741   +121
Staff member
Facepalm: System cleaning app CCleaner has made the headlines quite a bit over the last few years, but most of it hasn't been good publicity. Keeping with that trend, one user recently found that deleting it from his PC also erased most of his other programs. Owner Avast has acknowledged the issue can happen in some circumstances and is working on a fix.

Reddit user rounakr94 (via BetaNews) earlier this week wrote that when they deleted CCleaner 5.91 from their PC, they noticed in the progress bar that some MSI, Steam, and Origin files were also being removed. Once the process was complete, Adobe reader, Afterburner, Aida64, Steam, Origin, Discord, HDsentinel, and more were all corrupted, though not uninstalled completely.

rounakr94 then spent two hours reinstalling the deleted software and fully scanning his PC for any signs of malware—an action you would likely take in such a situation.

The scan came back clean. Another user enquired where CCleaner had been installed, to which rounakr94 replied that it had been on the D: drive, the same drive where the deleted/corrupted programs had resided.

A developer on the Piriform Forums said: "CCleaner should be removing everything from its installation directory is, under normal circumstances, exactly what you would want CCleaner to be doing. Not just the files from its original installation manifest but any updates, log files, etc so that it does not leave any traces of itself behind."

That obviously didn't appease rounakr94, who complained that such action resembles either bad coding or simple revenge tactics for removing CCleaner.

Avast has now acknowledged that in some circumstances, deleting CCleaner can remove other programs not associated with the app.

"CCleaner's default behavior when installed is to create a new 'CCleaner' folder, so at the point of uninstall, everything in that folder can be deleted without issue. In the case described in this article, a user would need to deliberately bypass this behavior and either choose to install CCleaner to a folder they currently use for other purposes or later use the 'CCleaner' folder for something other than its intended use," said an Avast spokesperson.

The company is now working on an update to prevent similar incidents from happening again.

CCleaner hasn't received much positive coverage since it was acquired by Avast for $1.3 billion in 2017, the same year malware was discovered lurking in the app. There were the privacy issues in 2018 that saw the active monitoring feature turn itself back on even after users disabled it; complaints that CCleaner was installing Avast anti-virus without permission; and Windows Defender flagging the free version of the tool as a Potentially Unwanted Application (PUA).

Permalink to story.

 
That program is garbage
No it isn't. It's very useful. No software is perfect. CCleaner was installed to not only a custom folder, but also a non-OS drive. This can cause very serious problems on a programmatic level for some software. If the user who had the problem had installed it to the typical directory, the glitches they encountered would not have occurred. Problems like this will happen with other software as well. Older versions of Chrome didn't like being installed to non-standard directories either and uninstalling afterwards caused Windows installation corruption that running SFC couldn't fix.
 
Interesting bug, I've used CCleaner for years with a break in 2017 when they had some problems. The older version worked fine back then. I found the recent versions are fine other than containing some nagware that attempts to "upgrade" you to a version with more features for a price (that I find useless).

Personally, I always let programs install to their default directory so I don't encounter any strange issues. There has been many programs over the years that can get buggy if you don't - especially with respect to uninstallation.
 
I think I stopped installing CCleaner just before they got acquired by Avast. It’s ironic that a good application became a “potentially unwanted application”, “malware installer”, and used to actively monitor people’s usage after being taken over by a supposedly anti-virus/ computer security company. It just goes to show that installing less is best nowadays.
 
Older versions of Chrome didn't like being installed to non-standard directories either and uninstalling afterwards caused Windows installation corruption that running SFC couldn't fix.
That is also Microsoft's fault, unless Chrome deleted SFC or the files it uses to repair Windows.
 
That is also Microsoft's fault, unless Chrome deleted SFC or the files it uses to repair Windows.
Very likely. Still, it was a programmatic problem that was not necessarily the fault of the programmers. As such laying negativity and implying blame, like what is displayed in these comments, seems needless.
 
Back