Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: REDACTED on May 07, 2017, 09:49:53 AM
-
Avast should pay me
Then, fire your support staff, your engineer, and the team who's responsible for this disaster!
I deal with lots of support stuff like these as well, and you know, the stupid HAVE YOU RESTARTED YOUR PC? DID YOU PERFORM A REPAIR? never works, it never does, so guys, mods, stop with this BS and do some real world test and find the fix before spewing your nonsense by-the-book replies here, ok?
What a disaster they have created and the recent reports along with my own case links back to the same issue. I first discovered it when IDM was horribly slow, and the drama that went with it yada yada similar to what others have been reporting.
Idk if i'm the first ever to discover it, by chance and trial/error/randomly clicking things, i found a fix to the current issues reported for slowdown.
Originaly posted:
https://forum.avast.com/index.php?topic=201729.msg1391933#msg1391933
Here's what you need to do. Settings > Troubleshooting > Enable both of these highlighted > Restart PC
(https://d2ppvlu71ri8gs.cloudfront.net/items/1U2u2x2a3U2C3q3D2v33/%5B4d3d290e75324c21cb178152f9c7f230%5D_Image%25202017-05-07%2520at%25209.15.28%2520AM.png?v=4398a8f0)
Edit:
As pointed out, this "fix" was caused by the effect of a reboot, and during that time (roughly 5 minutes), your programs will launch as normal. The idea behind is avast hasn't kicked in fully and once the system is all loaded (despite avast being loaded first) the programs will slowdown.
-
the stupid HAVE YOU RESTARTED YOUR PC? DID YOU PERFORM A REPAIR? never works
You can't be more wrong.
It does work many times.
If enabling them is solving things for you it doesn't mean it will do so for others.
-
the stupid HAVE YOU RESTARTED YOUR PC? DID YOU PERFORM A REPAIR? never works
You can't be more wrong.
It does work many times.
If enabling them is solving things for you it doesn't mean it will do so for others.
Oh, you wanna bet? :)
I've seen you around, even though i just recently joined the forum and all you did was just telling people to repair the program. HAH. Sorry to break your bubble, but it has never worked. Sure, when something is stuck, the easiest way out is to restart the PC, the router, etc. But when the issue is caused by an update that is pushed, that is entirely out of a user's control, so no, a restart, repair, re-install to the latest version, and reinstall the entire OS, will not work. I'm gonna throw in 1 million dollars if it ever does. And so far, none of the people who have done it, including me, ever got to fix this recent issue caused by the update. NONE.
Sidetrack a little, it's like every single time i called up my ISP support, and the first thing they ask, have you ... and the first thing i told them, "stop what you're trying to say, i know, and i've already done it, so now, listen to my report, and pass it to your technician". Otherwise, there's no end to their robot troubleshooting which doesn't fix the issue caused by their problem, not my problem.
-
I've seen your original post and tried it. Now, that I wanted to report, I saw your new, separate thread on this, so I reply here.
Thanks!!! for your info. It worked for me.
I was always wondering what that "new" sub-option ("nested virtualisation") of the hardware-assisted virtualisation was doing. I had the main hardware-assisted virtualisation option enabled for as long as it existed. I'm not sure if the sub-feature came with the first v17 version, but it was definitely there with the previous one (v17.3.2291) (and it was always - I repeat always - disabled ("by default"*) since it appeared in the software on my system). But because of the "reboot required" note I was always to lazy to try it. And it would have been no difference to be seen anyway - in previous versions.
The sub-feature (which is not mentioned or explained in the contextual help), if enabled, does fix the (additional) problems I had with v17.4. The VirtualBox GUI not starting problem was fixed right away, i.e. no reboot needed. The "reduced framerate problem" was only gone after reboot - most probably because the service (or whatever) that causes / caused that problem was already running (I'd guess a service that is started at windows boot).
But, as the sub-feature was there before and never caused any problems if not enabled, I wonder: were previous versions not implementing it correctly or is this new need for enabling it a bug? But if it's the first, why is there no apparent mention of it in the changelog (which are not too informative/explanatory anyway).
*I've never really did a clean install. I did uninstall and re-install but the first thing I do after re-install is importing my settings because I really really don't like redo all the settings (I have done over the years) manually - and I couldn't remember all the exeptions and settings anyway. So, that might be the reason why the "nested virtualisation" never was enabled on my system.
-
You already have lost that bet.
The option you told is enabled by default, so why would people enable it?
You seem to be just another wanabee support guy.
People like you are giving real techs a bad name.
I've seen you around, even though i just recently joined the forum and all you did was just telling people to repair the program.
Time for you to look better.
I (and others) have helped 10.000's (likely even more) of people and not just with telling them to perform a "repair".
-
You already have lost that bet.
The option you told is enabled by default, so why would people enable it?
You seem to be just another wanabee support guy.
People like you are giving real techs a bad name.
I've seen you around, even though i just recently joined the forum and all you did was just telling people to repair the program.
Time for you to look better.
I (and others) have helped 10.000's (likely even more) of people and not just with telling them to perform a "repair".
Good for you. But you missed the point of the bet. It was regarding this particular issue, and no, the option was not enabled by default, read, and re-read again what he just said, "enabling it was what fixed it for me". Not only have you lost the bet, you had the cheeky idea of reversing the bet on me but alas, you failed.
Did you take the time and effort off, actually tried to look into what was reported and preproduce it? Nope. You just did basic troubleshooting, and it was all based on knowledge on common things reported. This is a unique case, only caused by the update, so your basic method will not work. Am i a genius? No, but i'm a user desperate for a solution, contrary to you, who never had any of these apps installed, and never faced such specific issues.
If you had virtualbox, IDM, overwatch, and opera installed, you will face at least the same issue, but since you either didnt have any of these, then you're not qualified to give advice.
It's like going to the doctor and every single patient has his own unique issue, and the doctor first thing ask, did you drink enough water? Out of 1 million, 1 thousand will have this issue, how can 1 million of them get prescribed the same thing? That makes the doctor sound really ridiculous.
Gonna take my leave for now. Enjoy telling your new batch of 10.000 to repair their installation. I'm sure youre a big help ;)
-
It was regarding this particular issue
And ?
As I said, what is working for one user might not work for another.
Did you take the time and effort off, actually tried to look into what was reported and preproduce it? Nope
Again you are wrong.
If you had virtualbox, IDM, overwatch, and opera installed, you will face at least the same issue, but since you either didnt have any of these, then you're not qualified to give advice.
And you are wrong again.
-
It was regarding this particular issue
And ?
As I said, what is working for one user might not work for another.
Did you take the time and effort off, actually tried to look into what was reported and preproduce it? Nope
Again you are wrong.
If you had virtualbox, IDM, overwatch, and opera installed, you will face at least the same issue, but since you either didnt have any of these, then you're not qualified to give advice.
And you are wrong again.
Good for you. I'm the Mr wrong guy here, who have managed to help a few, others have reported in other threads it has worked for them, while you have helped zero regarding this particular issue.
I'm sorry for being the MR wrong guy here. But then again, why are we arguing anyway. You should at least be more negative towards avast here, (instead of pretending to help with your general support), who have done nothing for days to fix this while it took me 1 day to find a temporary fix that could have helped half of it's affected userbase.
Until now, no public announcement has been made, look at the number of reports, and the number of viewcount on those threads ! No matter how much of a fanboy you are, you can't be totally ignorant.
-
@avast-user-01,
This was enabled by default on my pc running win 10 with Creators Upgrade.
-
@avast-user-01,
This was enabled by default on my pc running win 10 with Creators Upgrade.
It seems depending on system avast will either enable it or disable it by default. And i seen other people reported it was enabled and it didn't work (because it's enabled and they didn't touch it). Since my PC worked (problem was temp solved) after i enable it, i did a test to disable the nested option, rebooted, and guess what? No slowdown !
How strange. So for anyone who has already enabled it, my theory is something needs to be done on the troubleshoot option that requires a reboot, so disable the nested option if it's enabled and reboot.
Edit:
Looks like i spoke too soon. After a while, the issue came back. So for those with the option ticked, you're probably out of luck. You can disable and then re-enable it again, but i doubt it will help.
-
I feel like you should apologize to Eddy now.
-
I feel like you should apologize to Eddy now.
Who are you? And why should i? And who is he? He got everything wrong and still made me the Mr wrong guy, and idk who you are just jumped in and asked me to aplogize to him? Hmmmm, welcome to the internet eh?
-
I say you should because your fix didn't exactly last very long mind you.
Eddy is one of the users on the channel, and while he isn't the most informative at times, he was correct in that your method wouldn't work with everyone.
Also of note, your attitude towards the community is rather hostile, considering many of us are trying to find solutions to the issues, while you're just being condescending and attempting to make yourself correct overall.
Granted, it's a bit annoying that Avast has issues each update, but what's slightly worse is those users who only join/create accounts to openly harass users or the program itself, rather than leave constructive feedback :)
-
A temporary fix would also be not playing Overwatch.
-
I say you should because your fix didn't exactly last very long mind you.
Eddy is one of the users on the channel, and while he isn't the most informative at times, he was correct in that your method wouldn't work with everyone.
Also of note, your attitude towards the community is rather hostile, considering many of us are trying to find solutions to the issues, while you're just being condescending and attempting to make yourself correct overall.
Granted, it's a bit annoying that Avast has issues each update, but what's slightly worse is those users who only join/create accounts to openly harass users or the program itself, rather than leave constructive feedback :)
Not only is there no one from Avast jumping in to try and find a fix, we have a bunch of fanbois here who are are ignorant about the entire situation, and let avast do whatever they want and still we stuck onto them. Sorry to break it to you Mr i dont know who you are, but plenty of users are going to uninstall this and look elsewhere, me included.
Just look at what others are replying. Oh and btw, my attitude towards the community, what did i do? Nothing. Did i harass them? No, i'm just stating the facts, only old members got a little salty. Those who registered just this week are looking for a quick solution, and i managed to help some of them, did you?
-
A temporary fix would also be not playing Overwatch.
BEST POST EVER. CONGRATULATIONS ON WINNING THE INTERNET. The majority of new users signing up and complaining is overwatch users, and you're now openly and blatanty telling people to quit that while keeping avast. It's like telling someone, stop eating. I dont play overwatch, but man, you're way over the top there.
Oh your car stopped running. Calls up the boss, and tell him, hey i'm gonna stop working till the car is fixed. ;)
-
Not entirely help them mind you. Nor help quite a decent bit of people.
All i did was find the responsible shield causing the issues, informed people of the issue, as well as suggested on various other reddits to either wait for a patch or replace Avast in the meanwhile.
But i haven't done much myself :)
Also eddy is being sarcastic, calm down son.
-
Kinda strange calling people fan boys if you have no clue about what I and others have told avast in places you don't have access to.
For your information, I haven't been using avast for way over a year.
And again you are wrong.
Check the posts from let's say the last 1000 people who joined and read them.
Only a few of them mention a problem with Overwatch.
That is definitely not the majority.
And again you are wrong.
I never told anyone to quit playing it.
-
Arguing isn't going to solve the problem nor will it make new friends.
The settings are pre-checked by default if your operating system and hardware permits.
As a non gamer, I can't offer any conclusions as to the merits of checking or unchecking these functions.
-
As a side note, the reason a restart makes it appear Avast is working is because Avast hasn't fully started up yet. Once it has, the issues return (due to file system shields).
-
So far I haven't had any issues with this new version I updated the day it was released.
Edit: typo
-
Well, the title was (unwittlingly) correctly chosen: temporary fix.
My v17.4 problems are back, too. But there's also a new vps, so that might be the explanation for the change. Just as it worked with vps 20170505-2 and didn't again with vps 20170505-4.
For now, I'll go back to v12.1 and wait until avast comes out with a new version and states in the changelog that the problem is fixed - because by now I don't think they even accept that there is a problem. Otherwise it wouldn't be there with on vps, gone with the next and return with the one after that.
-
This is also the weekend and as afar as I know,
weekend means skeleton crew.
-
This "fix" is not a fix. The slowdown stops because you're rebooting your system. But it will reappear at some moment, regardless whether those options are enabled or not. Also they were enabled by default on my PC, and I did try disabling them and re-enabling them, and no change occurred. Also just by the name of the options, I highly doubt they're related at all with Discord or some games. I'm pretty sure neither Discord or 99% of games use any virtualisation technology at all.
-
Has anyone tried turning off the Gaming mode:
(http://screencast-o-matic.com/screenshots/u/Lh/1494195381545-40457.png)
-
This "fix" is not a fix. The slowdown stops because you're rebooting your system. But it will reappear at some moment, regardless whether those options are enabled or not. Also they were enabled by default on my PC, and I did try disabling them and re-enabling them, and no change occurred. Also just by the name of the options, I highly doubt they're related at all with Discord or some games. I'm pretty sure neither Discord or 99% of games use any virtualisation technology at all.
You have a point. I'm going to test it again with the settings on and leave it for a while just and then re-test the speed of programs launching. The default setting is to launch avast before other programs get to launch, so i doubt the other settings or a reboot can make avast launch later.
Edit: You are right ! I'm getting the slowdown just 5 minutes in. Strange indeed. What does this even mean IDEK anymore. I tested IDM and virtualbox before the effect kicks in the earlier time, and the program launches just as normal. Now i wait for 5 minutes and the slowdown came back even with the settings turned on.
Has anyone tried turning off the Gaming mode:
See, i really didn't wanna get so hostile as some would put me into that category, but seeing the amount of post you had, one might think you have actually read the issue and tried to use the real source of it to debug and come out with a temporary fix, but you're clearly not even reading a single line of what's been reported.
This isn't overwatch thread, and this isn't about the game only getting slowdown, so what in the world has turning off this helps the reported IDM, discord, virtualbox, etc ?
I guess anything goes eh? For your sake i'll try it out and see if i'm the Mr Wrong guy here yet again.
-
@ avast-user-01
The only people that have responded in your topic have been other avast users like yourself and not Avast Team members/employees. So they can't debug the source of it nor come up with a fix.
-
Figured as much. I know they're not from the avast team, i don't exactly see a point in trying to help with a program that avast clearly ignored, me included. I only helped because i
am was a fan and wanted the community to benefit from it, that's about it. But avast' silence and non open policy got me.
For the record, this will be my last post, i've since switched over to bitdefender after being suggsted by " avast alternative" and i couldn't be any happier. Not only is it silent, it's install and options is so minimal i'm cracking my head wondering if it does or even works, and it does.
They might have their own issues, so be it. But i've other qualms with avast that makes me leave so if the other guys have problems, i'll also just leave them.
Never stay loyal to any service guys. And never be a fanboy. There are always alternatives.
Cya
-
Your system, your choice. Enjoy :)
-
For now the vps update from today (170509-4) seems to have fixed the problem. Let's hope it's not just temporary as before.