windows 10+Avast = unpleasant user experience

system · 2016-01-22T17:16:01.000Z

lukor post:22:

Hello Guys,
we are monitoring this issue (“Cortana or start menu not working”) and are talking with Microsoft about this. Currently we all believe it is a problem (or several issues) in Windows and Microsoft is trying to fix this.

One of the attempts to fix this can be in the following update: KB3105210
https://support.microsoft.com/en-us/kb/3105210

The list of changes mentions start menu and cortana reliability fixes.

Another attempt to fix this can be expected from the upcoming TH2 release of Windows 10. Please try the latest build from the Windows 10 Insider Program. If anyone is experiencing the same issue with the latest Insider build, please let us know (e.g. post here or write to me directly). We would like to escalate the issue again, if it is not fixed in TH2 Windows 10 Release.

Thanks a lot.

What we’ve also seen is that a restart or a few restarts resolves the issue with startmenu not opening. (restarting is also part of the Avast uninstallation, but you can restart without uninstalling as well).

Lukas.

So I have the latest version of Windows 10 (1115), and I have the updated version of Avast, and I am still having problems with my start menu and cortana not working. I just paid for Avast Pro, and I’m not impressed at all, that this isn’t fixed by now (both Microsoft and Avast). I’m running a fix to reinstall my Windows apps, and I’m hoping that works, but I’m still seeing a ton of people posting about this. I haven’t tried booting into Safe mode yet (waiting for this other thing to finish first). Just wanted to let you know, that this isn’t fixed with the latest upgrades.

Thank you!

DavidR · 2016-01-22T19:02:02.000Z

And there is no doubt a ton of people posting about this that don’t have avast installed as has been mentioned in other topics.

I would certainly have tried the boot into safe mode first, given that would be less hassle than reinstall of windows apps.

schmidthouse · 2016-01-22T19:08:05.000Z

I also read a post I believe by Bob that said booting into Safemode “with Networking”. Not sure what difference if any that would make. :-\

system · 2016-01-22T19:53:26.000Z

From my experience, this “safe mode trick” helps for about 1 day, it depends on how often you reboot/shutdown/hibernate your pc.

Patrick2 · 2016-01-22T20:56:56.000Z

If it Matters I upgraded to Windows 10 from 8.1 on my Old PC, and my Newer one, and didn’t experience any problems with it, though I let Windows Defender run during upgrade install, then did a clean install following the upgrade, did all the WIndows 10 updates, then configured Avast Free again, no issues with Start menu, Cortana at all, been running this System almost a month now, Sleep and Restarted off and on.

refreshed my old system and gave it to Mom, again no issues experienced with Windows 10 or Avast once I got Avast installed

My Theory is could be a conflict with someones start up item, a setting, or something

bob3160 · 2016-01-22T21:08:25.000Z

schmidthouse post:32:

I also read a post I believe by Bob that said booting into Safemode “with Networking”. Not sure what difference if any that would make. :-\

Those instruction come directly from the Windows 10 support site.
On the computers that I’ve had to use this on, have never had the problem again.
It is certainly more than a one day fix.

system · 2016-01-22T22:25:10.000Z

Certainly NOT for all…

bob3160 · 2016-01-22T22:30:51.000Z

malone.m post:36:

Certainly NOT for all…

I suggest you have someone thoroughly check your computer for possible conflicts.

system · 2016-01-22T22:44:20.000Z

Dear Bob, I am perfectionistic and experienced enough to keep and eye myself on possible conflicts and prevent them

system · 2016-01-22T22:54:05.000Z

malone.m post:33:

From my experience, this “safe mode trick” helps for about 1 day, it depends on how often you reboot/shutdown/hibernate your pc.

For what it is worth…HIBERNATE…is the very first thing I disable within a new PC.
http://www.tenforums.com/tutorials/2859-hibernate-enable-disable-windows-10-a.html
Hibernate is notorious for mucking things up and with new Windows fast boot you cannot really tell if a reboot is a true reboot from O/S or A/V perspective.
I’ve found SLEEP is just fine for power savings and so much cleaner on resume…and power downs, boots, etc. are so much better off without hibernate.
You can do a google and see the issue of this function overs the years and it is a “layer” that can cause issues that frankly just isn’t worth the marginal benefit.

system · 2016-01-23T00:48:26.000Z

thekochs post:39:

malone.m post:33:

From my experience, this “safe mode trick” helps for about 1 day, it depends on how often you reboot/shutdown/hibernate your pc.

For what it is worth…HIBERNATE…is the very first thing I disable within a new PC.
http://www.tenforums.com/tutorials/2859-hibernate-enable-disable-windows-10-a.html
Hibernate is notorious for mucking things up and with new Windows fast boot you cannot really tell if a reboot is a true reboot from O/S or A/V perspective.
I’ve found SLEEP is just fine for power savings and so much cleaner on resume…and power downs, boots, etc. are so much better off without hibernate.
You can do a google and see the issue of this function overs the years and it is a “layer” that can cause issues that frankly just isn’t worth the marginal benefit.

Sorry, actually I meant regular “sleep mode” in my post above. I wasn´t thinking too much about the true meaning of the word, english is not my native language

system · 2016-01-26T16:17:04.000Z

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.

bob3160 · 2016-01-26T16:21:15.000Z

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.

system · 2016-01-26T16:42:16.000Z

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.

bob3160 · 2016-01-26T17:44:09.000Z

Bruce68 post: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.

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.

system · 2016-01-26T17:51:21.000Z

Bruce68 You are absolutely right.

bob3160 · 2016-01-26T18:00:22.000Z

malone.m post:45:

Bruce68 You are absolutely right.

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

system · 2016-01-26T18:51:42.000Z

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?

system · 2016-01-26T20:21:59.000Z

bob3160 post:46:

malone.m post:45:

Bruce68 You are absolutely right.

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

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 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.

bob3160 · 2016-01-27T10:57:46.000Z

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.

Announcements