@
allenergy,
I have been watching this topic since my last post. Your posts were clearly transferring some urgency, together with... well, not being calm enough to solve the problem quickly enough.
Once you insisted that the process (not "service", as you stated) was avast.setup, and that you were not interested in actually solving whatever the problem was (but more as "give me my CPU back and go away"
), then I thought that a reboot was probably more "effective" than even opening this topic (at least, for the time being). But by the time I thought about it,
Asyn was already expecting some answers from you. Adding more posts (from me) in the middle wouldn't had help you with your work.
Please don't get me wrong. I understand that you expect "everything" (including Avast) to assist you in your work and not to bother you. But let me clarify some things, at least the way I see them.
You mentioned in your posts about having to disable the shields. Yes, I suggested that, just to see if that would liberate your CPU. Although it would be a security risk when a potential malware is at your door, it was the most simple step you could carry out so to try to recover CPU power for your work. I wasn't giving you a major task, with hours of double checking.
I am NOT taking this personal. I am just trying to put things into some proportion. Of course you want things to work "as they should", but once they don't...
I also want to mention that any user posting here in this post was trying to help, as fast and effective as we could. You said you can't answer immediately. You said it several times. I think that you were feeling the pressure of your job and tasks, not from the forum users. If you were not answering fast enough, that only works bad for yourself, and also talks "good" about this forum's users, specially about those not directly related to Avast Software (which are most of us).
I want to make as clear as possible that all these comments (ranting?) are only meant to help you, and it is not about anything negative in any way.
Finally, the technical part.
I am set for auto updates for defs as I mentioned above. I just changed the frequency to once every 1440 minutes or once a day. From 2 x per day.
Avast *checks* for updates the first time you get connected to the Internet after a boot, and once every 4 hours (240 minutes) after that. Avast Software usually makes available database updates about twice a day. For each time your Avast program *checks* for updates AND *finds* an update available, you get to apply the update (Avast does it). So changing from 240 to 1440 minutes means changing the *checking* frequency.
If that helps you to work better while it keeps you safe, fine.
According to your own descriptions, I would NOT recommend to change this setting to "manual".
IF the update today (or whenever the problem started) was having some problem, it could be for many possible reasons. One reason might be that your bandwidth was being intensively used, and Avast was trying to download updates. Usually, Avast updates are fast and around 10s or 100s of KB, but not always. A server might have a temporal problem. Or at the same moment you were intensively using your system, "exactly" when Avast was *trying* to update (with some problem) and you decided to check your task manager.
To be clear, I don't have the knowledge to say if the avast.setup process/service that you saw was indeed related to some kind of update for Avast. I am not saying that an update was the problem.
It might had been possible that had you leave it to complete the update, it had had free the CPU time eventually in a couple of minutes. This is a completely blind speculation now.
The fact is that you had a problem, and something might go wrong sometime in computers. If the problem was indeed an update for Avast, then from the millions of users receiving updates several times a day every day, "sometime" something could go wrong. This is never an excuse, but it is a practical / real possibility.
It might be Murphy's law, and a simple reboot might "
solve" the problem, as it happens with many different tools. And if not, always remember to keep it calm and you will find someone to try to help you in this forum.
(My apologies for the long post.)
