- Aug 30, 2012
- 6,598
Avast Blamed for Breaking Down April 2018 Update
- Thread starter BoraMurdar
- Start date
- Jun 24, 2016
- 2,400
I knew it! LOL
I created a huge debate yesterday on an IT Facebook Group explaining with detail why Windows updates are so important and must be installed, while all pseudo-technicians claimed that they were useless and broke machines everytime, using April Update as an example of how many PC's they had to repair due to it. I kept saying that if nobody touched the system in the update process or there was no antivirus blocking it, no problems should pop up. And heeeeeere comes Avast once again taking the lead!
If you do not use Windows Defender the best option in these scenarios is to disable your main antivirus before doing an important security update.
I created a huge debate yesterday on an IT Facebook Group explaining with detail why Windows updates are so important and must be installed, while all pseudo-technicians claimed that they were useless and broke machines everytime, using April Update as an example of how many PC's they had to repair due to it. I kept saying that if nobody touched the system in the update process or there was no antivirus blocking it, no problems should pop up. And heeeeeere comes Avast once again taking the lead!
If you do not use Windows Defender the best option in these scenarios is to disable your main antivirus before doing an important security update.
- Jul 3, 2015
- 8,153
I updated a machine with Avast to April Update, and I did not have any problems at all. Aside from the fact that Avast itself is annoying.
Good thing I use Kaspersky, although disabling (or even uninstalling) the Anti-Virus is always recommended with this Updates.
- Jul 3, 2015
- 8,153
6 months ago, Kaspersky was blocking Windows updates on some machines. This went on for a few months. They fixed it, but all 3rd party AVs have the potential to conflict with Windows functioning. It's a matter of luck.
It's funny how Avast gets blamed for Microsoft Spring Creator Update 1803 breaking the system. Everything was working fine until 1803 hit the system.
Blaming the 3rd-party publisher shows lack of understanding. "But it is Avasts! responsibility to fix everything before Microsoft released 1803 !" No, it doesn't work that way. With a little bit of knowledge, one can hardly say it is Avasts! fault.
Microsoft's new release schedule makes it such that no publisher can keep up with all the unilateral changes. In that kind of environment "stuff" is going to happen.
And no... the solution is not to test using the Windows Insider Program. Even if you do, Microsoft, more often than not, does not provide sufficient time for the publisher to provide fixes before Microsoft makes a "stable" release. And besides, Microsoft very often makes a fix to their update within the first 30 days. So, from the publisher's perspective, it is better to wait until 30 or more days after a Windows Update\Upgrade to go on the fishing expedition to figure out what Microsoft broke in their software.
Blaming the 3rd-party publisher shows lack of understanding. "But it is Avasts! responsibility to fix everything before Microsoft released 1803 !" No, it doesn't work that way. With a little bit of knowledge, one can hardly say it is Avasts! fault.
Microsoft's new release schedule makes it such that no publisher can keep up with all the unilateral changes. In that kind of environment "stuff" is going to happen.
And no... the solution is not to test using the Windows Insider Program. Even if you do, Microsoft, more often than not, does not provide sufficient time for the publisher to provide fixes before Microsoft makes a "stable" release. And besides, Microsoft very often makes a fix to their update within the first 30 days. So, from the publisher's perspective, it is better to wait until 30 or more days after a Windows Update\Upgrade to go on the fishing expedition to figure out what Microsoft broke in their software.
Last edited by a moderator:
But the article states:
"However, this problem has only occurred on systems that attempted the 1803 upgrade in the last two days. This infers that a very recent update to Avast is interfering with the upgrade process"
1803 was already out for quite a while.
- Jul 3, 2015
- 8,153
- Nov 26, 2016
- 699
Updated April Update on 3 systems even before it was officially released and had no problems. Who wants to bet systems were running some ancient versions of avast! that were less than optimal for April update? avast! keeps on pressuring users to update program versions and users keep on stubbornly refusing because "reasons". And then geniuses jump on avast! because that's a common point, but how many actually evaluated what contributed to the "error"?
I completely agree with you. This is special dangerous when MS make important/low level changes in the system that could break sensitive software such as AVs, that uses low level APIs or kernel mode drivers.
On the other hand, It seems that Avast is not to blame for this problem. The article in reddit was updated and several users with other AVs (AVG and Norton) also have the same problems.
These posts are difficult because they are not normal human conversations.
1803 has not been out long enough for publishers to figure out all the problems. It isn't like there is an army of programmers who sit there and wait for the next Windows Update and then test that update to death once it is released. It doesn't work that way.
Of course, 3rd-party updates that have bugs can smash Windows. I am not denying that fact.
The system was working fine until the people attempted to upgrade to 1803... that's plain enough.
Everyone is assuming that Microsoft changed nothing in 1803. While I could find out, it would take hours because Microsoft doesn't make looking anything up easy. It just isn't worth my time to figure it out.
All I am pointing out is that what people really want is someone to point the finger at - and invariably it always ends up being the 3rd-party publisher - long before all the information is made available. And I mean officially and not some Reddit.
Last edited by a moderator:
- Jan 8, 2011
- 22,361
I'm sure it has been mentioned many times before, but in general it's advisable to disable or uninstall your Antivirus prior to any major OS Upgrades.
- May 16, 2018
- 18
Agreed. Especially if you are doing major feature updates like this.
Although I think Microsoft is to blame too. They change a lot in these feature updates in the low level parts of the OS, kernel drivers and such. You think they would test the updates with one of the most used antivirus programs on the planet.
Although this may be too much to expect from an incompetent company like Microsoft who reportedly fired their testers and rely on Windows Insiders for QA which are probably not gonna run a lot of third party programs.
Last edited:
- Apr 13, 2013
- 3,147
- Jan 8, 2011
- 22,361
Well it kind of was their fault, because non-Avast users didn't have this issue. Js.
May 24th - Windows 10 failed update to 1803, maybe an Avast problem?
Basically Avast was incompatible with the latest Windows 10 update. They have public beta builds quite regularly.. right?
First basic rule: NEVER upgrade an OS when an AV is present (especially if the said AV has a BB/HIPS, etc...).
Those doing it are just noobs and should take a beginner computer course before blaming the AV.
Those doing it are just noobs and should take a beginner computer course before blaming the AV.
- Jul 28, 2014
- 1,990
instead of uninstalling would deactivating it permanently and updating the OS be any help? Many AVs have options to deactivate and start protection again until manually activating it again, even through restarts
it may help if the deactivation also stop the service.
But to be honest i prefer full uninstall, at least i'm sure nothing will interfere.
Similar threads
