Windows 10 - Latest Update - Unable to start Firewall!

[REDACTED]

Nothing.

[Avosec-UK]

Nothing.

And you don't have the service in the MS's Services Snap-in?

[REDACTED]

I see the registry has the entries for the avast! firewall.

The avast! Firewall service has been installed, configured for automatic startup on the Local System, but is not running. Manually starting this service results in a quick stop and the following message: "The Avast! Firewall service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs." Should be noted, I see no dependencies identified.

I don't see any events associated with aswNdisFlt or avast! Firewall in event viewer. I checked the Device Manager for installation of Ndis driver under the Network Adapters, none are present.

[REDACTED]

I see the registry has the entries for the avast! firewall.

The avast! Firewall service has been installed, configured for automatic startup on the Local System, but is not running. Manually starting this service results in a quick stop and the following message: "The Avast! Firewall service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs." Should be noted, I see no dependencies identified.

I don't see any events associated with aswNdisFlt or avast! Firewall in event viewer. I checked the Device Manager for installation of Ndis driver under the Network Adapters, none are present.

Same thing here.

[REDACTED]

Nothing.

And you don't have the service in the MS's Services Snap-in?

Like he saif, it's there, but running the service stops.

[REDACTED]

OK,
Event Viewer\Windows Logs\System\Information Event (7026)
The following boot-start or system-start driver(s) did not load:
AFD
aswNdisFlt
aswRdr
aswRvrt
aswSnx
aswSP
aswVmm
ATKWMIACPIIO
CSC
dam
Dfsc
FileCrypt
GpuEnergyDrv
GUBootStartup
NetBIOS
NetBT
nsiproxy
Psched
rdbss
RrNetCapFilterDriver
snapman
tdx
vwififlt

[Avosec-UK]

Alright then, digging further:

In both of the log files I see the same error before the installation of the FW driver:

Error: Unable to uninstall OEM inf file 'C:\WINDOWS\Inf\oem*.inf' with error 0x00000057!

Error 0x00000057 translates to "A network adapter hardware error occurred.".

@jdfrench3 can you attach C:\WINDOWS\Inf\oem90.inf
@Theberge43 can you attach C:\WINDOWS\Inf\oem47.inf

Let us see what these are.

[REDACTED]

Attached is a copy of my oem90.inf file converted to image files for posting.

[REDACTED]

https://cloudup.com/cblQWDInHIL

[REDACTED]

The oem90.inf file list the ClassGUID as {4D36E974-E325-11CE-BFC1-08002BE10318}.

The Intel 6235 NIC involved has a ClassGUID of {4D36E972-E325-11CE-BFC1-08002BE10318}.

Could this difference be enough to cause the driver not to be installed?

[hillen]

Here is what I have found... If a computer had an existing Avast product on it such as Internet Security, even though it was uninstalled using the Avastclear, the firewall will not install. One must run a repair to even get it to install the service, but the actual service won't start. DOA.

The only machines the firewall actually installs on are computers with fresh installs and no prior Avast product being installed.

Avast, this is really serious as you are leaving us vulnerable. Once again none of you are even giving a "hey, we're looking into it" just the usual silence. Will this all come down to a company having to actually sue you for damages when corporate networks for infected because of your faulty products and lack of communications ?

[hillen]

Jumped through all of the hoops again and here is what is failing to install.

Error installing aswNdisFlt.inf ( 0x80070002 )

[REDACTED]

Actually what isn't working is netcfg_x64.exe, this in turn, installs aswNdisFlt.inf.

The date of my netcfg_x64.exe is 2/17/2010. A little old for handling Windows 10 OS.

C:\Program Files\AVAST Software\Avast Business\Setup\INF\x64

[hillen]

yep -- so what is the FIX!

Also just an fyi... the firewall will no longer start on the "good" installs.

What a mess!

[REDACTED]

Well, Avast promised a Windows 10 compatible Endpoint Protection product by the end of December... That still gives them a few days.

1. Must fix this firewall (Ndis) issue. Must be made so that the new version will install right on top of the previous versions.
2. Must be able to use Microsoft Edge browser to work with Admin Console. No more dependency of Silverlight, Chrome, or Internet Explorer on a W10 PC.

Users with problems with the new Avast! programs, need to walk away, demanding a refund for the unusable product that has been promised for months.