Here's the first log I got on February 1: Malwarebytes' Anti-Malware 1.50.1.1100 www.malwarebytes.org Database version: 5657 Windows 6.1.7600 Internet Explorer 8.0.7600.16385 2/1/2011 11:29:05 PM mbam-log-2011-02-01 (23-29-05).txt Scan type: Flash scan Objects scanned: 106059 Time elapsed: 10 second(s) Memory Processes Infected: 0 Memory Modules Infected: 0 Registry Keys Infected: 0 Registry Values Infected: 0 Registry Data Items Infected: 0 Folders Infected: 0 Files Infected: 0 Memory Processes Infected: (No malicious items detected) Memory Modules Infected: (No malicious items detected) Registry Keys Infected: (No malicious items detected) Registry Values Infected: (No malicious items detected) Registry Data Items Infected: (No malicious items detected) Folders Infected: (No malicious items detected) Files Infected: (No malicious items detected) ____________________________________________ Now all I get is something like this, as of the last 7 logs: 14:46:09 Michael MESSAGE Protection started successfully 14:46:13 Michael MESSAGE IP Protection started successfully 17:22:48 Michael MESSAGE Protection started successfully 17:22:53 Michael MESSAGE IP Protection started successfully 22:05:15 Michael MESSAGE Protection started successfully 22:05:19 Michael MESSAGE IP Protection started successfully 22:37:59 Michael MESSAGE Protection started successfully 22:38:04 Michael MESSAGE IP Protection started successfully 22:57:29 Michael MESSAGE Scheduled update executed successfully 22:58:27 Michael MESSAGE IP Protection stopped 22:58:28 Michael MESSAGE Database updated successfully 22:58:30 Michael MESSAGE IP Protection started successfully AND most recently : 12:50:02 Michael MESSAGE Protection started successfully 12:50:06 Michael MESSAGE IP Protection started successfully 15:41:09 Michael MESSAGE Protection started successfully 15:41:14 Michael MESSAGE IP Protection started successfully 18:30:46 Kent MESSAGE IP Protection stopped 18:30:48 Kent MESSAGE Database updated successfully 18:30:50 Kent MESSAGE IP Protection started successfully 18:56:58 Kent MESSAGE Protection started successfully 18:57:03 Kent MESSAGE IP Protection started successfully 19:00:59 Kent MESSAGE Protection started successfully 19:01:04 Kent MESSAGE IP Protection started successfully 19:33:21 Kent MESSAGE Protection started successfully 19:33:25 Kent MESSAGE IP Protection started successfully 21:30:06 Kent MESSAGE Protection started successfully 21:30:11 Kent MESSAGE IP Protection started successfully 21:44:59 Michael IP-BLOCK 212.117.176.187 (Type: outgoing, Port: 49602, Process: avwebgrd.exe) 21:45:07 Michael IP-BLOCK 212.117.176.187 (Type: outgoing, Port: 49608, Process: avwebgrd.exe) 21:45:23 Michael IP-BLOCK 212.117.176.187 (Type: outgoing, Port: 49614, Process: avwebgrd.exe) 21:45:23 Michael IP-BLOCK 212.117.176.187 (Type: outgoing, Port: 49620, Process: avwebgrd.exe) 21:45:47 Michael IP-BLOCK 212.117.176.187 (Type: outgoing, Port: 49626, Process: avwebgrd.exe) 21:46:27 Michael IP-BLOCK 212.117.176.187 (Type: outgoing, Port: 49632, Process: avwebgrd.exe) 21:47:15 Michael IP-BLOCK 212.117.176.187 (Type: outgoing, Port: 49652, Process: avwebgrd.exe) 21:47:15 Michael IP-BLOCK 212.117.176.187 (Type: outgoing, Port: 49658, Process: avwebgrd.exe) 21:47:39 Michael IP-BLOCK 212.117.176.187 (Type: outgoing, Port: 49661, Process: iexplore.exe) 21:47:39 Michael IP-BLOCK 212.117.176.187 (Type: outgoing, Port: 49662, Process: iexplore.exe) 22:57:33 Michael MESSAGE Scheduled update executed successfully 22:58:34 Michael MESSAGE IP Protection stopped 22:58:36 Michael MESSAGE Database updated successfully 22:58:38 Michael MESSAGE IP Protection started successfully _______________________________________ It wasn't blocking antivir webgrd. initially, and was reporting on all other kinds of information. Now it doesn't say anything except IP blocking and updates. I haven't changed any settings in either program. Further, as a quirky aside, it fails to name the Michael account properly. That isn't the name of the account. It's Mikey.?? But mainy I'd like to know if the program is doing what it is supposed to be doing, given the most recent logs v. the initial log. Was the initial log even reporting what looks like a proper log? thanks mucho for any assistance, Mikey