Dave, you've done well, and exhibited uncommon patience. I have precisely the same issue, on different televisions, but the same (fully up to date) Surface Pro and Surface 3 pcs failling to properly connect with a Microsoft Display Adapter in exactly this way. I was about 6 hours in before I got on to the turning off the firewall. I hadn't seen the note on the exe you found, but I agree that isn't enough for AVG, and I agree that if there isn't a solution then we dump AVG. It seems an odd thing for AVG to not be worried about. There's plenty of folk out there loving these adapters, and also plenty returning these adapters and blaming Microsoft because they can't get them to work, and I'll bet a bunch of them are for this reason, it's just that the issue is so unexpected. I suspect this only comes back to haunt support.
I think there may be an IP range that needs to be open too. If I can find it, I'll post it back here for you. If I don't post within 2 days, I couldn't find it, and I think you're right that the advice then is that if you want to use the Microsoft Display Adapter, you want some other firewall than AVG.
Wow. Can't imagine how that's a sensible place to end up, but there we are ;-)
Hello Gents I had same issue and after couple hours looking for… David was rigth, unfortunnately I checked it after fixing… I found that under advanced firewall >customize>network profile few lines were as public, so, I set all to private and done ! hope this help future users with same issue.
I have a Surface Book, with exactly the same issues. I even upgraded my MWDA to the latest hardware to find that I had the same issues. Windows 10 can see the MWDA, install drivere (etc.) and attempt a connection, but in all attempts it timed out.
As a test I disabled the AVG Firewall componment (as have others in this thread) and hey-presto - it worked consistently. I re-enabled the AVG Firewall, and the problem re-emerged. All the solutions above are far too technical for a non-techy (thankfully I am a very technical person and work in IT). This issue is also giving Microsoft (in this case) undeserved bad press when it is an AVG issue. What I need is a simple way to enable the apropriate firewall rule, and something in the settings to be obvious.
I am going to try a lot of the advice in this thread, and I thank everyone in the public domain who has contributed and had the patience. If I relied on the MWDA this wouild be a deal breaker for me. I am a long standing AVG customer and recomend it to everyone. I am totally unimpressed with the response from AVG - not a priority indeed!!
However, brand loyalty doesn't seem to be anything companies care about in this day and age of rapid consumerism. If I replace AVG on my Surface Book, it will be replaced on all my PC's, phones and tablets in my home at the next renewal (Jan 2018), and I will remove AVG from my recomended products for friends/family, etc. A company only needs to screw me around once to lose me forever and AVG is this close.
I have a Surface Book, with exactly the same issues. I even upgraded my MWDA to the latest hardware to find that I had the same issues. Windows 10 can see the MWDA, install drivere (etc.) and attempt a connection, but in all attempts it timed out.
As a test I disabled the AVG Firewall componment (as have others in this thread) and hey-presto - it worked consistently. I re-enabled the AVG Firewall, and the problem re-emerged. All the solutions above are far too technical for a non-techy (thankfully I am a very technical person and work in IT). This issue is also giving Microsoft (in this case) undeserved bad press when it is an AVG issue. What I need is a simple way to enable the apropriate firewall rule, and something in the settings to be obvious.
I am going to try a lot of the advice in this thread, and I thank everyone in the public domain who has contributed and had the patience. If I relied on the MWDA this wouild be a deal breaker for me. I am a long standing AVG customer and recomend it to everyone. I am totally unimpressed with the response from AVG - not a priority indeed!!
However, brand loyalty doesn't seem to be anything companies care about in this day and age of rapid consumerism. If I replace AVG on my Surface Book, it will be replaced on all my PC's, phones and tablets in my home at the next renewal (Jan 2018), and I will remove AVG from my recomended products for friends/family, etc. A company only needs to screw me around once to lose me forever and AVG is this close.
Wow…I had forgotten all about this issue. I haven't used my MWDA in over a year, and when I last used it, my 'work-around' enabled it to function. That process was to disable the AVG firewall, connect MWDA, then re-enable AVG. In the meantime, I now use AVG 2017 Unlimited. I do not know if the MWDA issue has been resolved through the updates. When I am sifficiently bored, I will try it.
Dave, you've done well, and exhibited uncommon patience. I have precisely the same issue, on different televisions, but the same (fully up to date) Surface Pro and Surface 3 pcs failling to properly connect with a Microsoft Display Adapter in exactly this way. I was about 6 hours in before I got on to the turning off the firewall. I hadn't seen the note on the exe you found, but I agree that isn't enough for AVG, and I agree that if there isn't a solution then we dump AVG. It seems an odd thing for AVG to not be worried about. There's plenty of folk out there loving these adapters, and also plenty returning these adapters and blaming Microsoft because they can't get them to work, and I'll bet a bunch of them are for this reason, it's just that the issue is so unexpected. I suspect this only comes back to haunt support.
I think there may be an IP range that needs to be open too. If I can find it, I'll post it back here for you. If I don't post within 2 days, I couldn't find it, and I think you're right that the advice then is that if you want to use the Microsoft Display Adapter, you want some other firewall than AVG.
Wow. Can't imagine how that's a sensible place to end up, but there we are ;-)
Hi M. Zbynek, I created the rule and verified it exists. Could not connect. I viewed but cannot now find the place where rule details are specified. When I previously accessed it, I could pick either TCP or UDP for the rule. The Intel support text said to apply the rule to both protocols. How can I do this? On some previous website the difficulty with the Miracast technology is that it has some kind of dual access requirement. Does that compute? Cheers, Dave
Hi yet again, I forgot to emphasize that my Microsoft Wireless Display Adapter does not connnect through the LAN, wireless or otherwise. It functions directly from my Surface Pro 3 and the Samsung Smart TV, or alternately as I have tested, an LG computer monitor. I could turn off my Cisco DPC3825 and it would still mirror the display from Surface to the second monitor of my choosing. Cheers, Dave Kelly
I have uninstalled (just) AVG Firewall, and am relying on Windows Firewall - all my pain is gone
Search uninstall, click change or remove a program, AVG 2015, Change, Add remove features - change, Next, uncheck Firewall, Next, and follow your nose.
It is now July 16, 2015. My issue connecting my MWDA without disabling AVG Security firewall has not had any further response since April. I was told it had been elevated to a higher level of support capability.
Soon I wiil have to decide if I should renew my AVG subscription for three machines. Should I renew for a service that must be disabled to use an item of now common, worldwide hardware?
Can someone give me an update please? Cheers, Dave Kelly
I have not heard any feedback from AVG Support on this issue for several weeks. I can reliably connect my MWDA from my Microsoft Surface Pro3 as long as I disable AVG 2015 firewall during the connction process. During this step, I am protected by Win8.1Pro firewall.
Does this mean that AVG protects me in ways that MS does not? In what way does is this protection better? As one of a multitude of customers worldwide, I want a way of allowing a Miracast device to communicate and connect through AVG firewall. Otherwise AVG Security may not be the product for us any longer.
I wish to allow Microsoft Wireless Display Adapter through AVG2015 Firewall, on my SurfacePro3. I can connect by temporariliy disabling Firewall, but wish to avoid this step. The Device does not appear on Win8.1 Device Manager unless it is connected, and it diappears each time Win8.1 goes to sleep or disconnects. Entering the MWDA Miracast address in the AVG Firewall Applications Allow has not worked because the app dos not Exist until after it is already connected.
It is now July 16, 2015. My issue connecting my MWDA without disabling AVG Security firewall has not had any further response since April. I was told it had been elevated to a higher level of support capability.
Soon I wiil have to decide if I should renew my AVG subscription for three machines. Should I renew for a service that must be disabled to use an item of now common, worldwide hardware?
Can someone give me an update please? Cheers, Dave Kelly
Well AVG, you had better get thi up your priority list. This makes a major function of my expensive PC unuseable without disabling AVG. Not acceptable in a business.
I've also spent many hours and gone and bought replacemet hardware as I could not find any reason why my old hardware no longer worked.
I have a lot more money invested in my PC than the cost of AVG, so guess which one I will be dropping if this doesn't get fixed soon. rodtod
