Forum Discussion
[FIXED] Edge insider Canary Not working anymore. opens all websites in WDAG Application Guard Window
UPDATE: Fixed in Edge insider Version 79.0.294.0 (Official build) canary (64-bit)
I just updated my Edge insider Canary to Version 79.0.292.0 (Official build) canary (64-bit)
and After that, when I type in something in the omnibox or click on any bookmark, the browser launches the Windows Defender Application Guard window and attempts to open that websites in there.
I said attempt because It tries and fails with this error:
I'm on Windows 10 fast ring build 18990. tried restarting computer and disabling all extensions but still no luck. whatever this last update had triggered this problem. so right now Edge insider canary is literally dead and I'm posting this with Edge classic.
anyone else experiencing this?
I'm also seeing this issue on Canary. No websites can load, as they all try to open in Application Guard and Application Guard seems to be completely broken.
Hi, thanks, can you please also mention which Windows 10 build/version you're using?
wanna make sure it's not related to Windows insider.
by the way I tried uninstalling application guard feature but it's failing. Windows restarted 2 times, said the changes were rolling back.
you could give it a try maybe it won't fail for you
- George Smyrlis
Microsoft
HotCakeX Same problem also for me. After upgrading to version 79.0.292.0 every page tries to load inside an Application Guard window but with no luck. My Windows version is 1903 10.0.18362 Build 18362
- Same with me on 1903. I honestly don't know how it'll be fixed because internet connection doesn't even work, so how is it going to search for updates? I guess we'll have to download the installer manually from another browser.
- When I open Edge canary, the main window opens and after few seconds the application guard window, but i can still manage to go to the settings and check for update in the about page.
also the news feed in the new tab page works for me.
- That bug has gone fixed many thanks
HotCakeX Fails for me on non-insider Win 10 1903 10.0.18362.387. Not only does it try to open in WDAG, it doesn't work in WDAG just as shown in your screenshot. WDAG still works fine with Spartan.
- Thanks, this narrows it down to the Edge insider canary only to be the source of the problem
HotCakeX Absolutely. I had tabs opened and manually checked this afternoon for updates in settings. After tapping the Restart button, WDAG started and nothing restored. I dropped back from canary to dev. I hope it is fixed tomorrow. I"m very surprised the build was released or even that check in verification didn't block the bug. Maybe the verification checks run on systems without WDAG enablrd.
- That happens to me too removing application guard you can browse normally when enable application guard again wont let you it's broken I'm alm windows 10 insider 18990 better wait new update for canary
- George Smyrlis
Does anyone has any feedback from the Dev Team for this critical issue? Like josh_bodner? Thank you
- I just noticed today the bug can't use edge canary wont open pages just application guard broken and prevents to use it before this build working fine can't open tabs too
Yes - I am also seeing this same issue - with WDAG. (running GA build 18362.356)
Will see what happens with next Canary build release....I am using Edge Dev 287.2 to reply - no issues with that build.
This is a DNS issue, and it is still broken depending on the DNS server being used.
The issue is edgetipscdn.microsoft.com aliases itself.
Such as:
nslookup
> edgetipscdn.microsoft.com
Server: [8.8.8.8]
Address: 8.8.8.8Non-authoritative answer:
Name: sni1gl.wpc.epsiloncdn.net
Address: 152.195.19.97
Aliases: edgetipscdn.microsoft.com
edgedccdn.azureedge.net
edgedccdn.ec.azureedge.net
scdn1c9d1.wpc.37160.epsiloncdn.netSome DNS servers only return "edgetipscdn.microsoft.com" and nothing else, therefore creating an infinite DNS loop.
I fixed it by appending this to my c:\windows\system32\drivers\etc\hosts:
152.195.19.97 edgetipscdn.microsoft.com
- very good fix wdag has stopped creating problems im in 21h1 builds so its working fine now still need monitor it if comes again the crash
