Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: cheblasko on August 18, 2012, 09:23:55 PM
-
I have a problem with avast antivirus free. In the device manager does not recognize Avast! Firewall NDIS Filter Miniport and you can not install this device.
-
Could you provide us a hijack log of your machine?
What is your avast build? https://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=586#idt_01
thank you
Lukas.
-
Hi Lukas
I have the same problem and I tried to reinstall the drivers and it didn't help. I am using a paid version of Avast.
Thanks
-
Hi,
Same problem for me: The system advises me that this peripheral is not operating properly.
What to do now?
I have the latest updated retail avast Internet Security, automatically updated and running on W7 x64 ultimate.
Please advise what to do now?
What is this peripheral for? How to repair? There is no new driver on the net via Windows update.
Thanks
Patrice.
-
Also having the same problem. Started occurring after recent program update. Also, I used a product key to upgrade from the free to the Security Pro version. The miniport shows up in the device manager in one of two ways. For a while, it displayed the full name (avast! firewall NDIS Filter Miniport) under network devices, and every time I tried updating the drivers, it would say the drivers were found but access was denied. Now, the device just appears as unknown device and reads "The drivers for this device are not installed. (Code 28) Access is denied." in the properties. I will run a hijack scan and post the log here soon.
Update: I tried uninstalling the device, and avast! seems to work fine. Is this device really necessary for the firewall? Avast still shows the firewall as operational and my internet connection has not disappeared like some people have found.
-
Same issue here, with Windows 7 reporting "Avast! firewall NDIS filter miniport xxx" not installed, where xxx has been various three-digit numbers (lately 344).
The Avast! Firewall NDIS Filter Driver does show up as "checked" in the properties for all network adapters and everything seems to be working correctly -- except for the error box that Windows 7 pops-up when the machine boots up.
I do have a VPN connection and VirtualBox "adapters." Perhaps related?
Regardless, is uninstalling the non-functioning miniport effective in suppressing the error message withoug adversely affecting the box's security?
-
Same here,every boot up tries to install it and fails.
Only since last update.
AIS and Windows 7
Ian
-
I have the same problem. Win 7 and the error on startup is a fail to install driver error for "Avast NDIS filter miniport #8". See Hijack log and AVAST IS version screenshot. Thank you.
-
I have been all round the houses with this problem - first my wireless printer stopped working on 8th August. I uninstalled/reinstalled, phoned HP. Have spent a MONTH on the phone with them, problem not fixed. Bought a new printer and finally got an error message 'Avast! Firewall NDIS Filter Miniport #82 xFailed'. Its been AVAST all along. Phoned for help, Avast tried to charge me £120 for a fix. OUTRAGED.
-
:o This seems to be a general problem, though it doesn't disturb my computer activities, but I'm worried for its existence!
-
The same problem and this is the text from windows after driver installation failure: Avast Firewall NDIS Filter Mini port #698
OS: Windows 7 Ultimate x64
Avast Internet Security version 7.0.1466
-
Hi,
I've been getting strange driver messages for the past month or so, and today the same description I'm seeing here in the Forum appeared.
So we're not alone. I'm also slightly alarmed.
Does anybody know what's the score?
Iain
-
Hello,
was it really avast support who you called?
Can you provide me with phone number, date and time when phone call took the place?
Thank you
I have been all round the houses with this problem - first my wireless printer stopped working on 8th August. I uninstalled/reinstalled, phoned HP. Have spent a MONTH on the phone with them, problem not fixed. Bought a new printer and finally got an error message 'Avast! Firewall NDIS Filter Miniport #82 xFailed'. Its been AVAST all along. Phoned for help, Avast tried to charge me £120 for a fix. OUTRAGED.
-
I could also be having the same problem I have a 250 GB WD Elements External HDD that was working fine on my Netbook, firstly with W7 then W8-DP, W8-CP and then starting about a 6 weeks ago with Ubuntu.
The drive is formatted as NTFS and has a bunch of backup data on it.
I removed it from the Netbook running Ubuntu, which is not using avast! and tried to connect it on each of my three W7-SP1 computers. Windows will not install the drivers and not assign a drive letter to it on any of the three desktop computers.
I don't know if it is the same problem or not but seems like it could be.
-
Same issue here, just started after re-install of parallels on MB Pro.
Paid version on Win 7. Tries to install miniport #5 and #6, Fails both.
-
SO anyone has a solution? thanks in advance
-
Same problem over here :-[!
-
Got this fix from Avast support:
Fully Boot up in SAFE MODE then reboot Normally... problem should be gone
Sounds crazy, but it worked for me...
-
Had the same problem with the NDIS Filter Miniport driver.
Went into Safe Mode with Networking option -> selected Devicemanager -> updated the NDIS driver and everything was OK.
-
I tried with booting to safe mode and just rebooting, but it didn't help. Then i tried to "update" the driver from safe mode, but didn't find a way to do it. It was always reporting as being up to date. So i uninstalled it, hoping i can install the driver again, but the driver is now lost in device manager.
The good thing is, everything is working just fine, or at least it looks that way :D Windows is not trying to install the software.
Can i leave it like this or should i try to install the driver again? I did the avast repair, but the driver is still missing form device manager.
-
Same here. I've been having an error coming up for a while now and it happens every time I log into windows ( Windows 7 ). A few days ago I got tired of seeing it so I called Avast customer service (1 (877) 696 4358) the person who I spoke with was just telling me that my computer was infected with viruses and that It was hacked, so he recommended me to send me a technician from Avast team or going to one my self and get my PC fixed, I asked him that what was the point of me paying for Avast Internet Security if I wasn't been protected against this kind of stuff and all he did was recommend me again to get a technician and fix my "broken PC"... I always loved using Avast antivirus (been using it for over 4 years) but honestly after this, not so happy with the software.
-
I had four different miniports showing that there was a failure and would not update. As someone else mentioned, I rebooted in "safe mode with networking" then went to control panel, device manager, and then found the ports listed with a small yellow triangle and an exclamation point in the device manager list. I let the computer set for a minute and the screen blinked about four times. One by one the drivers automatically updated. What was strange is that I had opened the "device properties" box and was going to manually select "update" but the button was not active. As I say they updated all by themselves while I was in the device manager screen. Once that was done, I restarted again in normal mode and everything was fine. The driver installer didn't show up again and the failure dialog box wasn't there. It just seemed to take the computer a moment in safe mode to process the updates.
-
Got this fix from Avast support:
Fully Boot up in SAFE MODE then reboot Normally... problem should be gone
Sounds crazy, but it worked for me...
I was absolutely hopeless, as this bug was continuously blocking my WiFi access. I booted up in safe mode (with network options) and I went into device manager, and the whole firewall ndis filter was gone!
After that I booted up normally and he was still gone! So I'm loving it!
It's absolutely nuts that it fixed the issue, but I'm happy it helped! Thanks for sharing it!