system
1
Hello I get Multiple Network Adapter - Unknown Devices - sw_aswNdidMP. Every time I boot the computer it adds another. after the 1st one I get a driver cannot be installed.
This device is not configured correctly. (Code 1)
Insufficient system resources exist to complete the requested service.
To find a driver for this device, click Update Driver.
I have the latest Avast update and believe the sw_aswNdidMP is something to do with Avast firewall.
Win7. Plenty of resources Q720 1.6ghz, 6GB memory
I delete them all and they start to come back.
mchain
2
hi burkeam,
What version of avast!, os, and SP?
Free, Pro, AIS, Premier? 6, 7, 8.0.xxxx, beta?
mchain
4
AIS 1497 is beta.
Suggest a repair of avast! Since info re operating system is missing, cannot specify exact way to perform this, as XP and newer have slightly different ways of accomplishing this.
Please share.
system
8
win7 pro/64 sp1, Everything is updated every Tuesday.
defender is running. Has only block a adware once on 3/2011
I have been using AIS since new - almost 2 year old. Only Avast ever installed on machine. I don’t think the free version was ever on this machine
system
10
Thanks Asyn,
I had problems but got it to work with a addition to you instructions.
With the instructions I got a firewall installation error. See attachment.
Did it a 2nd time but after using the uninstall utility I deleted the network adapter driver relating to avast.
The install then worked.
Rebooted machine another 3 time and only see 1 unknown device with the sw_aswNdidMP. Should this be here?
system
11
Here the driver errors on the 1st install
system
13
Followed instructions and no change after reboot.
2nd time I deleted the Unknown network adapter 1st then repaired as instructed. It is now gone.
I’ll post again if it comes back.
thanks for the help Asyn.
system
15
It came back. Multiple network adapters -unknown device. Noticed when trying to sink phone via USB or wireless. Cannot connect. driver details sw_aswNdisMP
Asyn
16
Did you update to V9 already…!?
system
17
I did now. Didn’t know it was out. Hopefully it corrects this issue