Forum Discussion
Rafaelhilario
Apr 17, 2021Brass Contributor
Issues on MICROSOFT EDGE
Hey Everyone! Good evening for all of you, this is my first post here in this communitty and I'm here for asking some of you, how can I solve one issue which I've been experiencing since today. ...
- Apr 17, 2021Hi,
it was a temporary issue, many people were experiencing it, even saw tweets about it, but now I'm checking and it's fixed now. I'm testing it on Edge stable, Dev and Canary channels.
so just check for update again, hopefully you see it's fixed too.
dftf-wip
Apr 17, 2021Iron Contributor
A lot of people were reporting the same issue.
Though I do find it odd how it suggests users add "MicrosoftEdgeUpdate.exe" into their firewall exceptions when, by-default, they don't even add that exception into the Windows 10 built-in firewall exceptions list! Surely they could? The main edge.exe process does get automatically added...
Though I do find it odd how it suggests users add "MicrosoftEdgeUpdate.exe" into their firewall exceptions when, by-default, they don't even add that exception into the Windows 10 built-in firewall exceptions list! Surely they could? The main edge.exe process does get automatically added...
- HotCakeXApr 17, 2021MVPBugs are odd, but there are many situations where people have a strict firewall rules, that's when that message in Edge updater is relevant for.
- dftf-wipApr 17, 2021Iron ContributorSure, but my point still stands: why doesn't Edge add that executable into the Windows Firewall (or Windows Security Firewall, in recent Windows 10 versions) by-default? It adds the main "edge.exe" process by-default, but not the one suggested there?
Is it asking too-much to expect Microsoft to add that exception into the Windows built-in firewall, given both products are made by, you-know... Microsoft?- HotCakeXApr 18, 2021MVPSpoiler
dftf-wip wrote:
Sure, but my point still stands: why doesn't Edge add that executable into the Windows Firewall (or Windows Security Firewall, in recent Windows 10 versions) by-default? It adds the main "edge.exe" process by-default, but not the one suggested there?
Is it asking too-much to expect Microsoft to add that exception into the Windows built-in firewall, given both products are made by, you-know... Microsoft?Because it's already working properly.