The new update 1473 is causing my pc to freeze on startup. This has never happened before. This never happened with 1466 before. My system is Windows 7 ultimate 64bit sp1. Other security software I use is Malwarebytes pro, superantispyware pro, comodo firewall, and exploitshield. Everything is up to date. Other then exploit shield which i just added a month ago because its a new software, I have been using all of this for many years and haven’t had this problem with Avast before. Untill this problem can be fixed, I have switched Av over to comodo av. Also I haven’t used any Av before Avast. I have used that since 4.8.
Try this: http://forums.malwarebytes.org/index.php?showtopic=10138&p=417798&#entry417798
Better now…??
I did what you said and after a few restarts the problem no longer exists. This is, however, unusual on why this all of the sudden happened and has never happened before in the past. No matter the problem is fixed, looks like I won’t have to get rid of Avast after all, good because I love Avast.
I’m experiencing this as well…using AIS. I have Win7x64…figured it was just my pc but have made 5-6 attempts this week with same problem…
Version 7.0.1466 is different from the new version 7.0.1473. Possibly different file versions introduced, so MBAM did not know what to do with the new Avast! files? Seems MBAM locked your system up? Strong security programs can do this due to configuration issues; MBAM is one of them.
Unknown file versions in a security program can lock things up as this is a configuration issue here. Maybe turn off the protective part of MBAM Pro in the future when updating may allow the changes to be registered after reboot and then turn MBAM protection back on? Four step procedure here: MBAM protection off>Update Avast!>Reboot>Avast! fully loads>Turn MBAM Pro back on. Might save a reboot or two for you if it happens again, but I suggest using this short four step process to avoid this in the future. Might work.
I uninstalled MBAM-Pro and problem gone. This is the only upgrade I have ever had an issue using AIS.
You’re welcome.