Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: REDACTED on January 24, 2015, 11:22:17 AM
-
What effect will this have in terms of functionality?
I have tried it and upon restarting, AvastSvc.exe still is running prior to my opening the user interface, doing any on-demand scans, etc. Also, historical scan data seems to show activity in the shields after startup, and prior to the user interface being manually opened or activated in any way.
-
what is it it you are trying to do? ...... and why?
-
what is it it you are trying to do? ...... and why?
just trying to figure out the utility of this item to see if it's needed.
-
if there is any module in avast you dont want, there is a correct way to remove them
Avast 2015: Changing, adding, or removing individual program components and features in setup configuration of Avast Antivirus
https://www.avast.com/en-eu/faq.php?article=AVKB96#artTitle
-
if there is any module in avast you dont want, there is a correct way to remove them
Thanks, but I'm not attempting to remove modules. I feel my initial post is very straight-forward, and that's what I'm looking to find out.
-
AvastSvc.exe
now why would you disable your antivirus?
-
AvastSvc.exe
now why would you disable your antivirus?
Question is in my first post:
Disable AvastUI.exe Startup Entry? What effect will this have in terms of functionality?
and my follow-up:
just trying to figure out the utility of this item to see if it's needed.
If that doesn't make sense to you, please refrain from attempting to help. Thank you
-
Disable AvastUI.exe Startup Entry? What effect will this have in terms of functionality?
as said above, it will disable vital parts of your AV
If that doesn't make sense to you, please refrain from attempting to help. Thank you
No it does not make sense ..... so i will follow your advice ;)
-
If anyone knows what specific effect disabling the AvastUI.exe startup entry has on program functionality, I'm curious to find out. Thanks
-
I'd consider it reverse engineering something that goes against the EULA. :)
It's an intricate part of the program.
-
I'd consider it reverse engineering something that goes against the EULA. :)
It's an intricate part of the program.
Definitely not my intention. I checked the EULA, and as I understand it, it is restricting users from reverse engineering with the intention of attempting to "discover the source code of the Software or algorithms contained therein."
I thought perhaps it is something really simple such as being the exe for loading the tray icon (which I'm not using). In any case, perhaps a moderator can shed a little light on the subject (as long as it doesn't reveal any proprietary code, etc :)
-
Why don't you just remove it and see what happens?
-
Why don't you just remove it and see what happens?
From my first post:
I have tried it and upon restarting, AvastSvc.exe still is running prior to my opening the user interface, doing any on-demand scans, etc. Also, historical scan data seems to show activity in the shields after startup, and prior to the user interface being manually opened or activated in any way.
--
So it seems the program is still functioning without the startup entry. However, I can't be sure to what degree, without someone more knowledgeable weighing in to share (if possible) what basic function this start-up entry has.
-
Without avastsvc.exe your protection will be reduced to nothing.
If you want protection leave it alone. If you don't want to be protected and
run the risk of infection(s) knock yourself out.
If I were you I'd leave it alone.
-
Without avastsvc.exe your protection will be reduced to nothing.
If you want protection leave it alone.
The question is regarding avastUI. As mentioned, avastsvc does not seem to be affected by disabling the avastUI startup entry, and nowhere did I mention the desire to disable avastsvc.exe. Again, as I previously posted (twice):
Disable AvastUI.exe Startup Entry? What effect will this have in terms of functionality? Just trying to figure out the utility of this item to see if it's needed.
-
If it wasn't needed, avast would not have programmed it.
-
The avastUI.exe is the interface between the User and the avast Program. Whilst it isn't specifically part of the antivirus protection element (avastSvc.exe) of avast, without it the user doesn't have the interface between them the program and I believe that extends to displaying avast alerts and any action buttons, etc on those popups.
It also has other functions not related to the protection, as users we aren't fully aware of all of these administrative type functions.
But the greater question would be why you are even considering trying to disable it, when as far as resources go it is a drop in the ocean. Certainly when compared with other running applications.
-
If it wasn't needed, avast would not have programmed it.
That's not true, and without knowing exactly what the startup entry does, such a statement is truly an assumption. Plenty of programs have startup entries that can be disabled without affecting core program functionality.
-
It sure is true.
Companies like avast are not gonna waste their time on things that are not needed.
-
18 replies and still no answer as to why you want to install part of a program that takes up very little space?
It's part of the program. If you don't like the program, then remove it.
-
1) Why are you so worried about nothing?
2) Which one are you asking about avastsvc.exe or the avastui entry?
3) Each is necessary for full functionality.
-
I was curious too but I believe DavidR had answered the question. It must have the same functionality as any other startup entries that resides on the system tray e.g VGA, Audio etc. Disabling it from starting at system startup should not affect the core functionality. And is there any entry in the T&C that actually says disabling the AvastUI.exe which brings up the interface will violate the EULA? I think not.
-
I was curious too but I believe DavidR had answered the question. It must have the same functionality as any other startup entries that resides on the system tray e.g VGA, Audio etc. Disabling it from starting at system startup should not affect the core functionality. And is there any entry in the T&C that actually says disabling the AvastUI.exe which brings up the interface will violate the EULA? I think not.
You may interpret reverse engineering differently than I do. Since this will never get to a courtroom,
it really is unimportant. :)
-
I was curious too but I believe DavidR had answered the question.
It must have the same functionality as any other startup entries that resides on the system tray e.g VGA, Audio etc.
Disabling it from starting at system startup should not affect the core functionality.
<snip>
I don't think that is generally has the same functionality as other startup entries as for the most part they are actually launching the program. AvastUI.exe isn't launching the program as in an AV it has low level drivers (System) and very early initiation, image attached. But it still requires the user level interface which is going to start later when a user account launches.
It may not effect core level functionality, but it could well effect other integration/usability/administrative functionality. Just how much, is certainly beyond this avast users experience and would require developer knowledge - I don't know if they would be too keen on giving detailed information on the workings of the avast program as a whole.
But for sure I wouldn't attempt to disable it because of the above and the fact that it uses minimal resources - if resources are an issue your system is in trouble already, also image1.
EDIT: image attached.
-
AvastUI performs all the "visible" (UI) operations - which the service running on a different session can't do.
So if you disable it, you won't see anything - if Avast blocks or deletes a file, you won't know (so it may get quite confusing if your files are disappearing and you don't know why). Some functionality won't be available (context menu scanning, inserting license files, ...).
Shields should continue to work even without AvastUI, but it's not really the usual test case, so I cannot rule out the possibility that some functionality will also be limited.
-
If there's a real problem I would rename this component and see what happens.
But I don't see any reason to switch off any part of a program I want to use ...
-
AvastUI performs all the "visible" (UI) operations - which the service running on a different session can't do.
So if you disable it, you won't see anything - if Avast blocks or deletes a file, you won't know (so it may get quite confusing if your files are disappearing and you don't know why). Some functionality won't be available (context menu scanning, inserting license files, ...).
Shields should continue to work even without AvastUI, but it's not really the usual test case, so I cannot rule out the possibility that some functionality will also be limited.
Thank you Igor
-
AvastUI performs all the "visible" (UI) operations - which the service running on a different session can't do.
So if you disable it, you won't see anything - if Avast blocks or deletes a file, you won't know (so it may get quite confusing if your files are disappearing and you don't know why). Some functionality won't be available (context menu scanning, inserting license files, ...).
Shields should continue to work even without AvastUI, but it's not really the usual test case, so I cannot rule out the possibility that some functionality will also be limited.
I know this is quite an old topic but I have arrived here after seeing all the changes Avast Clean Up says my system requires to get it working properly. After an Antivirus full scan Avast offers me to run a Clean Up (the Idea of Avast is to convince me of the need to buy the clean-up tool) the Clean Up results shows a series of actions that must be taken on processes that affect my computers start-up and general performance (the truth is I have been suffering growing problems with performance with many programs showing a "doesn't respond" warning before finally opening if I wait long enough (i.e. Word). Some of those processes that Avast Clean Up mentions require "clean-up" is "AvLaunch component" which includes "AvastUI" in the "Tasks Manager > Start Up" in Windows 10.
So I would like to know what does Avast Clean Up do with AvastUI and/or AvLaunch component so they don't interfere with the performance at start up in my computer, and if this implies disabling them at start up. Of course Logic takes us to ask why does Avast include processes at start up and then produces another tool that suggests it should be cleaned up. Shouldn't Avast clean up that process before delivering Avast to its clients so we don't have performance problems?
I ask you Igor directly because you appear to be Avast staff and in all this thread you are the only one who has treated rm15's question using reason, but due to the assessments of Clean Up it's worring. If you can't answer this question please get someone else in the staff to answer it. I doubt anyone who is not staff can answer this question with accuracy. Thanks.
-
@ Richard567,
Please start your own topic in the following Section: https://forum.avast.com/index.php?board=63.0