41

The people saying Avast isn’t causing this is in denial. I work with computer repair and I’ve been noticing it happen ever since Windows 10 came out and sometimes the issue appears immediately after installing Avast or after rebooting it once Avast is installed. Uninstalling Avast fixes of the problem every single time.

Of course if you’ve been dealing with Windows 10 for long enough you know that there are a number of things that break the start menu and cause the desktop shell to stop responding (outdated shell extensions for example), but that doesn’t mean Avast isn’t causing it too.

Oh btw this is after performing a clean install of Windows 10 on many different systems.

Just today I experienced something similar after installing avast on a Windows XP machine. Right after installation and before the “Welcome to avast” audio was played the desktop shell stopped responding, I was still able to use the mouse and interact with open Windows’ but nothing else worked. I’ve seen this happen on Windows 7 as well, more than once, and although it only happened after finishing the installation and didn’t happen again after rebooting the computer (avast worked fine after reboot) it’s very similar to what happens on Windows 10 the only difference being that on Windows 10 it can happen at any time and not just when the setup completes and before the Avast UI is able to start.

42

What does an XP system have to do with reported Windows 10 problems ???
No one is in denial since this problem happens on systems that have never had Avast installed. It also happens on
systems that have had other Av’s installed.
But, you’re the expert. So if it makes you happy, stick to your theory.

43

There are a number of things that can break the Windows 10 start menu and Avast IS one of them. I mentioned the Windows XP issue because it’s very similar. The desktop shell stops responding and there’s nothing you can do other than reboot.

And I’m still installing Avast on Windows 10 systems because it only affects a small number of devices which might indicate a conflict with a device driver or something but it does happen.

The Windows 10 start menu/cortana/shell should be more stable and resilient but it doesn’t mean avast isn’t causing a problem.

44

It is when it happens on systems that have never had Avast installed on them.
It is when it happens on systems that run a different third party AV.

45

Bruce68 You are absolutely right.

46

Excellent answer from someone who isn’t even using Avast. :slight_smile:

47

So if a software causes the system to bluescreen for ~5% of the user base, because it’s not happening to everyone and because other things can cause the system to bluescreen that software shouldn’t be blamed for it?

48

:smiley: :smiley: :smiley: Are you kidding me? Yes, I´m not using it right now, because I´ve been forced to stop using it for known reasons. Another your brilliant attempt to stultify me, bravo :smiley: Maybe you should know that not so long ago I´ve recommended Avast to people who searched good free antivirus and myself used it cca 3 years until now.

49

Very simple, if this was truly an Avast problem, then it should not happen to people who don’t use Avast.
Put the blame where it belongs. It’s a known Windows 10 problem.