Forum Discussion

William-ACCI's avatar
William-ACCI
Copper Contributor
Dec 04, 2019

Latest Edge Build Breaks Logmein

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?

    • MattGrant's avatar
      MattGrant
      Brass Contributor

      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.

      • Eric_Lawrence's avatar
        Eric_Lawrence
        Icon for Microsoft rankMicrosoft

        MattGrant - You're pointing to the bug 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.

  • dbaldwin's avatar
    dbaldwin
    Copper Contributor

    William-ACCI I too have noticed this exact issue with LogMeIn. Internet Explorer works fine. Just started around the 9th of December. Worked perfectly prior.

     

    Windows 10 Enterprise 1909 18363.535

    Edge: Version 80.0.361.5 (Official build) dev (64-bit)

    LogMeIn client ver 1.3.4650

     

    Would love to know when this is fixed!

    • MattGrant's avatar
      MattGrant
      Brass Contributor

      Just updated to today's realease and LMI still does not work. Neither does microcenter.com in Edge Dev.

      • MissyQ's avatar
        MissyQ
        Icon for Microsoft rankMicrosoft

        Hey, everyone! Thanks for bringing this to our attention. It seems this is happening in Chrome Canary as well (I tested myself with microcenter.com, I can't test with LogMeIn, though).

         

        Know that we're aware of it and we'll circle back once we have more information. Appreciate the understanding!

         

        Missy Quarry (she/her/hers)
        Community Manager - Microsoft Edge

  • MattGrant's avatar
    MattGrant
    Brass Contributor
    Just updated to Version 80.0.355.1 (Official build) dev (64-bit) and LMI still doesn't work, neither does microcenter.com WTF?
  • MattGrant's avatar
    MattGrant
    Brass Contributor

    William-ACCI 

    I am having the exact same issue and now I cannot load microcenter.com. Like you, I can login to LMI fine, but when I click on a computer, I get "Hmmm… can't reach this page The connection was reset.". Both sites work normally in all other browsers on my computers. I even went as far as installing the latest Edge Dev on a Windows Sandbox VM and both sites do not load. So that proves it is not something with my MS account sync. I also loaded Edge beta on the Sandbox VM and both sites work as they should.

    I fully understand that this is pre-beta software and stuff like this happens, it is just weird that it started so close to the final release. I hope we get a new build soon. I hate having to use Chrome to do anything anymore. I have been using Edge Dev for a couple months now am ready to remove Chrome from my computer as soon as it is fully released.

    • Eric_Lawrence's avatar
      Eric_Lawrence
      Icon for Microsoft rankMicrosoft

      MattGrant - The Microcenter problem is a bug in their website; we've reached out to them. The problem is also seen in the latest builds of Chrome (we're both based on Chromium). To workaround it, you can launch Edge like so:

       

      START > RUN > 

         msedge.exe --disable-features=PostQuantumCECPQ2 www.microcenter.com

      • MattGrant's avatar
        MattGrant
        Brass Contributor

        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.

  • Arkanel's avatar
    Arkanel
    Copper Contributor

    William-ACCI 

     

    I had this issue for a while.

    Same error. 

    Here is the screenshot (in french unfortunatly).

    • SimonBuckner's avatar
      SimonBuckner
      Copper Contributor

      So we are seeing the same here as well. 

       

      Version 80.0.345.0 (Official build) dev (64-bit)

      Windows 10 Ent 1903 (18362.418)

       

      I get the same error, even if I access the portal using guest profile & no extensions enabled.

       

       

       

      • Jason Poole's avatar
        Jason Poole
        Copper Contributor
        Same here, after update no longer can use Logmein to remote into a computer.

        Version 80.0.345.0 was working on earlier builds.
    • William-ACCI's avatar
      William-ACCI
      Copper Contributor

      HotCakeX 

       

      Developers Channel

      Microsoft Edge is up to date.Version 80.0.345.0 (Official build) dev (64-bit)

       

      Any ideas?

      • HotCakeX's avatar
        HotCakeX
        MVP
        Well it could be the new update breaking it or an extension was rendered incompatible or problematic after the update, could you please attach a screenshot of the error?

Resources