Forum Discussion

gabrio-81's avatar
gabrio-81
Brass Contributor
Feb 14, 2021

Every time MS Edge updates, the firewall needs to ask permission again when there's no need

Every time when there is an update to edge, for instance there is one now from 88.0.705.50 then the Win10 firewall will ask again to authorise the access outgoing, that happens i think because the folder of the new version where Edge lives has changed, namely with the version number of the new version. so i had before \Microsoft\Edge\Application\88.0.705.50 and now it has just been installed to \Microsoft\Edge\Application\88.0.705.53 which means the firewall will soon request me to approve again as if it's a new program but it's just the new version.

 

Chrome updates a similar manner but this does not influence the firewall having to request this every single time. The executable file of chrome is within the /chrome and not within the folder with the release number. on edge instead, you have msedge.exe and also msedge.exe within each folder with the version number.

 

my shortcut is of course the version OUTSIDE the folder with the release number, it will still pop the firewall.

 

I have also created an issue in feedback up please upvote it https://aka.ms/AAaxwxo

 

is anyone experiencing it? i find it really annoying having to "allow" MS Edge every single time. cmon is MS on MS why this happens?

 

best,

Gabrio

17 Replies

    • Anonymous's avatar
      Anonymous
      Dziękuje Za zainteresowanie jestem ciekawy co o tym powiesz ?
      Ja mam kompilację sytemu Windows 19042.804
      Teraz jestem na innym urządzeniu więc piszę z innego konta
      Andrzej2255
      • HotCakeX's avatar
        HotCakeX
        MVP
        Hi,
        that's strange, have you changed any default settings in Windows firewall or Windows security (Defender)?
        i'm on the same build but not seeing this behavior
  • Anonymous's avatar
    Anonymous
    Tak potwierdzam na kilku komputerach zapora blokuje Edge
  • Henno_Keers's avatar
    Henno_Keers
    Iron Contributor

    gabrio-81 

    The firewall complaints because the path to the executable has changed, so for it, it is a new one. Hence needing a new rule. I presume you are running Canary?

     

    Regards, Henno

    • gabrio-81's avatar
      gabrio-81
      Brass Contributor

      Henno_Keers 

       

      thanks, yes i have realised that of course but:

       

      1. why is it doing it?

      2. why can't they fix it? Chrome updates the same and does not do this behaviour. I don't see why asking for firewall permissions every single time would be needed. surely if i said YES once i will still be ok with it no?

       

      No canary, all normal "stable/release" versions here.

      • Anonymous's avatar
        Anonymous
        Warto o tym mówić gdyby takie zdarzenie bywało u zwykłego użytkownika byłaby to bariera i problem !

Resources