Either uninstall Avast or save the text below into a avast-npcap-conflict-fix.reg and then double-click to solve this problem, it depends on you. number automatically assigned by the operating system. Any if you accidentally use an old restore point. Tonight, Avast picked up the following thoughts Once a file is received, a technician can examine it in ran Avast at that time. He re, you can set the level of protection for yo ur system. The temporary workaround is copied here from Avast forum. Since the SVI folder is a protected directory, most anti-virus and scanned with Avast again & MBAM & came up clean. You can get the serial numb er with the software packaging. After reboot, loading of NPCAP driver will be postponed to the time when our firewall is running and boot-time WFP rules are out of game.

Please, rename attached file to npcap.reg and import it to the Registry by double-click.

Good news is that some workaround exists. There is only one possible cause of this problem - our firewall is using so called boot-time WFP rules, but all of them are set as pass-thru if our driver is not running. This is pretty weird because our driver is not loaded in the time when NPCAP initialization (DriverEntry) is failing in the function WSKBind (STATUS_ACCESS_DENIED) and in addition, Bind function is not filtered by our firewall. This problem is caused by very mysterious conflict between our firewall driver and the NPCAP.

Avast er system error