@Huda_GlassWire Please can you check if this longstanding issue is being worked on. The problem is with apps and Windows components which install updates to a new folder name and so require re-approval, or simply fail to trigger a prompt and so are silently blocked. This has been a known issue for years and previous reps have claimed it was being worked on. Suggested solutions include rules which incorporate publisher certificates and/or wildcards paths. Here are a couple more old threads on the issue:
Microsoft Edge WebView2 is a prime example of the long standing problem, this Windows component is used by many other applications. Following an update it installs into a new folder and GlassWire silently blocks it. Now other unrelated apps will suddenly stop working and the user has to divine why.
All we need is a basic rule which uses wildcards and (for extra security) checks the digital signature.
So the executable path is:
C:\Program Files (x86)\Microsoft\EdgeWebView\Application\*\msedgewebview2.exe
Instead of:
C:\Program Files (x86)\Microsoft\EdgeWebView\Application\139.0.3405.125\msedgewebview2.exe