We had a few computers not boot up correctly this week. Seemed to start right after the update released by avast to address the issue with the windows 8 computers not behaving correctly after that Microsoft update discussed in another post. However my startup issues are with some windows 7 pc’s. I was forced to do a system restore so I can log in. Once logged in, I saw that Avast had a red mark going thru it. I needed to uninstall and reinstall avast on all the PC’s with this Startup issue. After the reinstall, I needed to browse out to the location of our license file otherwise the installations would all be running in trial mode. Everything went back to normal once the license file got updated on the computers.
Has anyone else had this problem this week? It happened to 4 of our PCs on Wednesday and 3 computers this morning.
I’m not a expert on the business edition(s) so don’t take my word for it,
but if I’m correct it can take a few hours before the client pc’s pull the license from the server.
We have ran into a similar issue. We were out for thanksgiving, on Monday a handful of 7s were stuck in startup repair mode, today even more are. Although it appears logging in safe mode and uninstalling and reinstalling avast corrects the issue.
We had about 50 Win7 machines with this issue Monday morning too. BSOD Bug Check code 0x1000007e. Tries to run Startup Repairs which doesn’t work. Boot into Safe Mode and uninstall Avast and the machine restarts normally. Re-install Avast and everything is still working fine. I Thought it might have been a bad update from Tuesday 11-23-2014 which was the last day of school before our break for Thanksgiving, but today I walked into about 5 more computers with different hardware that had this same issue.
Sure would like to find the root cause of this because at about ~10 minutes per machine it’s getting very OLD.
I’ve also experienced on 2 PC’s that if the repair is successful the PC looses the trust relationship to the network. Avast what’s going on? This issue seemed to start last Wednesday with everyone.
I have investigated some of the failed computers and noticed that the aswsnx.sys is version 8.0.11603.401 (Modified 11/25/2014) while the ones that are working correctly are 8.0.11603.399
It was stated that Avast team updated aswsnx.sys in order to correct the issue with KB3000850 (which only affected windows 8.1 systems) I am curious if that update got mistakenly sent out to other OSs or if the other ones are going to get this update and fail eventually.
Our 32 bit Vista machines started doing this recently. It is the “other” patch… KB3011780 - if it installs before avast gets updated to the latest engine, bad things start to happen.
Fix seems to be: Reboot the machine in safe mode with networking, uninstall KB3011780, do not reboot, go into the avast installer (from programs and features) and do an update there, while in safe mode with networking… let avast reboot the machine after it is done updating… reinstall KB3011780…
Avast is this change meant to only comedown to Windows 8 OS’s and no other OS types? What about Windows server 2012, 2008R2 etc. I’m petrified to power down my servers or restart them now fearing that this issue could also happen to them. They are all showing aswsnx.sys version 8.0.11603.399.
Its ridiculous that we would need to go thru all these steps. We can’t be playing games with a live environment!
I have the same issue in our school district, calls started last Wednesday and continue through today. Win7 machines with startup repair or BSOD.
Booting to safe mode, uninstalling Avast rebooting and re-installing has fixed the problem so far. 42 machines and counting.
If so, that isn’t avast!. Our School Network system has the same issue (Usually only affects a few computers on any given week). That’s an issue the the network and the computer. I believe the fix is to take the computer out of the domain, and then put it back in. Don’t take me 100% on that, because I’m only 16 and not the technician here. (However, I am pretty familiar with how things run here)