Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: REDACTED on April 22, 2016, 04:58:57 AM

Title: Microsoft Wireless Display Adapter
Post by: REDACTED on April 22, 2016, 04:58:57 AM
Hello,

First off I am new to Avast; I am also not so tech savy...  I am trying to connect to a Microsoft Wireless Display Adapter with Premier, Windows 10.  If I turn off the firewall all will work fine; with firewall on it's a no go.  I can't figure out where to add and exception for the adapter within the Avast firewall...

Thanks in advance.
Title: Re: Microsoft Wireless Display Adapter
Post by: Asyn on April 22, 2016, 06:11:45 AM
-> https://www.avast.com/faq.php?article=AVKB25#artTitle
Title: Re: Microsoft Wireless Display Adapter
Post by: REDACTED on March 15, 2018, 02:26:08 PM
Hi, I'm having this issue with my MSDisplayAdapter_3B (Firewall blocks it) but the FAQ on creating a program exclusion doesn't work for me. There isn't a program that I'm activating. I'm connecting to a wireless display through the "Project" function. It's currently listed as being connected to "Local Area Connection* 16 (Adapter)".

How do I adapt those exclusion rules to this connection?

(I'll post back if I find it.)
Title: Re: Microsoft Wireless Display Adapter
Post by: bob3160 on March 15, 2018, 04:53:09 PM
Is your connection currently set to private ???
Title: Re: Microsoft Wireless Display Adapter
Post by: REDACTED on March 17, 2018, 12:37:27 AM
That does actually fix it! Thank you!
Title: Re: Microsoft Wireless Display Adapter
Post by: bob3160 on March 17, 2018, 01:22:05 AM
That does actually fix it! Thank you!
Your welcome. :)
Title: Re: Microsoft Wireless Display Adapter
Post by: hd.naujoks on April 02, 2020, 08:19:09 PM
That does actually fix it! Thank you!
Your welcome. :)

Sorry, but this seems to have stopped working since a security update during the last weeks. Now on each connect to the MS Display Adaptor Win 10 assignes a new randomly assigned network connection name which invalidates any previous setting to private mode. Please Avast, give us a solution that allows the use of the MS Display Adaptor without totally switching the firewall off.
Title: Re: Microsoft Wireless Display Adapter
Post by: bob3160 on April 02, 2020, 08:51:30 PM
That does actually fix it! Thank you!
Your welcome. :)

Sorry, but this seems to have stopped working since a security update during the last weeks. Now on each connect to the MS Display Adaptor Win 10 assignes a new randomly assigned network connection name which invalidates any previous setting to private mode. Please Avast, give us a solution that allows the use of the MS Display Adaptor without totally switching the firewall off.
Reported to Avast
Title: Re: Microsoft Wireless Display Adapter
Post by: lukor on April 02, 2020, 09:09:03 PM
Hi, can you, please, try if enabling ICS mode will help you?

On Firewall page / Settings and then this, see image:

Title: Re: Microsoft Wireless Display Adapter
Post by: hd.naujoks on April 04, 2020, 10:06:31 AM
Nope, no change: In lower part of the FW settings screen you see those failed connections with generated names.

TIA,
hdn
Title: Re: Microsoft Wireless Display Adapter
Post by: GaryDaniels on April 10, 2020, 08:34:42 PM
1. Go to Protection -> Firewall and set your Network to Private
2. Below that, click Settings and check Internet Connection Sharing Mode
3. On the same page, click System Rules and set both Allow Windows File and Printer sharing & Allow remote desktop connections to this computer to Enabled. Click OK
4. Click Packet Rules and add 4 new rules: (see attached image)
     UDP Local port 67
     UDP Local port 68
     UDP Remote port 67
     UDP Remote port 68
5. Restart your computer for settings to take effect.

(http://)
Title: Re: Microsoft Wireless Display Adapter
Post by: bob3160 on April 11, 2020, 03:30:57 PM
1. Go to Protection -> Firewall and set your Network to Private
2. Below that, click Settings and check Internet Connection Sharing Mode
3. On the same page, click System Rules and set both Allow Windows File and Printer sharing & Allow remote desktop connections to this computer to Enabled. Click OK
4. Click Packet Rules and add 4 new rules: (see attached image)
     UDP Local port 67
     UDP Local port 68
     UDP Remote port 67
     UDP Remote port 68
5. Restart your computer for settings to take effect.


Sorry but I don't see the image and it would be very helpful. Thanks
Title: Re: Microsoft Wireless Display Adapter
Post by: hd.naujoks on April 11, 2020, 07:48:29 PM
Sorry, but connect still fails when FW hasn't been switched off first.
I'm posting the settings I made the way I understood your recommendations.
Title: Re: Microsoft Wireless Display Adapter
Post by: bob3160 on April 11, 2020, 07:51:18 PM
@ hd. naujoks,
Did you restart the computer after making those changes? Thanks
Title: Re: Microsoft Wireless Display Adapter
Post by: hd.naujoks on April 11, 2020, 08:08:04 PM
Yes I did, more than once to be sure. First time btw was to allow the changes as my mouse cursor disappeared every time when moving it over any Avast window, an effect I've already noticed a few times before. And of course I restarted when all changes were correctly saved.
Title: Re: Microsoft Wireless Display Adapter
Post by: bob3160 on April 11, 2020, 08:39:51 PM
Following your instructions but, I can NOT confirm your findings.
For me, once these changes described by you and GaryDaniels work.
As you can see from the photo I just took, my laptop is now projecting
to my TV using the Microsoft Wireless Display Adapter
(https://screencast-o-matic.com/screenshots/u/Lh/1586630299886-24412.png)
Please make sure that your settings have actually taken. They certainly work for me.
Title: Re: Microsoft Wireless Display Adapter
Post by: hd.naujoks on April 16, 2020, 11:19:01 PM
Of course I appreciate everyone's effort to support me a lot and I also envy you for my settings are working for you  ??? but unfortunately after double-checking all settings nothing has changed: Avast FW = ON means connect fails after a long time the MSWDA was showing "Connecting to <PC-name>", Avast FW = OFF means connect is successful and adapter shows the display like intended. Maybe you're using a different adapter FW version (mine is V.2.0.8381) or a different Win 10 Version (mine is 1909 Build 18363.778) or a different Avast version (mine is 20.2.2401 (Build 20.2.5130.570). Even switching FW back to ON after having conncted to the MSWDA successfully makes the connection break within 10 seconds or so.

Title: Re: Microsoft Wireless Display Adapter
Post by: Asyn on April 17, 2020, 05:43:12 AM
You could try the latest beta: https://forum.avast.com/index.php?board=15
Title: Re: Microsoft Wireless Display Adapter
Post by: hd.naujoks on April 19, 2020, 04:58:29 PM
Well, to be quite frank as I have to do a lot of beta testing in my professional life but getting payed for, I'm not much affected to do the same for something I'm paying for in private. Maybe compatibility to the current version of MSWDA should be put on the compatibility list for your next release tests and I'lll wait for that to solve my problem.
Title: Re: Microsoft Wireless Display Adapter
Post by: bob3160 on April 19, 2020, 05:27:06 PM
Well, to be quite frank as I have to do a lot of beta testing in my professional life but getting payed for, I'm not much affected to do the same for something I'm paying for in private. Maybe compatibility to the current version of MSWDA should be put on the compatibility list for your next release tests and I'lll wait for that to solve my problem.
I'm on the beta version and after the latest update, the sharing again does not work.
I have checked and all the rules and settings are still as suggested but, the connection fails.
Guess for now, I have no choice but to switch back to the Windows Firewall.  :( 
@hd.naujoks,
We are on the same version of MS and use the same version for the Wireless display adapter.


Title: Re: Microsoft Wireless Display Adapter
Post by: bob3160 on April 20, 2020, 03:03:28 PM
I've again reported this to Avast. Let's see if that helps.