Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: d4mnm4d on October 16, 2013, 09:48:58 AM
-
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... :)
-
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 (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 :/ 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 know I'm late to this thread but have you tried making the exclusion in avast? ???
I tried now and it doesn't work :/
-
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
-
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. ::)
-
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
-
I can only test in my own system, CCleaner for Windows 4.07.4369 is working perfectly on Win 8.1 x64.
Well I ques this problem is happening only in w7x64
-
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... :)
In that case why not just use Windows System Config' to change startup processes?
-
Running W7 x64, Ccleaner, no problems.
-
Running W7 x64, Ccleaner, no problems.
Yep after I reinstalled my windows 7 sp1 x64, no problem here, I can confirm this :)
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.
-
I can confirm too, problems enabling/disabling/removing some startup items. It works for some, but not for others...
I think you're on to something with the theory about avast protecting the whole syswow64 registry section instead of only its entry...
-
+1. I too cannot remove startup entries using Ccleaner... very annoying.
-
And still in 9.0.2008, no changes in this issue(problem still occur) :-\
-
If the latest AVAST update is having issues with CCleaner I'm sticking with my old AVAST and not even going to think about updating.
CCleaner is a tool I use every day for managing restore points, cookies, cache and registry cleaning, secure deletion and disabling/enabling start up items. I've had issues with past versions of AVAST, the AvastUI in start up in particular and CCleaner helped identify and sort out that for me.
CCleaner is simply the most useful tool for doing this - try managing your restore points or basic start up items using Windows itself and there's no contest, CCleaner wins every time for convenience; it should be in everyone's PC software toolkit.
If you have to disable something in AVAST to get CCleaner to function fully again then it is AVAST's fault not Piriform's. What user wants to have to disable the AVAST SDM for any reason? I want an AV to do its job unobtrusively and that doesn't mean just providing protection it means doing that without interfering with the workings of other perfectly safe and widely used programs like CCleaner.
-
If you have to disable something in AVAST to get CCleaner to function fully again then it is AVAST's fault not Piriform's.
1. I have never experienced any issue between avast and CCleaner and use both side by side.
2. On contrary of what you've said, it's CCleaner which is trying to "clean" avast! and not the opposite. CCleaner is trying to do more than it can do safely (for the user, for the computer, for the security).
My 0.02.
-
If you have to disable something in AVAST to get CCleaner to function fully again then it is AVAST's fault not Piriform's.
1. I have never experienced any issue between avast and CCleaner and use both side by side.
2. On contrary of what you've said, it's CCleaner which is trying to "clean" avast! and not the opposite. CCleaner is trying to do more than it can do safely (for the user, for the computer, for the security).
My 0.02.
I agree with Tech on this, CCleaner is sticking it's nose where it doesn't belong, the Avast boxes under CCleaners applications list should be unticked as with all security software listed in there ( WinPatrol, Malwarebytes, Defender, etc ) CCleaner have no business in these areas and should be removing those options imo.
-
CCleaner have no business in these areas and should be removing those options imo.
Just to make it clear. If any other program could "change" or "mess" the antivirus files, well, security will be compromised.
On other hand, we can always complain and complain IF avast! is not doing a good job on housecleaning.
-
.. CCleaner is sticking it's nose where it doesn't belong...
I'm sorry to disagree. The problem central to this thread has been clearly identified as Avast's self defense module protection extending beyond its own settings and impeding the functionality of other commercial software. This is clearly an issue that Avast should be addressing, and I would suggest, with some urgency.
-
I'm sorry to disagree. The problem central to this thread has been clearly identified as Avast's self defense module protection extending beyond its own settings and impeding the functionality of other commercial software. This is clearly an issue that Avast should be addressing, and I would suggest, with some urgency.
+1
blocked autostart entries or energy settings are a problem of Avast and not of CCleaner.
Greetings
Christian
-
Thanks for report. Next release/update will contain fix for this issue.
-
.. CCleaner is sticking it's nose where it doesn't belong...
I'm sorry to disagree. The problem central to this thread has been clearly identified as Avast's self defense module protection extending beyond its own settings and impeding the functionality of other commercial software. This is clearly an issue that Avast should be addressing, and I would suggest, with some urgency.
Sorry. I did not realize that. Thanks for the heads up olddog.
-
I'm interested in the comments here about the matter of CCleaner putting its nose into Avast when it's not wanted. With CCleaner you have a choice whether or not to include Avast. If getting rid of some , most likely, unnecessary logs which most people never see because by Avast puts them in folders Windows hides by default, then simply untick the Avast entries in the Applications > Utilities.
But the fact is CCleaner has always included Avast log cleaning by default and any other action it is capable of relating to Avast could be performed without issue until now. Avast's behaviour has apparently changed not CCleaner.
-
I'm interested in the comments here about the matter of CCleaner putting its nose into Avast when it's not wanted. With CCleaner you have a choice whether or not to include Avast. If getting rid of some , most likely, unnecessary logs which most people never see because by Avast puts them in folders Windows hides by default, then simply untick the Avast entries in the Applications > Utilities.
But the fact is CCleaner has always included Avast log cleaning by default and any other action it is capable of relating to Avast could be performed without issue until now. Avast's behaviour has apparently changed not CCleaner.
Is the issue that CCLeaner cannot get rid of logs or that people are trying to use the disable autoruns for STARTUP in TOOLS section of CCLeaner ? If it is the autoruns why do people not just use MSCONFIG in the O/S ?....or a M/S util which is even better...just Google Microsoft Autoruns utility.
http://download.cnet.com/Autoruns/3000-2094_4-10744886.html
-
Is the issue that CCLeaner cannot get rid of logs or that people are trying to use the disable autoruns for STARTUP in TOOLS section of CCLeaner ? If it is the autoruns why do people not just use MSCONFIG in the O/S ?....or a M/S util which is even better...just Google Microsoft Autoruns utility.
The issue is that Avast self protection is preventing the enabling or disabling of some Startup items in CCleaner Tools section.
Yes, an alternative would be to use MSCONFIG, or Autoruns, but CCleaner is a legitimate program with a larger user base. Why should its users be forced to use an alternative because of the present poor coding of Avast. Avast have known about this problem for some time but have yet to remedy it. I suspect they would not appreciate such slow reaction if the boot was on the other foot.
-
Avast have known about this problem for some time but have yet to remedy it.
Well, I think it was acknowledged that it will be corrected in the next program upgrade...
-
Don't know if you have solved this problem but the easy fix is simply to add CCleaner to your exclusion list in Avast. It can be found in Settings - Antivirus. Use the browse button to find your installation of CCleaner and then add it. After having done this to my installation (Win 7 64bit), all the functions in CCleaner started to work normally.
Hope this helps.....
-
CCleaner works on both my systems (win XP Pro and win7 32bit) without having any exclusion.
So is this a 64bit issue or probably you are having ccleaner clean avast elements ?
If you are having ccleaner clean avast elements (logs, etc.) then I would suggest that you leave them alone and allow avast to do its own housekeeping.
-
It has nothing to do with the cleanup function! The Ccleaner page 'tools' -> 'startup' is a way to enable/disable/remove startup items (which can be seen in msconfig as well). It is a separate function that does not affect Avast.
-
It has nothing to do with the cleanup function! The Ccleaner page 'tools' -> 'startup' is a way to enable/disable/remove startup items (which can be seen in msconfig as well). It is a separate function that does not affect Avast.
It will if it is trying to remove an avast startup entry as the self-defence module will kick in. After all that is the purpose of the self-defence module to prevent unauthorised removal or disabling avast.
Unless you are saying that this permission/access is denied when you try to remove non-avast entries, but I don't see anyone stating which startup entries they are trying to remove.
I tested this on my XP Pro system on my dropbox startup entry, it allowed me to first of all disable a startup entry and then remove it completely. I got the cautionary CCleaner popup, but avast 9.0.2008 or the self defence module had any objection.
-
If you actually read you'd see that even OTHER startup items are blocked, not only avast's entries. None of the processes can be deleted. THAT's the problem, not the self-defense. That's all good and well, and working as intended.
-
If you actually read you'd see that even OTHER startup items are blocked, not only avast's entries. None of the processes can be deleted. THAT's the problem, not the self-defense. That's all good and well, and working as intended.
That's why I ran the test myself and I was able to first disable and then delete without any input from avast, that is what is strange for me.
-
(http://content.screencast.com/users/Propheticus/folders/Jing/media/28cee6d9-b36c-43c1-9dd3-a65620c87be7/2013-11-29_0128.png)
Happens with some, but not all entries. I Was able to remove Evernote for instance.
-
<snip image>
Happens with some, but not all entries. I Was able to remove Evernote for instance.
That's the problem, the inconsistency of it, if this were truly avast blocking then wouldn't it be blocking all or none not just some.
-
Thanks for report. Next release/update will contain fix for this issue.
@DavidR
Avast self defense is protecting all startup entries in HKML/Software/Microsoft/Windows/Current Version/Run
although it should protect only Avast startup reg key.
Not all startup entries are in HKML/Software/Microsoft/Windows/Current Version/Run and they can be disabled/deleted by CCleaner.
Personally,I don't have problems with Avast and CCleaner in Windows 7 x86.
It looks like Windows 7 x64 is affected by this bug.
-
Avast self defense is protecting all startup entries in HKML/Software/Microsoft/Windows/Current Version/Run
although it should protect only Avast startup reg key.
Not all startup entries are in HKML/Software/Microsoft/Windows/Current Version/Run and they can be disabled/deleted by CCleaner.
Personally,I don't have problems with Avast and CCleaner in Windows 7 x86.
It looks like Windows 7 x64 is affected by this bug.
+1
see also my previous post in this thread
Greetings
Christian
-
Thanks for report. Next release/update will contain fix for this issue.
@DavidR
Avast self defense is protecting all startup entries in HKML/Software/Microsoft/Windows/Current Version/Run
although it should protect only Avast startup reg key.
Not all startup entries are in HKML/Software/Microsoft/Windows/Current Version/Run and they can be disabled/deleted by CCleaner.
Personally,I don't have problems with Avast and CCleaner in Windows 7 x86.
It looks like Windows 7 x64 is affected by this bug.
Yes, it would appear it is 64bit OS related as I could remove the HKCU:Run and even HKLM:Run entries in XP Pro 32bit