Latest Edge Build Breaks Logmein

[William-ACCI]

I am impressed with the Chromium-Edge Browser and have been using it as my default for a few months.  This evening, after coming home from work, I was presented with a new build and then went about my business.  

I needed to update a few systems at work and logged on to Logmein which had worked fine yesterday.  Now, when I select a computer to remote into, Edge displays an error page asking me to check firewall and proxy settings. It's a complete show stopper.

I tested with the original non-Chromium Edge and Logmein works fine.  I also reset the latest Chromium-build but still encountered the same issue.

I am interested in hearing if others are experiencing the same thing?

[#2]

@Eric_Lawrence 

I don't think any of us can send you a link to what is not working with LMI. We are able to login to our LMI accounts, but when you click on a computer in your computer list, it immediately gives the message "Hmmm, can't reach this page". This issue does not happen in Chrome or regular Edge. It is a known bug in the Chrome Canary builds too (https://bugs.chromium.org/p/chromium/issues/detail?id=1028602). Also, www.microcenter.com is not working.

[#3]

@Eric_Lawrence 

Both LMI and the microcenter.com issue started on the same day for me about 2  or 3 Edge Dev builds ago. Strange that LMI and microcenter.com work in every other browser but Edge Dev (and Chrome Canary).

[#4]

@Eric_Lawrence 

Also, that command you said to run still gives me the Hmmm, can't reach this page if I have the browser open already. If I close all open instances, then the command opens MC's website. After that, if I try to go to the page normally, it gives the error.

[#5]

@MattGrant - You're pointing to the bug I filed on the Microcenter.com issue; that problem with Microcenter is well understood. Your repro steps allowed me to discover that this is indeed the same issue on the LogMeIn scenario.

If starting Edge with the command line didn't resolve the issue for Microcenter, it means that there was a hidden Edge instance that was still open; you'll need to use Task Manager to find those Edge instances and kill them first before re-launching with the command line.

[#6]

@Eric_Lawrence 

I guess I could create you as a user on my LMI Central account, assign you a computer to have access to and let you log into LMI to see what is happening. Please email me directly and I will get you setup to test it.

[#7]

@MattGrant You were right-- this is the same issue. Starting the browser with the --disable-features=PostQuantumCECPQ2 command line fixes LogMeIn as well. I'll update the bug.

[#8]

@Eric_Lawrence 

Yes, I just tested it and it works as it should. What is the long term fix for this?

[#9]

@MattGrant -- I suspect the most likely outcome here is that we/the Chromium team will disable this experiment for a while to allow sites some time to update themselves. 

[#10]

@Eric_Lawrence 

Just to inform this post that yes the problem was fixed for me also at the beginning of Januaray 2020 but the problem came back with Edge Canary 82.0.425.0 or just the version before this one.

[#11]

We're been stuck on 82.0.425.0 on Canary channel for a while now, it broke/removed PDF inking functions too. problematic update overall