Avast 2014 blocks CCleaner functions on Win7-64 bit systems?

Hello,
I have installed Avast 2014 Free in 6 computers.
One of them is running Windows XP 32 bit, one is running Windows 7 Starter (32 bit). All seems to work correctly.
The remaining four pcs are running Windows 7 64 bit and in these computers CCleaner can’t disable or enable Startup processes. I receive the error “Failed to enable/disable startup item: Access denied”.
I uninstalled Avast, then CCleaner worked correctly again. I reinstalled Avast then CCleaner stopped to work.

Someone can help me please?

I hope I explained well the problem, sorry for my english… :slight_smile:

Im having the same problem. 32 bit is fine, just 64… I hope this gets figured out:)

You can upload files and report issues to avast here: http://www.avast.com/contact-form.php (select subject according to Your case)

Please also report it to Piriform
http://www.piriform.com/support

Thank you:) And there was only a problem after the update to 2014.

any news on this? If I had known this would happen I would’ve stayed on the previous version :confused: It’s too much of a pain to rollback now.

I know I’m late to this thread but have you tried making the exclusion in avast? ???

I tried now and it doesn’t work :confused:

I believe tomorrow there will be new version of CCleaner so maybe problem
with Startup manager will be fixed.

CCleaner v4.07.4369

http://www.piriform.com/ccleaner/download

And this pretty much reflects the relevance of majority of 2014-related comments here.

v4.07.4369 (24 Oct 2013) - Added Windows 8.1 compatibility.

Nevermind the previous versions have not been W8.1 compatible at all, must be Avast fault of course. ::slight_smile:

I can only test in my own system, CCleaner for Windows 4.07.4369 is working perfectly on Win 8.1 x64.

Just found the solution to the problem, well I know it is a temporally one, but hey till avast will fix this, here is the deal: Go to settings- Troubleshooting and from there deselect avast self defense module, after you disable all the unwanted start-up processes with ccleaner make sure you re-enable avast self-defense module.

Regards, RealNature

Well I ques this problem is happening only in w7x64

In that case why not just use Windows System Config’ to change startup processes?

Running W7 x64, Ccleaner, no problems.

Yep after I reinstalled my windows 7 sp1 x64, no problem here, I can confirm this :slight_smile:

Edit: Well not entirely, after I installed Adobe PS5, I can’t disable some start-up process of Adobe with Ccleaner, I have to disable again the avast self-defence module. So reinstalling the windows partially fix this issue, but with some specific process like Adobe, and maybe others who knows apparently you need to disable avast self-defence module.

I can confirm that on Windows Pro 64 bit, with Avast! 2014 and CCleaner 4.07.4369 64 bit, some startup items can be enabled/disabled in CCleaner, and some can’t. They return the message “Failed to enable/disable startup item: Access is denied”.

With those items, disabling Avast! self-defence module allows the changes to be made.

Hello,

I have the same problem.
I think only startup processes in folder HKLM\Software\wow6432nod\Microsoft\Windows\CurentVersion\Run are affected, because there is also an AVAST entry (see Screenshot). So this Folder is protected by AVAST. AVAST have to change their self-defence settings.

Greetings
Christian

I DO have the reported problem: on Win 7 Ultimate 64bit with actual CCleaner and Avast 2014, in CCleaner Tools Menu / Startup it is no more possible to deactivate common entries like Adobe ARM or Java Update Scheduler.

  • It took about 10 hours of work until I discovered this thread. I thought I had problems with access control / security items, tried and retried to take ownership with my (admin) user of simply everything. When this failed, I came to this forum. Gladly somebody had started the thread, thank you so much.

This moment I experience even worse problems, like CCleaner Clean hanging, SWEEPI Clean hanging (SWEEPI is great, experience it!). Not sure whether this is although fault of Avast.

I already informed exceptions in Avast, and this moment I totally deactivated Avast in his options menu. The problems still persist. Next step: I will do a total deinstallation of Avast 2014 (my personal and subjective recommendation).

Even though I am very grateful for the past time excellence of Avast Free Antivirus, it has been the n°1.