« Reply #74 on: July 17, 2015, 03:44:14 AM »
As best as I can determine, something in this newest build is blocking the MSRT (Microsoft's Malicious Software Removal Tool) from running on XP: when avast is enabled, the MSRT starts/tries to run, but it just "dies" and exits from memory... there are no warning messages from avast, and nothing appears to have been quarantined.
But if I disable avast's shields --- specifically, the File System shield --- I can then run the MSRT. Seems to be a clear "cause and effect" relationship here.
« Last Edit: July 17, 2015, 03:54:37 AM by ky331 »
Logged
Lenovo T530 laptop, Intel Core i5-3320M @ 2.60 GHz, 8GB RAM, Windows 7 Pro SP1 (64-bit), avast! 17 Free, MBAM3 Pro, Windows Firewall, MVPS HOSTS file, OpenDNS Family Shield, Zemana AntiLogger Free, SpywareBlaster, IE11 & Firefox [both using WOT (IE set to WARN, FF set to BLOCK)], WinPatrol PLUS, uBlock Origin, MBAE, MCShield, CryptoPrevent, SAS (on-demand scanner).
[I believe computer-users who sandbox (Sandboxie) are acting prudently.]