Jump to content
CCleaner Community Forums

arensky

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About arensky

  • Rank
    Newbie
  1. Thanks Imacri, I did run the Avast uninstall so should be OK. Seeing the comment that Ccleaner can recommend improvements to PC security - I have no problem with recommendation but just installing Avast without question is not recommending (there was no obvious indication or checkbox - and I do look for these). Anyway, thanks for the tip on the portable build version. I shall use that from now on.
  2. Thanks Rubeus; yes agreed this appears to work. I wasn't intending to upgrade until Piriform/Avast advised that the issue is resolved. Interestingly, I loaded this release onto a new Windows 10 PC (using Windows Defender by default) and, without asking, the installer loaded the Avast Anti-Virus; this is most inappropriate. I had then to uninstall the AV as, a friend, the ultimate user of this PC, prefers another AV that they're supplying next week. I do trust that this isn't indicative of a new direction for Ccleaner under its new management. This AV issue may be an appropriate new subject on this forum.
  3. I posted this a few hours ago on topic #52341 - it's relevant to this topic too - I hope it helps. With Windows 7; what I have discovered is that if you run CCleaner.exe (13364kb) rather than CCleaner64.exe (18100kb) the program seems to deactivate the monitoring as requested and keeps it deactivated. The version is still V545.6611 and both are in the CCleaner program folder. Curiously the CCleaner.exe version appears also to run the 64bit version - at least that's what it says - if you believe anything anymore. UPDATE: With Windows 10 - 1803 the same functionality occurs as with Windows 7 above. (Note: Also with Windows 10 - 1803 on a 32bit PAD) But initially the CCleaner.exe program does load the CCleaner monitor and this needs to be deleted from the Registry else it will initialise at start up - though you can stop it running at the UAC prompt. These are just workarounds - AVAST should fix this problem. It's very disappointing and I trust this error is not a sign of things to come! UPDATE for 64bit Windows: My comment above "Curiously the CCleaner.exe version appears also to run the 64bit version" If the OS is 64bit, then yes it does - so just rename the CCleaner64.exe program to something else and then as the program cannot be found it cannot be run. The 32bit version doesn't appear to display the same issue.
  4. With Windows 7; what I have discovered is that if you run CCleaner.exe (13364kb) rather than CCleaner64.exe (18100kb) the program seems to deactivate the monitoring as requested and keeps it deactivated. The version is still V545.6611 and both are in the CCleaner program folder. Curiously the CCleaner.exe version appears also to run the 64bit version - at least that's what it says - if you believe anything anymore. UPDATE: With Windows 10 - 1803 the same functionality occurs as with Windows 7 above. (Note: Also with Windows 10 - 1803 on a 32bit PAD) But initially the CCleaner.exe program does load the CCleaner monitor and this needs to be deleted from the Registry else it will initialise at start up - though you can stop it running at the UAC prompt. These are just workarounds - AVAST should fix this problem. It's very disappointing and I trust this error is not a sign of things to come! UPDATE for 64bit Windows: My comment above "Curiously the CCleaner.exe version appears also to run the 64bit version" If the OS is 64bit, then yes it does - so just rename the CCleaner64.exe program to something else and then as the program cannot be found it cannot be run. The 32bit version doesn't appear to display the same issue.
×
×
  • Create New...