Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: petr.chytil on March 20, 2017, 02:22:13 PM
-
What happened?
BSOD on Windows 7 32bit with 170320-0 virus definition update.
How to fix
Fix is included in the 170320-1 virus definition update. To update virus definitions:
Right click on the Avast tray icon -> Update -> Engine and virus definitions
or:
Open Avast -> Settings -> Update -> under Virus Definitions and Current version click on the Update button
or:
Download the offline virus definition updater (vpsupd.exe) from https://www.avast.com/download-update and execute it to apply the virus definition update
When was it fixed?
Timeline (all hours are in CET (Central European Time, GMT +1):
Mar 20 8AM - Virus definition version 170320-0 released
Mar 20 11AM - First mentions on forum about the BSOD
Mar 20 2pm - Release of 170320-1 with the fix started
Mar 20 5:30pm - Virus definition 170320-1 version released
Thank you!
We're very thankful to our Avast users especially those who posted here on the forum! You helped us discover the root cause much faster which drastically sped up our delivery of the fix.
Have a good day,
Petr
-
Petr,
How on earth did this pass without being noticed by QA?
Sadly, these issues are becoming a theme with Avast. Far too many major issues.
-
Petr,
How on earth did this pass without being noticed by QA?
Sadly, these issues are becoming a theme with Avast. Far too many major issues.
+1 :(
-
Petr,
How on earth did this pass without being noticed by QA?
Sadly, these issues are becoming a theme with Avast. Far too many major issues.
+1 :( :( :(
-
Thank you, the full disclosure is much appreciated.
-
Petr,
How on earth did this pass without being noticed by QA?
Sadly, these issues are becoming a theme with Avast. Far too many major issues.
If it was occur on weekend! then???
-
If it was occur on weekend! then???
@Be Secure :)
Manny issues are put forward by us to Avast Developers directly on Slack, so it doesn't really matter if it is weekend or not.
Also this issue was reported on Slack by Asyn as soon as he noticed it.
Greetz, Red.
-
If it was occur on weekend! then???
@Be Secure :)
Manny issues are put forward by us to Avast Developers directly on Slack, so it doesn't really matter if it is weekend or not.
Also this issue was reported on Slack by Asyn as soon as he noticed it.
Greetz, Red.
8)
-
Mar 20 11AM - First mentions on forum about the BSOD
I raised a high priority ticket at 10:04am notifying of problems on all 32bit machines - yet to be responded to..
Pretty poor that I've had to go via twitter to your forum to get updates.
-
I raised a high priority ticket at 10:04am notifying of problems on all 32bit machines - yet to be responded to..
Pretty poor that I've had to go via twitter to your forum to get updates.
Support is most probably flooded with requests, atm.
-
For those of you with Avast Business - go into your web panel -> Network -> Settings -> Go to the Template -> Turn off components
This has resolved it across the board for me. I was on fire, the fire is put out for now. I plan to re-enable the shields after I confirm the update is applied.
My question for Avast support team / representatives... Will the update(s) still apply regardless of the components being turned off? That way I can re-enable the shields after the update applies, so I do not cause further havok for all my clients.
Please advise.
-
Not bad.. 100+ computers in our company rebooting every 10 minutes since this morning...
-
You think 8 hours is fast? You should've pulled the broken definition update hours ago.
-
You think 8 hours is fast? You should've pulled the broken definition update hours ago.
+1 - That and a mass email should be sent out to everyone so we don't have to go searching as to why numerous workstations are rebooting over and over. Thankfully Google + someone elses Microsoft.com support post reply lead to Avast! being the common denominator which lead to another thread, which lead to this thread.
-
"Mar 20 5pm" :(
-
Petr,
How on earth did this pass without being noticed by QA?
Sadly, these issues are becoming a theme with Avast. Far too many major issues.
And somone from avast will later post "we are taking measures so this will not happen again"
as they did say the previous time, and the insident before that, and the one before that, and .....
:P
-
"Mar 20 5pm" :(
Is this 5pm UK GMT?
-
5 pm CET (GMT +1)
-
Am I correct in saying that the RPC server is down right now?
I just tried an update from the system tray and said it was unavailable.
-
What time zone will this occur?
What happened?
BSOD on Windows 7 32bit with 170320-0 virus definition update.
How to fix
Fix is going to be included in the 170320-1 virus definition update. Temporary workaround is to disable File System Shield component.
When was it fixed?
Timeline (CEST):
Mar 20 8AM - Virus definition version 170320-0 released
Mar 20 11AM - First mentions on forum about the BSOD
Mar 20 2pm - Release of 170320-1 with the fix started
Mar 20 5pm - (expected) virus definition 170320-1 version released
Thank you!
We're very thankful to our Avast users especially those who posted here on the forum! You helped us discover the root cause much faster which drastically sped up our delivery of the fix.
Have a good day,
Petr
-
What time zone will this occur?
See Reply #19.
-
Am I correct in saying that the RPC server is down right now?
I just tried an update from the system tray and said it was unavailable.
I modified my post in another thread. Stream 170320-01 has been started, but the VPS hasn't yet been released. My apologies to all.
-
I modified my post in another thread. Stream 170320-01 has been started, but the VPS hasn't yet been released. My apologies to all.
NP Gopher. ;)
-
Am I correct in saying that the RPC server is down right now?
I just tried an update from the system tray and said it was unavailable.
I modified my post in another thread. Stream 170320-01 has been started, but the VPS hasn't yet been released. My apologies to all.
When I said unavailable I meant both program and definitions
-
Ok but my Avast cant find the new definition updates.
Here we dont have a fix yet.
-
Btw. we don't have this issue with Win 7 HP 32bit machines running Program Version 12.3.2280 and 170320-0
-
Am I correct in saying that the RPC server is down right now?
I just tried an update from the system tray and said it was unavailable.
I modified my post in another thread. Stream 170320-01 has been started, but the VPS hasn't yet been released. My apologies to all.
When I said unavailable I meant both program and definitions
Server work fine for me, no update yet, though.
-
I lost so much time today when I had real work to do :(
-
I lost so much time today when I had real work to do :(
You're not alone, still waiting for the update...
-
Virus definition update 170320-1 is available.
Manually update via :
Avast - Settings - Update - Virus Definitions - Update - ok - ok.
Greetz, Red.
-
Virus definition update 170320-1 is available.
Manually update via :
Avast- Settings - Update - Virus Definitions - Update - ok - ok.
Greetz, Red.
Confirmed, it's finally out. Thanks Red. :)
-
Virus definition update 170320-1 is available.
Manually update via :
Avast - Settings - Update - Virus Definitions - Update - ok - ok.
Greetz, Red.
It's finally out. Thanks Red.
-
Disabling the file system shield does not help as a temporary fix.
-
Disabling the file system shield does not help as a temporary fix.
A VPS( 170320-1) out with fix.
-
Confirming the above mentioned. Virus definition update version 170320-1 with the fix has been released.
-
pořád to schazuje systém už jsem přešel na jinej antivir ..
-
pořád to schazuje systém už jsem přešel na jinej antivir ..
Please post English here, else use the forum section for your language.
-> https://forum.avast.com/index.php?board=21.0
-
it still schazuje system and restart the PC I went to antivirus else ..aspon So in windows 7 32bit throws a new update, so within 10 minutes of blue screen :'(
-
I was fighting with this issue during all the morningggggggggggg!!!!
Is there a way to do it from the central console? in the cloud version?? because I have more than 50 workstations with this issue.
Thank you
-
Confirming the above mentioned. Virus definition update version 170320-1 with the fix has been released.
I see no option to delete avast from my laptop, can you please tell me why?
-
Uh oh :(. I solved it by going on else antivirus worst is the feeling when I wanted to buy this antivirus because I was in test mode .. :'(
-
Well I don't know if this had a further reach than just win7 32bit, I've had a right run around today believing that this might have been a micro update to 3419.69. But now I'm not so sure if it isn't somehow connected to this issue, although I didn't get a BSOD and it was on my XP system.
<Snip>
I haven't got a clue what was in the micro update to 3419.69, but today MY XP system had been locking up solid. Unfortunately I couldn't even enforce a manual crash (to gather data) as no keys were working even the power off key on my keyboard.
I tried lots of things, disabling the enable hardware-assisted virtualization, uninstalling the Behaviour Shield and uninstalled MBAM. Finally I restored my backup image from Saturday and also disabled and removed the elements just mentioned.
I have just got VPS 170320-1 but since I haven't had a BSOD or that my effected system is XP Pro, I don't hold out much hope this would resolve anything and my concern is of a micro update to build 3419.69 (which we as users have no control to stop).
-
Is there a way to take a report from the cloud console to see what definition is in each computer? we need it asap!!! We have 160 computers in different sites and we cannot check it one by one.
Thank you
-
Thanks for the fix! Luckily, we only had a few old machines running 32 bit windows 7.
-
Fix appears to be working for us! Just pushed it out globally after testing it on a couple isolated machines for the past hour or so.
No problems so far.
-
Thanks!
-
While I appreciate the particular difficulties this incident has caused for those responsible for networks of multiple computers and for those who rely on their computer(s) for business purposes, as a domestic user I am grateful that Avast have resolved the issue in relatively quick time.
I found my way to this thread via the Microsoft Community Forum which quickly alerted me to the fact an Avast update was responsible. I then waited some 7½ half hours until 17:30 GMT before starting up my Windows 7 desktop. I then found the virus definition updated immediately and the system has been running trouble free for over an hour since. Previously, after approximately 5 minutes, the system would crash. I did not exactly panic but was nevertheless rather concerned and tried several things to try to resolve the issue but none, of course, worked. Using my Puppy Linux / XP with internet disabled dual boot system, I eventually posted a query on the Microsoft Community Forum and received a reply very quickly. This proved very reassuring as I realised that my Windows 7 system had no lasting problem. The link to this thread also made me feel more confident as it was very clear it was not 'just me' suffering.
All seems well now so thanks to those who sorted it. Hopefully Avast will be more careful with future updates so that the frustrations and major inconveniences reflected in many of the posts here, are not repeated any time soon. My relief makes me feel quite forgiving but many posters here will rightly be peeved with Avast for a fair while.
-
Thanks for the fix
-
I'm afraid the fix didn't work for me--I tried both the update and a clean uninstall/re-install and Avast is still blocking Windows applications (error 0cx0000005, etc.), Gimp, Sketchup, etc.
-
Fix worked but real time file protection isn't working even though I disabled the webshield first.
I tested it with the avast test virus and it let me run it with no warning!
-
I'm afraid the fix didn't work for me--I tried both the update and a clean uninstall/re-install and Avast is still blocking Windows applications (error 0cx0000005, etc.), Gimp, Sketchup, etc.
The fix wasn't for that error.
-
I just replied with this on a similar post:
My system booted into something called a "Temporary Desktop" after a very recent update.
See: https://forum.avast.com/index.php?board=2.0
Fortunately, rebooting solved the problem but it was a very strange event, at least to me.
Windows 7 64 bit
-
Avast, you have been a total nightmare, now my system is unable to bootup correctly due to your lack of quality testing.
-
Fix worked but real time file protection isn't working even though I disabled the webshield first.
I tested it with the avast test virus and it let me run it with no warning!
Please stick to one thread. Posting in different part of the forum makes helping impossible.
-
Fix worked but real time file protection isn't working even though I disabled the webshield first.
I tested it with the avast test virus and it let me run it with no warning!
Please stick to one thread. Posting in different part of the forum makes helping impossible.
Please fix a broken program!
-
Fix worked but real time file protection isn't working even though I disabled the webshield first.
I tested it with the avast test virus and it let me run it with no warning!
Please stick to one thread. Posting in different part of the forum makes helping impossible.
Please fix a broken program!
I don't fix or break.... I'm a user of the program just like you.
-
Fix worked but real time file protection isn't working even though I disabled the webshield first.
I tested it with the avast test virus and it let me run it with no warning!
Please stick to one thread. Posting in different part of the forum makes helping impossible.
Please fix a broken program!
I don't fix or break.... I'm a user of the program just like you.
Stick to one thread.
-
@nightshade,
I answered you remark. :o
-
Big mistake a company that takes its name. Although it is a serious problem in the short term consequences remain because no one could have expected from the blue screen programs like Avast, at least not in 2017 years
:o
-
@nightshade,
I answered you remark. :o
Well answer this then!
Laptop was unable to start, its now doing a startup repair, attempting repairs, been doing this for over 25 mins, what now?
-
@nightshade,
I answered you remark. :o
Well answer this then!
Laptop was unable to start, its now doing a startup repair, attempting repairs, been doing this for over 25 mins, what now?
2 options:
1. Wait or,
2. Boot into Safe Mode (hit F8 Key repeatedly while booting) Use System Restore to restore to a point before the last VPS update.
-
I think it's partly system restore that has got the laptop into the mess it's in.
-
I think it's partly system restore that has got the laptop into the mess it's in.
Do you have an image that you can restore ???
-
I think it's partly system restore that has got the laptop into the mess it's in.
Do you have an image that you can restore ???
Unfortunately not.
-
I think it's partly system restore that has got the laptop into the mess it's in.
Do you have an image that you can restore ???
Unfortunately not.
If nothing else works and there isn't a backup, the only other option is to use the manufacturers
restore option. The bad thing is that it will restore your computer to it's purchase installation.
You'll need to re-install all of the programs, update the OS and the programs and your personal data will be lost
unless you have that backed up someplace in the cloud ?
A service tech could possible access the HD and retrieve your personal information before restoring it to the factory reset.
-
I think it's partly system restore that has got the laptop into the mess it's in.
Do you have an image that you can restore ???
Unfortunately not.
If nothing else works and there isn't a backup, the only other option is to use the manufacturers
restore option. The bad thing is that it will restore your computer to it's purchase installation.
You'll need to re-install all of the programs, update the OS and the programs and your personal data will be lost
unless you have that backed up someplace in the cloud ?
A service tech could possible access the HD and retrieve your personal information before restoring it to the factory reset.
And all because of Avast software, thanks Avast, I won't be using your crappy software ever again!
-
I think it's partly system restore that has got the laptop into the mess it's in.
Do you have an image that you can restore ???
Unfortunately not.
If nothing else works and there isn't a backup, the only other option is to use the manufacturers
restore option. The bad thing is that it will restore your computer to it's purchase installation.
You'll need to re-install all of the programs, update the OS and the programs and your personal data will be lost
unless you have that backed up someplace in the cloud ?
A service tech could possible access the HD and retrieve your personal information before restoring it to the factory reset.
And all because of Avast software, thanks Avast, I won't be using your crappy software ever again!
Hope this will get you to start doing regular image backups to an external HD.
Remember that HD's don't last for ever. Sooner or later it will fail. Being prepared for a disaster always needs to happen
before the disaster. This time the system failure was do to a software glitch but there are many things that can cause it.
-
About this BSOD, a little inside information we got from Avast :
The problem was with program code released with the VPS 170320-0 virus definition update.
All VPS updates go through levels of automated tests, but this one slipped through because the faulty code kicked in after longer period of time.
So no excuse, but a different and/or difficult scenario to test imo.
Greetz, Red.
-
You son of a bitch, I lost 1 day of work and $50
-
Fuck you avast, i will use AVG.
-
Fuck you avast, i will use AVG.
LOL ;D ::)
-
Congrats AVAST! Ever since Win 7 was released no other software at my hand managed to crash it with a bluescreen! That really gives me confidence installing the yet purchased AfB Version for our application server.
Good for you, that your marketing department has my email address and knows, how to use it. Sad enough, that your support doesn´t see the necessity to send out a warning, before I and others spend a days work to get systems up and running again.
Maybe you should consider spending less time in developing useless gismos and gadgets like "safe price" and stuff, that noone wants to see at least in a paid software product and get´s installed by default, if not unticked upfront. Meanwhile I will consider the future renewals of our 60+ licenses maybe being a perfect moment to switch products...
Best regards
A.Koller
-
Fuck you avast, i will use AVG.
Ha Ha, you know Avast! own AVG now right?
-
Fuck you avast, i will use AVG.
You do realize they are the same company now.
-
;D
-
After some investigation, our technology have discovered, that the bug was caused by code in antirootkit module, which is linked into aswsp.sys driver. When VPS update was released yesterday, it started querying some additional PE information data from driver which crash OS.
We haven't seen any crashes on Win7 x64, or Win8, which supports our theory that the main cause is probably Win7 x86 OS bug. It is also worth mentioning, that crashes are not inside our driver, but in NT kernel module.
Sorry for any inconvenience caused.
Alex
-
I also crashed yesterday, same system same version, so now I changed the update to manual because I lost some important work. But, I can't understand the programming logic of Avast with their icon indicating a warning when the update is set to manual. The standard warning with the exclamation can mean anything. It would be preferable to display a blue "M" to remind users that their update is set to manual.
-
After some investigation, our technology have discovered, that the bug was caused by code in antirootkit module, which is linked into aswsp.sys driver. When VPS update was released yesterday, it started querying some additional PE information data from driver which crash OS.
We haven't seen any crashes on Win7 x64, or Win8, which supports our theory that the main cause is probably Win7 x86 OS bug. It is also worth mentioning, that crashes are not inside our driver, but in NT kernel module.
Sorry for any inconvenience caused.
Alex
How will you stop this from occurring in the future?
-
I really like avast for business, but I had to uninstall in my entire environment.
I would love to install it again, but how can I be sure that no blue screen will come at my door again?
-
I really like avast for business, but I had to uninstall in my entire environment.
I would love to install it again, but how can I be sure that no blue screen will come at my door again?
I'm sure Avast will do everything humanly possible to make sure it will not happen again.
Just as there are no guarantees in life, there really can't be any guarantees with this.
Microsoft gives no guarantees and we've all experienced an update problem that's gone wrong.
Back up on a regular basis so that you're prepared for a disaster if it should happen.
There's also no guarantee on your hard drive. The only guarantee is that eventually, it will fail.
-
I would like very much a final verdict about the incident.
Until now, we're guessing it was a Microsoft Windows kernel bug that was triggered from Avast antirootkit.
We need to apologize for a lot of things and, after all, fix requires a Microsoft update... It's ironic...
-
Hi,
It cause me so inconvenient.
It let me think hardware problem initially. (Depends on BSOD code.
It is so important Avast R&D to handle this issue carefully and to test your patches in detail before push clients update.
Otherwise, it will make the bad reputation of Avast into the World !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Hope all of Avast team members have to note that.
Stability, Reliability and Performance are important to customer rather than beautiful GUI of anti-virus program.
-
After some investigation, our technology have discovered, that the bug was caused by code in antirootkit module, which is linked into aswsp.sys driver. When VPS update was released yesterday, it started querying some additional PE information data from driver which crash OS.
We haven't seen any crashes on Win7 x64, or Win8, which supports our theory that the main cause is probably Win7 x86 OS bug. It is also worth mentioning, that crashes are not inside our driver, but in NT kernel module.
Sorry for any inconvenience caused.
Alex
Well, Windows XP is an old operating system and then it's working on it, forget it
But it turns out that the Avast command does not test updates to Windows 7 32 bit (x86). This is very bad. How can this be? In the world, there is 32 bit (x86) and 64 bit (x64) today. I understand that there is also Windows 10, but it's not everywhere yet
Even the masters for refilling printer cartridges on the shelves have several printers for testing printing after refueling
And at you the big company under mark Avast of a world level only two kinds of operational systems for tests and only x64
Strange ...
-
My issue with the entire situation is this. We could have been notified via email. I had to register with my email as well as sign in to manage our devices.