Unwanted Version 7 Pro is constantly regenerating

CCleaner for Windows
1

I installed 7 Pro and found there were things missing and not working all known problems when I asked for help. On top of which I do not like the 7 version. So I asked support for help reverting back to Version 639. I followed the instructions and uninstalled 7 using Revo and reinstalled 6 using the download link at the website. That worked the first time. The next time I clicked to open 6, the 7 installer took over my PC. I did everything I know how to do including locating the installer file and removing it with every known method and softwares. From then on I could no longer use CCleaner because the installer would pop up. Last night my PC was on and the installer loaded down 4 copies of 7 during the night.

Earlier this evening I used the chat bot at Support. I follwed all the suggested methods to the letter to no avail. Including downloading 6 via the link my license renewal on my email. That failed and the chatbot disconencted.

Just now i went through all that the Chatbot requested and was put on que for a live representative. After 45 minutes of watching the screen I gave up.

The Version 7 Pro obvioulsy has more bugs than any beta version and should have never been released. I have now paid for a subscritption to a product I cannot use and cannot really talk to anybody in support.

Time to uninstall permanently .

1 Like
2

I completely empathize with you. I have the exact same problem. CC v7 is a major bug bomb. It corrupted various systems in Windows 10 Pro on my PC. I had to run a Restore Point to recover W10. Then I used Revo to uninstall CC v7 and installed v6.39. But v7 continues to attempt installation. I can’t find a way to stop it. And CC Inc charged me $39.99 to renew my SINGLE license in September. I may ask my credit card to do a chargeback to get a refund.

3

I was contemplating notifying AMEX that I received a defective product and am getting nowhere with the vendor.

4

Did you turn off automatic updating in version 6 when you reinstalled it?

5

I am having the same issues on two computers on Win11. Ran Pro 6 for two weeks without problems then Beta 7 took over. Deleted everything using Revo, cleaned out any CCleaner reference, reloaded my 638 Pro download, put in license, and it worked once. Next time I tried it, it reverted to the Beta 7 version. This needs to be addressed.

6

How to Stop CC v6.39 From Updating to Buggy CC v7 - CCleaner for Windows / CCleaner Windows Bug Reporting - CCleaner

CrapCleaner version 7 is a major bug bomb that alters Windows 10 settings and corrupts W10 system files. It is wise to uninstall CC v7 and revert to stable version v6.39. The catch is that v6.39 has built-in mechanisms to ‘force’ an update to v7.

The way to stop v6.39 from updating is not obvious … but here is how:

The First Step is uninstalling CC version 7. The common way is to use Windows native method for uninstalling an application software (ie. CCleaner), but that method often leaves behind remnants of the uninstalled application. For a complete clean uninstall of CC v7, use an app called Revo Uninstaller (it is ‘paid’ software that offers a free trial period to use the full Revo version, allowing you to completely uninstall CC v7). Reboot Windows after uninstalling CC v7.

The Second Step is to install CC v6.39. Download CC v6.39 for Windows 10 / 11 here: https://download.ccleaner.com/ccsetup639.exe

[For detailed instructions on uninstalling CC v7 and installing CC v6.39, see the article here: How to Roll Back from v7 to v6.39 - CCleaner for Windows - CCleaner How to Roll Back from v7 to v6.39 ]

OVERVIEW: To stop CCleaner 6.39 from ever updating itself to version 7, you need to (1) disable automatic updates inside CCleaner, (2) block its update service and scheduled task, and (3) use a firewall rule to prevent CCleaner from contacting its update servers. This combination ensures version 6.39 stays frozen.

Step‑by‑Step: Prevent CCleaner 6.39 from Updating

I. Disable Updates in CCleaner Settings

  1. Open CCleaner.

  2. Go to Options → Updates.

  3. Uncheck ‘Keep CCleaner updated automatically’.

  4. Uncheck ‘Send notifications when there is a new version of CCleaner’.

  5. Close CCleaner.

(This alone is not always enough, because CCleaner can still eventually force updates, so continue with the next steps.)

II. Disable CCleaner in Windows Task Scheduler

  1. Press Windows key + R, type taskschd.msc, and press Enter.

  2. In Task Scheduler, expand Task Scheduler Library → CCleaner.

  3. Look for a task named CCleaner Update or CCUpdate.

  4. Right‑click → Disable.

(This prevents Windows from running CCleaner’s background updater.)

III. Stop the Update Service (IF present)

  1. Press Windows key + R, type services.msc, and press Enter.

  2. Look for CCleaner Update Service (sometimes called CCUpdate).

  3. Right‑click → Properties → set Startup type to Disabled.

  4. Click Stop if it’s running.

IV. Block CCleaner from Contacting Update Servers

  1. Open Windows Security → Firewall & network protection → Advanced settings.

  2. Create a new Outbound Rule

  3. Program: point to CCleaner.exe and CCUpdate.exe (usually in C:\Program Files\CCleaner).

  4. Action: Block the connection.

  5. Apply to all profiles.

(This ensures CCleaner cannot download update files.)

V. Block CCleaner’s Triggers for Automatic Updates.

Open Windows Task Scheduler and Click Task Scheduler Library

  1. In the main directory list, look for and click CCleaner Update (which should show Disabled)

  2. In the lower section below the Library List (after highlighting CCleaner Update), click on and highlight the Triggers tab.

  3. Click on Properties in the right-side column. Then click the Triggers tab in Properties.

  4. Click the ‘Daily’ trigger to highlight it. Then click the Edit button. Uncheck the box for Enable under Advanced Settings.

  5. Repeat the above process for the ‘At startup’ trigger.

If you do all the above steps correctly, you will not have to worry about CC v6.39 updating to CC v7. CCleaner 6.39 will remain locked in place and won’t auto‑upgrade to version 7.

Important Notes

  1. Pre-v7 CCleaner versions may attempt forced updates, even with auto‑update option disabled in CC v6.39. Blocking the updater service and firewalling the executables is the only way to guarantee you stay on 6.39.

  2. By freezing on 6.39, you won’t receive security patches.

  3. Keep a copy of the CCleaner 6.39 installer (ccsetup639.exe) so you can reinstall if needed.

7

Note that if you start blocking CCleaner.exe in your Firewalls then parts of CCleaner may/will stop working properly.

There is of course a much, much, simpler way of ensuring that the CCupdate.exe does not run at all.

  1. Open File Explorer and go to C:\Program Files\CCleaner
  2. Delete CCupdate.exe

Job done. If the CCupdate.exe isn’t there then nothing can run it on a schedule or a trigger.

You can leave the schedules. triggers, etc. as they are - because there is nothing for them to run when they try.
Plus of course if there is no updater to run then you don’t need to block it in your Firewalls.

I have had the deletion of CCupdate.exe in my CCleaner 'Includes; for a number of years.
Each time I manually updated CCleaner then a new CCupdate.exe was created, but as I had it as an include then the first clean I ran simply deleted it again.

8

Sorry but it didn’t work and when I looked. The installer replicated two copies to install.

Thanks for trying to help me.

9

This is where the glitch is. After I install and I click on anything in win 6 the 7 installer regenerates and starts the install. Effectily blocking any access to 6 and it’s controls.

10

Re-install 6.39 and run. It will start the first time after re-installation.
Go to Options-Update and uncheck all boxes.
After that 6.39 will run normally.

11

When you are reinstalling v6.39 the verly last page if the installer has two tickboxes the first one is “Run CCleaner” have it ticked so that v6.39 opens to finish the install.
Go immediately to Options>Updates and untick both boxes there.
Close v6.39 and it should no longer try to update when opened again.