Well I don't see any problem with the information in your. The Comodo forums reconfirmed just this week that CIS with D+ uses sandbox technology and is awake protecting my pc even during boot up! I'll schedule a boot scan in a bit to see if the logs show any of those Comodo induced 'can't scan' errors. I don't think I thought to check the logs the last time I ran a boot scan, either. To be quite honest, I never remember/think about boot scans unless I suspect adware of some sort. But when I turn off my FW those 'can't scan' errors do not appear in the avast log viewer, so I know Comodo's protecting them from all attempts to open/access. The reason I like to go out to safe mode to do my weekly scans is because if done in normal mode, my Comodo CIS with Defense+ (HIPS) protects so dang many files from being opened that it causes Avast to render all sorts of errors about not being able to scan half of the executables and files you would WANT it to scan.

I welcome any input.ĭuh! Now why didn't I think of that, David? This is a recent clean install of Avast, too, I might add. Maybe it isn't assigning my dynamic IP in a timely fashion and this is causing the drivers in the first msg to not load properly? Dunno. Maybe I need to call AT&T tech support and ask if something needs to be reset on the modem. My pc was wiped and aclean install of WinXP was done on Feb 12th. It lets me access the internet OK with all 3 lights green. My ATT DSL modem/router appears to be working OK. No Exclamation Marks to the left of anything. I have checked Device manager and upon expanding all items, there are no hardware problems. The DHCP Client service depends on the NetBios over Tcpip service which failed to start because of the following error:

The DNS Client service depends on the TCP/IP Protocol Driver service which failed to start because of the following error: The TCP/IP NetBIOS Helper service depends on the AFD service which failed to start because of the following error: The IPSEC Services service depends on the IPSEC driver service which failed to start because of the following error:Ī device attached to the system is not functioning.

The following boot-start or system-start driver(s) failed to load: If it's important, Event Viewer is showing this System error: Can anyone shed any light on this error message? Other than this one log error entry, the scan results screen just showed what I would expect, just 3 files that were not scanned due to the fact they were SAS quarantined files and PW protected, which I know is normal. I've tried calling up a search of the forums every way I can think of but get no results. Internal Error has occurred in module aswar scan function failed, function 00000002. The Error log after the scan has this entry: I just did an Avast 'Thorough' scan with 'Scan Archives' enabled out in SAFE MODE.

Avast safe mode scan